[texworks] new binaries for Windows and Mac OS X
bvoisin at me.com
Mon Oct 27 22:45:21 CET 2008
On 27 oct. 08, at 12:57, Jonathan Kew wrote:
> The intended behavior is that TeXworks should always respect the
> language chosen in Preferences / General / Interface Locale, though
> note that you may still see bits of English when a non-English
> locale is selected because the translations might not be complete,
> and there are a few strings (such as syntax coloring and auto-indent
> option names) that are not currently localizable.
> If there is no preference file (org.tug.TeXworks.plist on the Mac),
> then TeXworks should look at the system locale on startup, and
> default to this if a matching translation is available. But as soon
> as you pick a language in Preferences, this should override the
> system locale.
What's happening is a mystery to me. Even after deleting ~/Library/
TeXworks and ~/Library/Preferences/org.tug.TeXworks.plist, then
reinstalling TeXworks from scratch, switching the system locale to
English, and selecting the "English (built-in)" locale in TeXworks,
TeXworks still has French menus.
Two odd things:
- Opening org.tug.TeXworks.plist in Property List Editor, the language
item is of class String and has value Aucun (the French for None).
- In the newly recreated ~/Library/TeXworks, the translations folder
is empty. I'm not absolutely sure, but I think earlier this morning,
before experimenting with locale selection, there used to be files
there. I cannot get TeXworks to recreate a non-empty translations
In a desperate attempt to figure out what's happening, I checked the
Qt libraries in /Libraries/Frameworks and the hunspell and poppler
libraries in /usr/local/lib: none of the files there seems to have
ever been modified. I thought maybe there was some Qt configuration
file somewhere which had mistakenly been set to French during the
experimentation, but that doesn't seem to be the case.
More information about the texworks