-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
German Localization #1
Comments
Hi everybody, Second Person FormsI noticed that some used the more formal, so called polite forms for the second person singular and plural. I think that Apple nowadays uses the more direct, less formal «du/ihr». But it should at least be consistent throughout the app. Flavors of GermanSome strings could even be further adjusted to e.g. de-CH, de-AT. de-CH (Switzerland)
Edit: I split the concrete suggestions into a separate pull request: #16 |
In some cases, 'tape' is translated as 'Beleg', which means something like a receipt as far as I know. "Beleg per Email versenden" doesn't make much sense if you want to refer to the history of calculations. |
Obviously I'm not a german speaker, if you think it's more consistent, please go ahead and make the changes. Thanks |
I’m intending to update the following remarks as I work through additional files: English (U.S.) Terms
German TranslationsAppLocalizableBasic and MainI’m not sure in what context “Basic” and “Main” would appear. I’m assuming as themes. In that case, they could be translated as prefixes “Grund-” and “Haupt-” to “Schema”, as in “Grundschema” and “Hauptschema”. By themselves, it’s difficult to translate them as distinct terms, i. e. not using “Standard” over and over. ModelAngleMilI think Mil could be translated to “Artilleristischer Strich” (“Artilleriepromille” in Switzerland). However, this would make it more ambiguous, as 6400 units equal 360 degrees due to rounding. AreaacreAcre could be translated to the old fashioned “Acker”. But as “Acker” hasn’t been standardized, it would make it ambiguous. MassPound vs. “Pfund”Pound could but should not be translated to “Pfund”. “Pfund” is understood as 0.5 kg. I suggest introducing Pfund separately. German LayoutAppLocalizableFailed to Restore Purchases(Still too wide? Couldn't reproduce.) Show All Conversion Results(Too wide in portrait mode) |
Meter vs. Metre: In the US it shows up as Meter, everywhere else that's in English it'll show up as metre. Basic/Main are both strings used in the Mac version. Main shows up in the "Window" menu and is just the name of the Calculator window. "Basic" shows up in the "View" menu and is basically an option to toggle between that and Scientific mode. Acre/Mil, less ambiguity is best, so maybe leave them as Acre/Mil? Thanks for pointing out the strings that are too wide, I'll take a look at them. |
Basic/Main: Looking at the Mac app now, I translated Basic to “Standard” (#36). As for Main, wouldn’t it make sense to rename it to Calculator (“Rechner”)? I tried to find other apps using Main. I’m sure they exist, but I couldn’t find one right away. However, I noticed that almost all just name the windows somewhat less generic (after the app or after what’s displayed in them). Else, I would translate it to “Hauptfenster”[as was done in #43]/“Haupt-Fenster”, as in Main Window, which—I’m suspecting—would then have to be adjusted as well (in order not to state “Haupt-Fenster Fenster”). |
I’ve managed to reintroduce myself to the context again. Before I jump ahead and look through everything I haven’t been able to, I need some clarifications about some changes I noticed. It seems that “Imperial” is handled differently. I also noticed that on an iPhone 5s (Build 36081) any indication about differences is absent. |
US version will never have a "modifier" as part of it. So a "Gallon" is always considered a US Gallon, unless it's a UK Gallon in which case it'd have that "Imperial" modifier. Not really any ways around that without I'm guessing a good deal of changes. The symbol abbreviations for US are fine, I don't think folks will confuse gallon for gram in context, and those need to be short. That being said they aren't getting localized which is a problem and I'll have to get it addressed in a future update. Ugh. |
Hi Would it make sense to work with superscript and footnotes or things like macrons and/or carons to indicate imperial units? I'm not sure if any of the signage out of the Unicode Set might come in handy. Just as food for thought...
|
If I understood you correctly, I have removed all “(US)” specifiers in the German translations [89c76d8], so that it doesn’t all of a sudden say “Gallone (US) [Imperial]”. As long as both versions (“Gallone” and “Gallone [Imperial]”) are side by side, it’s not too ambiguous. |
Sorry for the late reply, there's a new build working its way through TestFlight review. Should be available sometime tomorrow. |
Thank you. It looks pretty good, in my opinion. Of course, some of the units’ full names are quite small. Since the Apple Watch is now also available in Switzerland and I was lucky to get one on launch day (6/26), I'm able to test it there as well. (I love Tip Calc!) Also, I'm having an issue in the iOS app (21007) unrelated to localization. The title for Tape/History doesn't switch correctly. Same thing for the corresponding Clear/Email Tape/History menu entries. |
German localization - Use this to coordinate your work, probably best to work on one strings file at a time.
The text was updated successfully, but these errors were encountered: