2. Go Map!!

Changes committed 5 hours ago

Changes committed 6 hours ago

You should not translate anything bracketed like @foo@. You can translate the comma between them if appropriate. "%1$#@meters@" is a reference to another string which will contain the actual translation, in this case "%1$.1f meters".

10 hours ago

Should we translate this? How to understand (parse) this string?

10 hours ago

English Czech 54 characters edited Current translation Translated 10 hours ago

English Czech 54 characters edited Current translation Translated 10 hours ago

English Czech 12 characters edited Current translation Translated 10 hours ago

English Czech 12 characters edited Current translation Translated 10 hours ago

English Czech 39 characters edited Current translation Translated 10 hours ago

English Czech 38 characters edited Current translation Translated 10 hours ago

Strings containing numeric value interpolations (e.g. "%ld nodes") have now been updated to have singular/plural forms. Don't expect to see this in every situation because in some cases the values are virtually always large numbers, so those are omitted from special treatment.

8 months ago

Hi everyone!

Thanks for all the translation work done so far., it's much appreciated and very exciting to see.

The most recent TestFlight release contains the translations so far for you to try out.

Please file bugs, or e-mail me directly, about translation issues or poor text layout.

Bryce

3 years ago

Hi everyone!

Thanks for all the translation work done so far., it's much appreciated and very exciting to see.

There were a couple issues that were preventing me from integrating the XLIFF files you produced, but I have manually fixed the errors and hopefully things will go more smoothly in the future.

The next TestFlight being released very soon (Version 1.9.8) will contain the translations so far for you to try out. Please feel free to file bugs (https://github.com/bryceco/GoMap/issues), or e-mail me directly, about translation issues or poor text layout.

Bryce

3 years ago

Hi everyone!

Thanks for all the translation work done so far., it's much appreciated and very exciting to see.

There were a couple issues that were preventing me from integrating the XLIFF files you produced, but I have manually fixed the errors and hopefully things will go more smoothly in the future. Two important items regarding the output XLIFF files:

• There are a number of tags of the form target-language="foo" spread throughout the file. For some language files the target langauge was being set to "en" rather than the proper target language code. Please ensure your translation tooling sets these tags correctly, and if it doesn't please correct them manually using a text editor.

• If you don't have a translation for a string please don't enter an empty string for the translation. Blanks will remain blank in the app rather than falling back to English. In the XLIFF the <target> tag should be ommitted completely if the translation doesn't exist.

The next TestFlight being released very soon (Version 1.9.8) will contain the translations so far for you to try out. Please feel free to file bugs (https://github.com/bryceco/GoMap/issues), or e-mail me directly, about translation issues or poor text layout.

Bryce

3 years ago

Hi everyone!

Thanks for all the translation work done so far., it's much appreciated and very exciting to see.

There were a couple issues that were preventing me from integrating the XLIFF files you produced, but I have manually fixed the errors and hopefully things will go more smoothly in the future. Two important items regarding the output XLIFF files: * There are a number of tags of the form target-language="foo" spread throughout the file. For some language files the target langauge was being set to "en" rather than the proper target language code. Please ensure your translation tooling sets these tags correctly, and if it doesn't please correct them manually using a text editor. * If you don't have a translation for a string please don't enter an empty string for the translation. Blanks will remain blank in the app rather than falling back to English. In the XLIFF the <target> tag should be ommitted completely if the translation doesn't exist.

The next TestFlight being released very soon (Version 1.9.8) will contain the translations so far for you to try out. Please feel free to file bugs (https://github.com/bryceco/GoMap/issues), or e-mail me directly, about translation issues or poor text layout.

Bryce

3 years ago

Hi everyone! Thanks for all the translation work done so far., it's much appreciated and very exciting to see.

There were a couple issues that were preventing me from integrating the XLIFF files you produced, but I have manually fixed the errors and hopefully things will go more smoothly in the future. Two important items regarding the output XLIFF files: * There are a number of tags of the form target-language="foo" spread throughout the file. For some language files the target langauge was being set to "en" rather than the proper target language code. Please ensure your translation tooling sets these tags correctly, and if it doesn't please correct them manually using a text editor. * If you don't have a translation for a string please don't enter an empty string for the translation. Blanks will remain blank in the app rather than falling back to English. In the XLIFF the tag should be ommitted completely if the translation doesn't exist.

The next TestFlight being released very soon (Version 1.9.8) will contain the translations so far for you to try out. Please feel free to file bugs (https://github.com/bryceco/GoMap/issues), or e-mail me directly, about translation issues or poor text layout.

Bryce

3 years ago