Skip to content
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

Russian Localization #25

Open
tapbots opened this issue Mar 19, 2015 · 6 comments
Open

Russian Localization #25

tapbots opened this issue Mar 19, 2015 · 6 comments

Comments

@tapbots
Copy link
Owner

tapbots commented Mar 19, 2015

Use this to coordinate any work

@inikitin
Copy link
Contributor

@tapbots In 'Power' category, 'Pferdestärke' translates to Russian as "metric horsepower", which is the unit that we already have. They are equal units, so I wonder whether 'Pferdestärke' should be ignored in Russian translation, or if it should be translated phonetically.

@tapbots
Copy link
Owner Author

tapbots commented Mar 29, 2015

I would say add Pferdestärke to the ignore list and just then translate Metric Horsepower as the two separate words "Metric" and "Horsepower"? There's really no way to disable a unit for a particular locale and just can't think of a good way to do that without possibly screwing up a lot of other things.

@inikitin
Copy link
Contributor

@tapbots for some reason, in Typography category all four of 'Pixel' units are still displayed in English, even though they were translated.

Another issue is that (UK) units still have '(UK)' postfix, instead of what I wrote in place of '(Imperial)'. It might actually be better to leave it that way for the sake of brevity, but ideally I could specify 'UK' abbreviation in Russian, so those instances could be fully translated.

@tapbots
Copy link
Owner Author

tapbots commented Mar 31, 2015

Good catch, the modifier type units were all sorts of screwed up on my side of things. I hopefully have them all fixed, give it a look and let me know if there are any issues.

@inikitin
Copy link
Contributor

@tapbots should we translate App/Localizable.string: Watch? If I understand correctly that is a product name reference just like "iPhone", so wouldn't need literal (or any) translation?

@tapbots
Copy link
Owner Author

tapbots commented Apr 26, 2015

I think Watch should be localized, since we aren't saying Apple Watch. Apple seems to do the same thing in the Watch App.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants