On 24/3/10 05:16, Jon Cruz wrote:
On Mar 23, 2010, at 6:25 AM, Stuart Edwards wrote:
3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] Warning: AppleCollationOrder setting not found, using AppleLocale. 3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] Setting Language: .UTF-8
The message 'Setting Language: .UTF-8' comes from the launcher script 'Contents/Resources/bin/inkscape' which tries to look up a language string it has read from the system preferences in the file '/usr/share/locale/locale.alias' but fails because that alias table doesn't include a lot of entries on some (?) systems. '/usr/X11/share/X11/locale/locale.alias' (at least on Leopard) could be a better choice as lookup table imho.
see also: Bug #476678 “Mac OS X: Fails to get locale in Japanese”: https://bugs.launchpad.net/inkscape/+bug/476678 comment #2
3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] cp: /Users/stu/inkscape_port/inkscape-0.47/packaging/macosx/stInkscape-aqua.app/Contents/Resources/etc/pango/pangox.aliases: No such file or directory
The packaging and launcher script needs to take into account that some files are not needed when building / running without X11 (e.g. the X font backend for pango)
3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] (process:41460): Gtk-WARNING **: Locale not supported by C library. 3/23/10 8:51:51 AM [0x0-0x606606].org.inkscape.Inkscape[41457] Using the fallback 'C' locale.
This seems an GTK+ issue I never really found an explanation for (using google ;), but the message is reported for other GTK+/X11 applications too, on different (linux) systems and with differing locale settings, not limited to Inkscape application bundles for Mac OS X.
I think this one might be related to needing a few magic directories added. I found this with fixing Java apps for OS X. One tricky point was that one a particular box had a locale unblocked for an app, it stayed unblocked in that box.
AFAICT adding empty *.lprj folders to 'Contents/Resources' does not solve the 'empty' $LANG string that is wrongly set it the launcher script but may override it on some systems? I no longer see the GTK+ message "Gtk-WARNING **: Locale not supported by C library." when using a modified version of the launcher script which correctly sets $LANG after reading the menu language setting from the system preferences.
~suv