Joerg Barfurth wrote:
Hi,
Frank Schönheit wrote:
currently, no way exists fore mere UNO components to access localized
resources, i.e. data stored in OOo's *.res files [1]. That's Bad (TM),
since it forces UNO components to use unlocalized error messages, for
instance.
I'm not sure OOo's res files are the best thing to use for components.
At least they seem better suited to strictly office components, than for
any other component that can run in a URE.
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.
FWIW the configuration database can automatically retrieve data for the
current UI locale. This has been (ab)used by component authors to
provide localized messages. I can't say whether we consider that a good
thing, but as one data point, even the OOo command names (for menus or
toolbar tooltips) are localized this way now.
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.
Juergen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
