1,157
edits
Changes
Jump to navigation
Jump to search
Line 9:
Line 9: − + − +
Translation Team/Localization testing (view source)
Revision as of 20:21, 13 June 2011
, 20:21, 13 June 2011→String localized and committedd
If the string is localized in Poolte, next check the PO file in the git repository. If the string is not localized in the version of the PO committed to git, then it will not show up in the build. A language administrator for that language needs to review and commit the PO file from Pootle for it to get into git. Ask on the Localization list if this is the case.
If the string is localized in Poolte, next check the PO file in the git repository. If the string is not localized in the version of the PO committed to git, then it will not show up in the build. A language administrator for that language needs to review and commit the PO file from Pootle for it to get into git. Ask on the Localization list if this is the case.
==String localized and committedd==
==String localized and committed==
If the string is localized in Pootle and git, it still might not show up in the activity if there has not been a build of the activity made since the string was committed to git. In this case, ask on sugar-devel for the activity maintainer to bump the version of the activity and add the new localizations.
If the string is localized in Pootle and git, it still might not show up in the activity if there has not been a build of the activity made since the string was committed to git. In this case, ask on sugar-devel for the activity maintainer to bump the version of the activity and add the new localizations.
There are other less common causes for a string not being localized.
There are other less common causes for a string not being localized.
==i18n error==
==i18n error==