← Back to team overview

spv-dev team mailing list archive

[Bug 612745] Re: Functional tests with a unicode file name on Mac OS X

 

** Description changed:

  Mac OS X stores files names with Unicode characters with a different
  decomposition format than on GNU/Linux. Bzr has some trouble to handle
  that (see
  http://wiki.bazaar.canonical.com/UnicodeSupport#Mac%20OS%20X%20issues)
  and to make the transition between different OS. We can have files
  reported has not versionned, two files, etc. and it can be worse when we
  manipulate those files in some tests.
  
  So, we must avoid Unicode characters but we still want to test with Unicode file names in our functional tests. My proposition is :
-   1) Remove those files from bzr.
-   2) Generate those files within the test
+   1) Remove those files from bzr.
+   2) Generate those files within the test
  
-  BTW, we have many duplication is test's resources. Auto-generating
- files inside the test from a template we be better anyway.
+  BTW, we have many duplications in test's resources. Auto-generating
+ files inside the test from a template will be better anyway.

-- 
Functional tests with a unicode file name on Mac OS X
https://bugs.launchpad.net/bugs/612745
You received this bug notification because you are a member of
SlidePresenterView Development Team, which is subscribed to
SlidePresenterView.

Status in SlidePresenterView - Console for presenters: Confirmed

Bug description:
Mac OS X stores files names with Unicode characters with a different decomposition format than on GNU/Linux. Bzr has some trouble to handle that (see http://wiki.bazaar.canonical.com/UnicodeSupport#Mac%20OS%20X%20issues) and to make the transition between different OS. We can have files reported has not versionned, two files, etc. and it can be worse when we manipulate those files in some tests.

So, we must avoid Unicode characters but we still want to test with Unicode file names in our functional tests. My proposition is :
  1) Remove those files from bzr.
  2) Generate those files within the test

 BTW, we have many duplications in test's resources. Auto-generating files inside the test from a template will be better anyway.







References