Apache OpenOffice (AOO) Bugzilla – Issue 62912
Improve translation for units, especially plural forms (like "pixels"), in helpcontent and UI
Last modified: 2013-02-07 21:50:51 UTC
Open Draw, create text box, right click, select Text, tab Text animation, select some anitmation - as you see in screenshot (attached), string 'Pixel' in middle field is not translated, and it is not translatable too.
Created attachment 34665 [details] screenshot
Which language are you using? I do not understand then problem completely. You say: "..string 'Pixel' in middle field is not translated, and it is not translatable too." Should it be translated? Or can't it be translated? What should it look like? Thanks.
Does not matter, which language I use. :) Word 'pixel' has different shape in several languages and this string in this dialog is not localizable, ie. it is not in localize.sdf. PS. Better were to use abbreviated unit at all, as it avoids problem with multiple plural forms too in most cases. It is ugly even in english (1 Pixel, 2 Pixel, 4 Pixel...
Reassigned. Please handle.
If I understand it corrctly vagula recommends to use abbreviations for units, because so translation problems, expecial for plural forms, can be avoided: Lang Sing. Plur. Sing/Plur ----------------------------------------------------- Geman: Pixel Pixel px / px Spanish: Píxel Píxelex px / px (?) English: pixel pixels px /px Svedisch Pixel Pixlar ? Italian: Pixel Pixel ? Polish: Piksel Piksele All these exaples without warranty ;-) @vagula: Do you agree with a new summary: For "untranslated" units abbreviations instead of complete word anglicisms should be used.
Yes, of course (since plural handling in oo.o is 'as is'). But even abbreviations must be translatable, because of different charsets languages may use (cyrillic, etc).
My first goal why I submitted issue was to change this fixed string to translatable string, non-translatable parts in UI are defects, not RFE.
Lutz, can you please take care of the below bug? This is a bug in the English UI which affects localization. Thanks, Rafaella. here the summary: =========== We have 2 issues: 1) Pixel seems not to be translatable because it is not included in the database. Please create a string for it 2) Pixel need to be both for the singular and the plural form. Please create a string saying Pixel(s) so that both the source and the target languages are correct in the UI - or a least the localizers are aware that this term is used for both the singular and the plural form ======
There are several forms of plurals in Czech. E.g. for the work pixel, it is: 1 pixel 2 pixely 3 pixely 4 pixely 5 pixelů 6 pixelů ... So we should localize the term "Pixel(s)" as "pixel(yů)"? Sorry but this is ugly.
see #i45551# for similar issue.
I suggest to change this string to abbreviation. Because the other box in the same dialog uses abbreviations (ms, not milliseconds). And it avoids problem with multiple plural forms.
Frank, please take care of this one. I strongly object against using an abbreviation for the word "pixel"! This is different to milliseconds, which are abbreviated as "ms", because that's a widely known abbreviation. "px" is mostly unknown, so we cannot use it. We are designing this software for users, not for translation processes. I am most confident that you will find a good solution. Thanks. Lutz.