I agree with Rafaella that there are IU issues that are not translation.
An example of this (which I have not yet reported) is for example that
when a language uses fonts that have a lot of vertical height (such as
Khmer) the document recovery window (for the rare occassion in which OOo
crashes) ... becomes too tall, and goes out of the screen. This is an UI
issue related to localisation, but not translation.
Javier
Rafaella Braconi wrote:
Hi Eike,
thank you for coming back to me on this.
Yes, my concerns would have been that UI and translation are 2
different things. A UI bug does not necessarily mean that this needs
to be fixed in the translation and ... on the other hand a translation
bug may be referring to the Help or other components as well.
I would also suggest not to replace *UI* with *translation*.
Thanks,
Rafaella
Eike Rathke wrote On 04/04/06 20:17,:
Hi Rafaella,
On Mon, Apr 03, 2006 at 13:44:19 +0200, Rafaella Braconi wrote:
I am not quite sure to understand the reasons why we should replace
UI with translation....
I thought 'translation' would be a more self-speaking name than 'UI' to
report bugs about wrong wording and spelling errors.
On the other hand there might be issues where mnemonics are duplicated
or strings are truncated because of a dialog being too narrow, or
unacceptable colors are used, or animals on an icon, or ...
So 'UI' _is_ fine, if commonly understood.
Eike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
