Hi Martin, *, 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? > Shouldn't lang pack installs feel > similar across different platforms? Well, "no" is the answer I guess... On linux, you install rpms, on solaris you install pgks, on Windows you run an exe,.... The installation process is different on each platform. > That way these language packs can be > properly localized - which they will have to be eventually. Of course, if > those strings apply to the Mac installation process. > > I believe (windows/linux) language-pack strings are currently in (not sure > if in all of those): > scp2/source/lingu.po > scp2/source/ooo.po > svx/source/dialog.po You're not looking at a vanilla repository. (OOo doesn't use po files) But even if it would mean the sdf files: As the installation on Mac is different from the installation on other platforms, there are no matching strings yet. (for the button labels maybe, but that doesn't really count :-) > I would suggest not to use system strings like "Yes", "No", "OK", "Cancel", > "Abort", "Continue" etc., because OSX interface is not translated to many > languages (in fact it is localized in a very small number of languages, much > less than OpenOffice.org). So all these strings for the langpack installer > should, IMHO, be taken out of the OpenOffice.org po files as well. In fact, I'm not using default strings already, but set them to OK, Cancel manually already. > 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 > One could download the wrong pack and > only find out later that it's impossible to use the interface and that the > process must be repeated and that the wrong ui langpack must be removed :) See above - you don't download the script alone, but the dmg containing the script :-) And the languagepack installer doesn't switch the UI language by itself. The user would have to manually switch the language in Tools|Options→Languages, so he won't be presented with an incomprehensible UI in that case either :-) (the language will only switch if the langaugepack matches the langauge of your Mac-Settings and the base version doesn't since OOo defaults to "default" - so when you have a french version of Mac OSX, an english base version of OOo and then install the french languagepack, OOo will launch with french UI, since "default" means langauge of the operating system - but if you use Mac OSX in that language, I'm sure you'll understan OOo in that langauge, so no problem here...) > [I snip all the full-stop missing ones for brevity] > "This might take a moment" -> [...] why is > this sentence in a new line? Maybe it should follow the previous sentence in > the same paragraph. If you want it in a separate paragraph, I suggest you > add spacing between both paragraphs. Well, I just added a newline, no real thought put in this - that's why I ask for feedback here :-)) > 2nd Window > "Choose the installation for which you want to install the languagepack" -> > "language pack" [...] I think > there are word order problems here, so I suggest: "Choose the installation > to install the language pack for:" or something like that? Well, I'm open to suggestions, it could be a totally different wording as well. But maybe a native-english speaker could jump in and make a proposal? > 3rd Window > "Click OK to start the installation" [...] > "(installation might take a minute...)" -> "Installation might take a > minute, please wait." or "please be patient" :) > > 4th Window > "Installation is completed - you should now be able to switch the UI > language" -> [...] does a newbie user know, what UI is? + Hmm - not sure, but how would you call it then? > "should be able" - arent we sure? Well, you never know bugs beforehand :-) - and users are creative when it comes to finding a way to break things :-) But seriously: When that dialog appears, the installation is complete and "we are sure". > + "completed"? -> here is my suggestion to > make it a bit easier for novice users: > "Installation is complete.\n\nYou can switch the user interface language > with $menu-path." where $menu-path would be the menu path to change the ui > language, I don't know it, so it should be like "Tools - Language - Change > ..." or whatever it truly is. Thanks > Don't forget the full stop at the end :) :-) > 5th Window (file picker) > It would be great if the strings were from OOo and not from OS language, so > that it would be localized to the lang pack language. This isn't possible. That dialog is Mac's own dialog, and the only thing you can configure there is the prompt at the top. > 7th window > "Installation failed, most likely your account doesn't have the necessary > privileges. Do you want to identify as administrator and try again?" > First, isn't this something that installer should find out at the beginning > of the process - if the user has sufficient privileges and if not it would > ask for the admin password? Well, this is very similar to what mac does itself when you try to copy an app to the Applicaitons folder as a regular user. It attempts to copy (the progress bar appears), then it prompts you that you need to identify or abort the process. If you choose to identify, you'll get the username/password prompt and the process continues. As usually the user who did install the base version of OOo also installs a langaugepack, most users will not see this dialog (even more so as the default user account on Mac OSX has administrator privileges already) Checking for privileges would mean to check each directory of the OOo installation for write permissions of the user's account. It is way easier and more reliable to just react on the error case here. > But anyway, here are the corrections: account > should be stated as computer/os/osx/mac account - not to confuse user about > usernames (web, mail etc.)? + "necessary"->"required" + privileges? maybe > rights? + "administrator" or "Administrator", I am not sure which ok for > this situation. > Here is the not-finished result, someone can make it much better, I believe: > "Installation failed. Most likely your (computer?) account doesn't have the > required privileges.\n\nWould you like to login with administrative rights > and retry the installation process?" That last part is wrong. You don't need to login with administrative rights at all. You identify with an administrator account's credentials so that the installation is allowed to run a command with administrator privileges. > "Yes, login and retry" (I don't like "identify") + "No, abort installation" Well, identify is the term Mac OSX uses (at least in german it is identifizieren, which translates back to identify - not sure what the english version of Mac uses though...) > Last window > "Installation failed" -> missing a full stop + maybe it's not bad to mention > installation of what failed: "Installation of OpenOffice.org language pack > failed." + "\nVisit Mac porting wiki for further information." > Maybe a link to forums or documentation should be available for unsucessful > installators. To the wiki? Or mailing list? > > That being said, my English is probably poor enough to raise even more dust > as the suggestions themselves ... > > I guess it would be best if the language packs would exist only in two > versions - in the English and the language of the langage pack. This way > only two versions of a lang pack would be compiled/repacked (i.e. English > and French for French, only English and Slovenian for Slovenian etc.). 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. ciao Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
