Hi Jürgen, > Exactly my opinion and i hope that we can answer this question in the > context of the general toolkit question. If we will go forward for > example with a XUL approach for UI components we should use the XUL > resource system.
I was more looking for a solution which can be used within the next few months ... ;) > I would say it is perfect for components where the UI is done by a > generic approach intern like menu items or toolbars for Add-Ons or in > the future localized display names and descriptions for Calc Add-In > functions. But probably not for complete dialogs. Admittedly, I'm currently only looking for localized strings, not for a UNO API for *all* the functionality of our C++ resource system. However, still I'd consider storing those strings in the configuration a hack (see the other mail). Given that in Java, as well as in XUL, localizing of strings is often done via properties files, would it be reasonable to add support for properties files (basically text files with a list of name=value pairs) to OOo, and create an UNO API for it? This should be future-proof: No matter which other toolkit we'll use later on, chances are good that it will also (need to) support such kind of localized strings. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
