nutritionfactsorg / daily-dozen-localization

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

Spanish: translation #6

Open marc-medley opened 3 years ago

marc-medley commented 3 years ago

@christirichards and @angelagvarela, below are some translation topics for your review and consideration regarding the current state of the Spanish translation in the Daily Dozen applications.

iPhone Translation Coverage

The Daily Dozen iOS version 3.2.1 was the first release with an additional language (Spanish). Given the state of the app at the time, there were a couple ways for errors to slip through.

First, the Spanish string changes pull request '#39' provided only 3 of the approximately 30 translation files with user facing text. The largest and most important text was in those three files, ... so, that's OK. The other files were various display, navigation and settings details. I filled in the other 27 files based on what I could see in the Android version.

Second, the Daily Dozen iPhone app needed many significant changes to the presentation logic. Often text was part of the source code and used in the presentation logic. Most of the code logic cases had been found and fixed for Spanish release. About 4 cases were later discovered (and fixed) while working with more recent Polish translation.

In particular, Off and On (keys: reminder.state.off and reminder.state.on) need Spanish translations due to a recent discovery and code fix.

It would be good to have the Daily Dozen iPhone app reviewed/tested by a translator to see if any other details on the various screen needs to be addressed.

Related Technical Note: Daily Dozen Localization Overview for the Apple Platform

Android & Apple Common Phrases

The nutritionfactsorg/daily-dozen-localization repository provides for a tsv spreadsheet translation common to both Android and Apple.

The daily-dozen-localization synchronize process can find differences in common phrases used in the Android and Apple files. The screenshot below shows two example differences. The blue lines on the right-side scroll area of the image highlight where to "scroll to" to find other differences.

Spanish_Android_v_Apple

These differences were found to originate from the Android Spanish string changes #156 and iPhone Spanish string changes #39 pull requests.

The current Spanish translations in the Android and Apple apps has been exported to the following two spreadsheets:

The shown screen capture used Meld to compare the two TSV files. There are also other tools for comparing two TSV files or spreadsheets.

In general, the translations differences may be ok (e.g. accepted synomyms). As a practical matter, someone needs to pick which translation term is used so that any future Android and Apple translations can use a common spreadsheet workflow.

App Store

Spanish_es_appstore.20210309.tsv provides the text which displays in the Android and Apple App stores. Both stores allow for localized text descriptions of the application.

If/when a Spanish translation becomes available for the app store text, then the store page could be updated for the language/region. Translated screen shots could be used as placeholders for localized marketing graphics.

Device Test Feedback

If there is any feedback from hands-on device testing from , that would be useful to know.

marc-medley commented 3 years ago

@christirichards and @angelagvarela, The attached file diff_DailyDozen_Spanish_Android_Apple_20210310.txt contains a summary fo the current Spanish translation differences between the Apple and Android Daily Dozen apps.

The files is derived from the output generated via the terminal command line diff Spanish_es.20210309.Android.tsv Spanish_es.20210309.Apple.tsv. The content lines preserve the tabs used in the translation spreadsheet columns. These lines can be copies & pasted into the Spanish translation spreadsheet.

As FYI, differences with human readable keys like dozeSpices.Variety.Text.17 are likely from differences in the Android & iPhone pull requests. Differences with random keys like Lef-Iw-Ywr.normalTitle are likely from the more obscure "other ~27 localization files" used in the iPhone app.

Future versions of the translation spreadsheets and iPhone source code will phase out the auto-generated random String IDs.

file: diff_DailyDozen_Spanish_Android_Apple_20210310.txt

angelagv commented 3 years ago

@marc-medley To go ahead and unify the translations for Android and iOS and get rid of those inconsistencies, plus add those few strings that were lacking because of the text that was previously part of the source code, what would be the preferred approach? I think I have understood everything that was explained here, but I am now wondering what file I'm supposed to work with and how to proceed. These are the files currently available under daily-dozen-localization/Languages/Spanish/tsv/

image
marc-medley commented 3 years ago

@angelagv Below are some notes on how to proceed with the available files. Please let me know if you have any additional questions. Thanks.

Application

Both Spanish_es.20210309.Android.tsv and Spanish_es.20210309.Apple.tsv have the same sort order, so that they can be compared side-by-side as-is. Also, diff_DailyDozen_Spanish_Android_Apple_20210310.txt in a previous post contains a summary of which items are different between Android and Apple iOS.

  1. Pick either Spanish_es.20210309.Android.tsv or Spanish_es.20210309.Apple.tsv to be used as an edit baseline. Use the other file as a comparison reference.
  2. Rename that baseline edit file to remove the platform part of the name. Use of a date in the filename is optional. For example, the edit file could be simply named Spanish_es.tsv.
  3. Review/edit/update the Spanish_es.tsv in any spreadsheet application which can export TSV.
  4. When done, export to TSV. Add a .txt extension the file. Post the update Spanish_es.tsv.txt to this issue thread.

Once the Spanish_es.tsv.txt is posted here, it will be processed to generate both Android and Apple localization files.

Note: The reason for the .txt extension for upload is that GitHub Issues allows attaching a .txt file but not a .tsv file.

App Store

