Closed marc-medley closed 9 months ago
@marc-medley Thank you Marc, I will create apks for the testers in the coming days.
@slavick A German translation which has been reviewed, updated and supports both platforms has been added. The Brazilian Portuguese has been updated for the region.
The attached android-resources-de-en-he-pt-ru.zip
file:
keysExpectedXml*.txt
)Android XML resource files: android-resources-de-en-he-pt-ru.zip
Please let me know if you find any issues with the set. Thanks.
Translations are now being provided via Pull Requests, so this issue no longer needs to be open.
@slavick The attached
android-resources.zip
file contains Nutrition Factsstrings.xml
translations for Hebrew, Portuguese, Portuguese (Brazil), Portuguese (Portugal) and Russian.android-resources.zip
Please check if these files work OK with the Android software. Let me know if anything is missing, incomplete or broken. See details below.
Also, if the Android app builds OK with these xml files, would it be possible to provide a test (non-general-release) build for the translators to review?
Thanks.
Details
The files are also located here:
The files were programmatically generated from the TSV files provided from the translation team. There were no subsequent hands edits done to the
strings.xml
files.The translated
strings.xml
is created by mapping the Android keys from the translated TSV file to overwrite values of an in-memory copy of the English_USstrings.xml
A (re-generated) English_US
strings.xml
is also include to give an idea of how the formatting is affected through the process.The English_US
strings.xml
file is used as the base reference to provide the following:<item />
may have the form<item/>
or<item></item>
Observations: Things to Check
An effort was made to use the same translated text for both Android and iPhone where possible. There may be some unexpected issues which need to be addressed.
\'
escaped programmer style quotation characters in the text body.activity_welcome_text
is longer than what is on the main branch. Was this shortened for the Android release based on space constraints?\n
carriage returns work OK for Android.$
argument index is present in the current main release branch forformat_version
andformat_num_days
. Would it be reasonable to adjust the Android java code to not need the argument index in the translation string? If yes, then the same translation TSV row can be used for both Android and iPhone.prior version
current branch
%s
strings are programmatically generated base on a string differencing algorithm the corresponding imperial and metric TSV rows. Basically, two imperial/metric TSV rows (equivalent to two imperial/metric iPhone JSON entries) maps to three<item>
s in Android. This may look different than expected in the xml; however, the parts should combine correctly in the running application code.For example: