-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
some extra files are not placed at the specified coordinates #33
Comments
Could it have something to do with the length of the name? Could you please try |
I tried different combinations of
|
Some more examples (you can see also examples of issue #32). 2 extra files, correctly placed: 2 extra files, wrongly placed: 3 extra files, correctly placed: 3 extra files, wrongly placed: |
[In case you're wondering, Pippo is the Italian name of Goofy and is one of the most used metasyntactic variable names in Italian, usually accompanied by Pluto and Paperino (= Donald Duck). :) ] |
Hehe, nice trivia :) I have very little time at the moment but will try to look at this more within a week. I think that it might have something to do with the ordering in the |
Hmm, the entries are sorted but maybe the sorting is wrong. https://github.com/LinusU/node-ds-store/blob/master/lib/ds-store.js#L278 |
I was short of time the last days, but tomorrow morning I should be able to do some more tests. |
I have the same issue here, as soon as I use spaces in my file name I get some icons being misplaced. In the example above, if I change "Project Scotty.app" to "ProjectScotty.app" I get proper placement. Here is my spec: { "icons": { "extra": [ |
I did some tests. I couldn't reproduce what @jschmidt42 describes: I get the same wrong placement of the icons both with and without the space in the application name. Maybe the @LinusU Any ideas? |
From http://search.cpan.org/~wiml/Mac-Finder-DSStore/DSStoreFormat.pod: "My guess is that the string comparison follows the same rules as HFS+ described in Apple's TN1150." https://developer.apple.com/legacy/library/technotes/tn/tn1150.html specifies that "Unicode strings will be stored in fully decomposed form, with composing characters stored in canonical order" and contains a FastUnicodeCompare routine defined as the "HFS Plus case-insensitive string comparison algorithm" The unorm module is used to fully decompose and canonically order filename strings. The FastUnicodeCompare routine is implemented as HFSPlusFastUnicodeCompare and used in Entry.sort instead of localeCompare. This solves LinusU/node-appdmg#33. (At first I only added .toLowerCase() to filename strings in Entry.sort, which solved the issue, but only in case of names containing only latin letters without diacritics.)
From http://search.cpan.org/~wiml/Mac-Finder-DSStore/DSStoreFormat.pod: "My guess is that the string comparison follows the same rules as HFS+ described in Apple's TN1150." https://developer.apple.com/legacy/library/technotes/tn/tn1150.html specifies that "Unicode strings will be stored in fully decomposed form, with composing characters stored in canonical order" and contains a FastUnicodeCompare routine defined as the "HFS Plus case-insensitive string comparison algorithm" The unorm module is used to fully decompose and canonically order filename strings. The FastUnicodeCompare routine is implemented as HFSPlusFastUnicodeCompare and used in Entry.sort instead of localeCompare. This solves LinusU/node-appdmg#33. (At first I only added .toLowerCase() to filename strings in Entry.sort, which solved the issue, but only in case of names containing only latin letters without diacritics.)
This is now fixed in |
This seems to depend on the file name: e.g. an empty
ChangeLog
file is placed ignoringXpos
andYpos
, while the same empty file renamed toDangeLog
is placed at the specified coordinates.The text was updated successfully, but these errors were encountered: