search

nutritionfactsorg / daily-dozen-localization

Repository to help coordinate translations for Apple and Android Daily Dozen apps.
5 stars 3 forks source link

Chinese, Simplified: translation #17

Open marc-medley opened 2 years ago

marc-medley commented 2 years ago

@salitrov The "Chinese_Simplified/tsv" spreadsheets to use for the simplified Chinese localization are listed below.

Content Translation

The lang_value column needs to be updated with the Chinese orthographies.

Web Page Localization

The lang_value column needs to be updated with the appropiate url segment or be emptied where the English_US URL fallback is not to be used.

"Tech Note: Daily Dozen Mobile Application URL Localization" provides translator level documentation for Daily Dozen mobile application URL localization.

marc-medley commented 1 year ago

@salitrov The changeset01 tsv files contain some addition lines which need translation to support the addition of Google Firebase Analytics to the application, translator recognition, and the cruciferous servings update.

salitrov commented 1 year ago

Hi Marc, please find the Chinese (Simplified) updates attached.

Chinese_Simplified_zh-Hans.changeset01 - Chinese_Simplified_zh-Hans.changeset01.txt Chinese_Simplified_zh-Hans.appstore.changeset01 - Chinese_Simplified_zh-Hans.appstore.changeset01.txt

marc-medley commented 1 year ago

Note comment on translator contribution list in Translator Recognition issue #16

marc-medley commented 1 year ago

@salitrov Chinese_Simplified translation Change Set v03 baseline is available here:

marc-medley commented 1 year ago

@salitrov The text needed to support the data export and import on the iPhone Daily Dozen app is ready for translation. Thanks.

marc-medley commented 7 months ago

@salitrov Below are the version v05 Chinese (Simplified) app and store files as currently in the repository. These files will be updated when a Chinese (Simplified) translation is available.

salitrov commented 7 months ago

Thanks! Are we able to just adapt the sheets we're using for traditional rather than using these? Converting TC to SC should be a simpler process as they're already in there. If for some reason we should use these versions instead, let us know.

marc-medley commented 7 months ago

@salitrov

Converting TC to SC should be a simpler process as they're already in there. If for some reason we should use these versions instead.

The following files have been updated to use TC as the basis for SC:

It is important that the filenames for Simplified translations retain a distinctly different filename from the Traditional translation files.

The previous SC versions now contain *.was.tsv in the filename: