Fix untranslatable strings

Fix untranslatable strings

Issue ID:2274
Issue Category:bug
Component:translation
Priority:normal
Status:fixed
Assigned:brion
Version:0.9
Milestone:0.9

There are several untranslatable messages in the software. I have been reporting them to Brion, but I think it's a good idea to list them here as a task for anyone to take care of.
* The most important part is the documentation. There is already a task for it: #2008
* Plugins: that includes "powered by StatusNet", "Flag", the map's "Full size" and OpenID messages.
* The license notice.
* "Other Settings" message in the Account page.

Legacy Data

This issue was migrated from another tracking system. The legacy data at time of import is provided below as a reference.

Ticket ID: 
2274
Reported by: 
OsamaK
Owner: 
brion
Status: 
accepted
Type: 
bug
Component: 
translation
Priority: 
3
Version: 
0.9
Milestone: 
0.9

Updates

#1

"Other settings" seems to be translatable and translated already.

License notice looks like one of those that's broken due to trying to stick variables directly into the string passed into gettext, which of course ain't going to work too well... needs cleanup.

#2

Fix for the footer:

[0.9.x a5cfc39] Fix localization for license notice in page footer (for ticket #2274: i18n cleanup)

#3

Along with adding translator hints in the sources, I'm also auditing the code for i18n/L10n issues. Often I can fix them, and sometimes I have to add a @todo to fix it later. I hope to be able to get more time in the near future to continue the audit more regularly. Core is first, extensions to follow.

#4

Status:active» fixed

Fixed in 0.9.6. All plugins can be translated now, and all i18n issues mentioned in this issue have been resolved. Please create new issues and feel free to assign them to me is you find remaining issues.

i18n/L10n review is still ongoing. Eventually I hope StatusNet will have complete translator documentation and a fully i18n audited codebase. (yay).

Login or Register to modify this issue, or to receive updates by email.

You can also subscribe to the RSS feed for updates to this issue.