On 31/12/2007, Christian Lohmaier <[EMAIL PROTECTED]> wrote: > > Hi Martin, *,
Hello, On Dec 31, 2007 1:23 PM, Martin Srebotnjak <[EMAIL PROTECTED]> wrote: > > > > why not use some strings that are already in the po files? Wont these > > strings end in a po file eventually? > > As OOo doesn't use po files: What files are you referring to? As a localizer of OOo I am editing po files. I think this is a world-wide way how other localizers do it. Because if we edited the sdf file directly, we would be lost. But if you get no reference from my file references, just forget them :) > As far as your English strings are concerned, they probably need some > native > > English speaker tweaking, but you could do that by adding them to po > files > > and asking OOo/Sun teams to check them. Here are just my 2 cents, > although I > > am also not a native English speaker: > > > > 1st Window > > "Welcome to the OpenOffice.org Languagepack Installer" -> "Languagepack" > or > > "Language Pack"? Shouldn't the language be explicitly stated on this > first > > window? Like "French" or "Slovenian"? > > Hmm - the language is included in the filename of the dmg like > OpenOffice.org-langpack-2.3.0_fr.dmg It is included in the name, right. But let's say you are in a ftp folder with all possible installers or at a webpage with dropdown list of all available lang packs, and by mistake you click on the wrong one (one above or under your preferred language). The file gets downloaded. Since the filename is long, the name on the mac Desktop is truncated, so you don't see the language shortcut on the desktop. You double click the file. There is no way to know you downloaded and installed the wrong language. But maybe I shouldn't care for average end user, I will take more care when clicking on the right language pack. Hmm - one could put both an english and one localized installscript > into the package. But then I wonder how many users will think that > they need to run both... > > I don't think it makes sense to provide two seperate installers for > each langauge. That's right. That's why I suggested *all* localized installscripts in the single language pack installer. With an additional first screen for installation language selection (that opens in OSX UI language). Lp, m.