Spanish_es_appstore.20210309.tsv contains both Android and Apple App Store information fields. Both App Stores currently show English descriptions. This file would be a new translation set to allow the App Store download/install page would be in Spanish.

NutritionFacts Links

Spanish_es_urls.tsv file does not need any attention that I am aware of.

marc-medley commented 3 years ago

@angelagv As FYI, when the unified translations for Android and iOS are recieved, those translation spreadsheets will be processed through some utilities which will:

  1. Update the id mappings to the current Android and iOS internal ids,
  2. runs some additional consistancy and coverage checks, and
  3. generate corresponding reports to indicates if any additional details need to be reviewed.

Also, the right most TSV Spreadsheet column is for notes to help the translator. You are welcome to (optionally) add notes would find beneficial. These notes can be either kept with the Spanish translation spreadsheet or propagated to the other languages as appropriate.

Please let me know if you have any questions or need more information.

marc-medley commented 2 years ago

Fixes in release candidate build v3.2.11(29).

es_info_v3 2 11(29)_snip

es_settings_v3 2 11(29)_clip

marc-medley commented 2 years ago

@salitrov (cc @angelagv ) As FYI, if the Spanish_es.appstore.tsv spreadsheet were to be translated, then the web store product page could be localized. It's a relatively short spreadsheet of 23 rows.

Also, the localization of the keywords could help user search and app discovery for the Spanish speaking users.

marc-medley commented 2 years ago

@angelagv The daily-dozen-localization Spanish spreadsheets have been brought up-to-date.

The NutritionFacts's Android and Apple translation spreadsheets have been merged into spreadsheets common to both platforms, as is the pattern for the other languages.

Since there were some differences between the Apple and Android translations of common elements, a judgement call was on a per row basis of which source to keep. The Report_Spanish_es_android_apple.txt file lists the differences which were reviewed.

A second opinion of the merge choices would be welcome.

marc-medley commented 2 years ago

@angelagv Below are some updates which need need Spanish translation support:

Core Translations. The core Android and iPhone translations have been unified to get rid of inconsistencies between the two devices.

The list of differences reviewed can be found in the Report_Spanish_es_android_apple.txt file.

The resulting Android/iPhone unified Spanish translation is located in the Spanish_es.tsv spreadsheet.

The most visible difference are the choice between ajustes vs potenciadores. ajustes was picked because it used less screen area. Although, ajustes could be switched to potenciadores if preferred.

Android Screen

Apple Ajustes

The choice of cucharadita vs ctda. was also present in several cases. The use of cucharadita and ctda. remains mixed in the unified spreadsheet.

Is the unified spreadsheet acceptable for now? or, should something be changed before it is released? (Subsequent updates are also an option.)

App Store Product Page The app store product page "Spanish_es.appstore.tsv" spreadsheet needs to be translated when time allows.

The store product page can be updated separate from a software release. As such, this effort is non-blocking relative to a software release and can be done as time allows.

Once available, the App Store DailyDozen produt page in Spanish can be fully localized. At the same time, the internet search engines will also have the product keywords in Spanish to help the DailyDozen be more easily found.

marc-medley commented 2 years ago

@angelagv Here is a first look at how potenciadores fits in three locations on an iOS device screen. The capitalization can be adjusted as needed.

Potenciadores_

marc-medley commented 2 years ago

@angelagv Here is a first look at how potenciadores fits in three locations on an iOS device screen. The capitalization can be adjusted as needed.

Potenciadores_

marc-medley commented 2 years ago

@angelagv 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.

angelagv commented 1 year ago

Thank you Marc! Will get back to you on this ASAP.

On 6 May 2022, at 10:50, --marc wrote:

@salitrov https://github.com/salitrov (cc @angelagv https://github.com/angelagv ) As FYI, if the Spanish_es.appstore.tsv https://github.com/nutritionfactsorg/daily-dozen-localization/blob/master/Languages/Spanish/tsv/Spanish_es.appstore.tsv spreadsheet were to be translated, then the web store product page could be localized. It's a relatively short spreadsheet of 23 rows.

Also, the localization of the keywords could help user search and app discovery for the Spanish speaking users.

marc-medley commented 1 year ago

@angelagv Below are the Apple App Store Daily Dozen product pages where the store front translations will go:

marc-medley commented 1 year ago

@angelagv There is some additional text for the Daily Dozen applications which need translation. The addition is described in "ChangeSet03: Serving Size (Suggested) & FAQ #30".

The needed translations are groups in the TSV change set v03 spreadsheets:

Please let me know if you have an questions. Thanks.

marc-medley commented 1 year ago

@angelagv When you have time, there are two change sets which need translation to Spanish for the Android and Apple mobile applications.

Please let me know if you have an questions. Thanks.

salitrov commented 1 year ago

Hi Marc, I'm attaching all of the pending translations for Spanish. I worked with Ángela on prepping the sheets. Let us know if anything else is needed.

Spanish_es.app.changeset02 - Spanish_es.app.changeset02.txt Spanish_es.store.changeset03 - Spanish_es.store.changeset03.txt Spanish_es.app.changeset03 - Spanish_es.app.changeset03.txt

marc-medley commented 1 year ago

v02 and v03 processed ok. thanks.