Translation process(es)
Hugo Lopes
I've noticed that there are some strings on the lastest subversion
revision that have no portuguese translation.
I used to update the strings.xml file directly and commit the changes
using subversion, but now that ASK is using crowdin for the
translations I've submited my translation to the site and don't know
what is the preferred way to update it.
I was frustrated with crowdin in the beginning after trying to
translate directly on the site, since for me it is much more efficient
to edit the XML files directly... until I found out that you can do
that and submit the complete translated file using the "+" icon on the
Actions column.
I used to compare the subversion english strings.xml with the
portuguese version maintaining line order and blank lines so that each
line had a corresponding translation. I can do the same downloading
the english file from the crowdin site, since the files seem to
maintain the same order for the string keys and there are no blank
lines, so they are easily comparable... but there are strings that are
not yet on the crowdin english file, so they cannot be translated
there. These are the missing ones I've noticed:
fullscreen_portrait_input_connection_supported*, hardware_keys_group
and use_user_dictionary*.
I think we should establish some translation guidelines and guarantee
that the latest version of the strings file is always on crowdin, and
that the latest version of each translation is always used on each new
market version. If possible an email message should be sent to the
translators one week or more before a new market version, so they have
time to add the missing ones.
I can create a page on the wiki documenting all this process. What do
you guys think?
--
Hugo Lopes
