(Thanks to whoever did it for re-subscribing me to the dev list)
I'm making this last post to both lists and then will try to find the
time to look into things on the lyx-devel side.
As I alluded to before, NeXT/OPEN/GNUstep/Cocoa allows one to
dynamically add and remove language support from a compiled program,
and it'd be nice for LyX to have a similar facility (perhaps it already
does, I haven't looked into it yet).
For the matter of different dialogs in different front-end versions, it
seems to me that the solution would be to have a single place to store
_all_ such, and then the xforms version grabs a version specific to it,
while the QT version gets one which it wants, and in the event of a
single version being available, they all fall back to that.
That way a translator only has one file/set to work on.
As an example, TeXshop has the following directories in itself:
Dutch.lproj
English.lproj
French.lproj
German.lproj
Italian.lproj
Japanese.lproj
Portuguese.lproj
Romanian.lproj
Spanish.lproj
each of which provides support for the appropriate language.
English.lproj then has:
Credits.rtf
CustomInfo.plist
FindPanel.nib
FindPanel.strings
InfoPlist.strings
Localizable.strings
MacroEditor.nib
MainMenu.nib
MyDocument.nib
Preferences.nib
TeXShop.scriptTerminology
TeXShopHelp
ToolbarItems.strings
completionpanel1.2.nib
matrixpanel.nib
One really cool thing here is that a user can edit a program's .nib
files to introduce new capabilities w/o recompiling the app.
Anyway, I hope that this is seen as helpful or constructive. I really
feel LyX is one of the most innovative, and forward-looking
applications available (open or closed-source) and am very glad to have
a new version running again, and am very much looking forward to 1.4
and beyond.
William
--
William Adams, publishing specialist
voice - 717-731-6707 | Fax - 717-731-6708
www.atlis.com
