Hi Martin, Clytie, On 9/20/07, Martin Srebotnjak <[EMAIL PROTECTED]> wrote: > Ok, before I try anything, what happens with languages that do not > have a Mac OSX GUI translated (like Slovenian)? Will this work anyway > (after GUI language of choice in OSX is set to Slovenian)?
The trick mentioned in this thread only refers to the labels of the bold menu in the native Toolbar that holds default entries of MacOSX for applications (Preferences, about, services, hide, hide others) and the labels of the default elements of the native filepicker (button labels, names of folders, etc). The strings for these elements then come from MacOSX directly, so this will only work when MacOSX offerss suppot for Slovenian by itself. I don't know whether MacOSX is available in Slovenian. If Slovenian is not supported, it will choose a fallback on its own, and that's most likely English in that case. > And what directory must I put what in? Folder sl-SI or sl? Sorry, but > I am asking this because I cannot access that apple developers > webpage. The link I posted doesn't require any apple-developer membership or similar, it is public for all users that browse to the site, no login or similar required. But sl is enough. sl-SL (both other letters uppercase then) would only be required if there are different variants of Slovenian, like there is for example en-GB and en-US. Or maybe an example where it matter more: chinese simplified vs traditional. Adding a lproj folder as suggested in this thread will not automatically translate other parts of the office, this would still need to be done via the regular OOo tranlsation mechanism (i.e. you translate the strings from the sdf files) When slovenian is not supported by MacOSX, then the folder alone is not enough, one would need to add a file that contains the translations then. But I don't know in what "realm" (don't know the official term here, but you can have different "sections" of translations that will then correspond to different filenames within that folder) and I don't know what the identifiers of the strings would be (the format is a UTF-16 encoded textfile with each line is an entry in the form of <id> = <translation>) So you translators don't have to do anything if adding the directory alone works for you already. If it doesn't = your language is not supported by Mac OSX itself, probably more effort is needed, at least,you would need to provide the translations for these strings and most likely OOo must be change to explicitly tell the system that it runs in that language. ciao Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
