Skip to content

Tasks & Notes for Project

Jump to bottom
MarkH edited this page Jan 15, 2014 · 9 revisions

==== Add current tasks list here ====

  • Inspect all arrays string data for things which are not translatable e.g. @drawable/btn_check_on_pressed_holo_light having these existing in values-ms as well as values will cause problems in the ROM when built. Review all files with non-translatable elements and decide strategy around this.

  • Merge the 70% translations from previous repo and then translate the remaining 30% on this official repo as a priority. (Merging is ongoing, ensuring all strings are correctly assigned or commented when missing translations).

  • Make note to localise translations to values-ms and values-ms-rMY if Malay is going to be imported as a secondary language to the values repository. If applicable, refactor values->values-ms etc.

  • i18n_miui / aries / packages / providers (to be translated where applicable).

  • i18n_miui / aries / packages / wallpapers (to be translated where applicable).

  • Merges for app packages in i18n_miui / aries / packages / apps (70% XML available to merge with Meld).

  • Merges for i18n_miui / aries / frameworks + review of strings / arrays files to be translated.

  • Check any image assets which may be worth editing (PSDs are available).

==== Things to note ====

  • When making git commits ensure you are not committing minor changes, try to batch changes by package so it is easier to track the commit history of each translations progress. This will also ensure Internal checking can be carried out on a per-package commit basis. Clean-ups should be done in batches (e.g. typographic errors and so on). Also ensure small and meaningful commit messages when adding to the project. (Use extended descriptions to further explain the commit in detail, any issues or points of note e.g. Started check at Line [x] and left off at line [y]).

  • Strings with only variables and xliff data sections and no text elements should be left in the order they are written in as they are for system functions. These will generally be commented as or similar notes above the string node.

  • Do not translate the name="some_system_tag" part of the XML file, doing so will cause the build system to reject the XML and will likely fail quality control before build anyway.

  • Make sure all string nodes remain in the same position after editing, tab spacing etc must be maintained.

  • Refer to this guide http://developer.android.com/design/style/writing.html for writing styles for Android best practices. Personal touches are OK but should remain within the Android guidelines.

Clone this wiki locally