On Wed, 27 Sep 2000, Thomas Diehl wrote : >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DBEGIN FORWARDED ME= SSAGE=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>From: =3D?ISO-8859-2?Q?Tinkl_Luk=3DE1=3DB9?=3D >>To: "'kde-i18n-doc@master.kde.org'" >>Subject: RE: koffice translations!!! >>Date: Wed, 27 Sep 2000 14:14:37 +0200 > >> "Erik K. Pedersen" wrote: >> >=20 >> > I did the translations yesterday. I know I have translated=20 >> these before. Have >> > they been in kspread before, then taken out and put back=20 >> in? Hyperbolic tangent >> > does not appear in any other po-file, but I know I have=20 >> translated that before. >> Yes, they were in kspread before. But one message per function, now we >> have about 6 >> messages per function. > >No, I must disagree - it's not only about splitting lines.=20 >Right now, I'm translating kspread.po and I'm really shocked why Torben = had >to change the functions' examples too. Sometimes, the example values cha= nged >and even several completely new strings were added. Moreover, I had to >correct each and every function, because kspread now uses a colon as >parameter separator and respects the locale. So I had to translate all o= f >them according to our locale, including the thousands and decimal separa= tor. >:-(( This is some sort of a catch-22, isn't it ? Torben is so nice as to implement what many non-English users asked: bein= g able to enter numbers in kspread using their locale. Well, in many languages, it's the comma that is used for the decimal poin= t, and kspread used to use the comma for separating arguments passed to a=20 koscript function call. But it can't be both, otherwise myfunc(1,2,3) cou= ld=20 mean a lot of different things ! So, as decided since quite a long time now, he fixes this, turning the co= mma into a semicolon, which isn't a decimal point for anyone. Of course the examples had to be fixed ! It's pointless to have examples,= =20 otherwise. I can understand the frustation due to the changes in the messages, but w= hen=20 the related fix _is_ a fix for non-English users, I think a bit of revers= e=20 understanding would be appropriate as well. On the whole, the timing for this KOffice hacking wasn't very good, that'= s=20 for sure. But when a government offers to pay for a developer & translato= r meeting session, you can't just say "good idea, but let's wait for after = 2.0,=20 we are in a freeze currently". --=20 David FAURE, david@mandrakesoft.com, faure@kde.org http://www.mandrakesoft.com/~david/, http://www.konqueror.org/ KDE, Making The Future of Computing Available Today See http://www.kde.org/kde1-and-kde2.html for how to set up KDE 2