It seems to swallow HTML inside the messages, stripping them and their contents out. See message 'Commons-android-strings-about license' in the Android Commons app. Actual english content is 'Open Source software released under the <a href="https://github.com/wikimedia/android-commons/blob/master/COPYING">GNU GPLv2</a>' while content according to Extension:Translate is 'Open Source software released under the '
Description
Description
Details
Details
- Reference
- bz47310
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T68725 Messages with links appear as empty in translatewiki.net | |||
| Open | None | T49310 Translate should not eat some tags inside message contents for AndroidFFS |
Event Timeline
Comment Actions
Need to use the same hack what I used in XliffFFS for this. /me wishes innerXml functionality from Santa.
Comment Actions
According to docs unescaped html is not allowed inside strings, except for b i and u tags.
Comment Actions
Removing easy per my last comment. This is either wontfix or an implementation which only supports those three tags, or I misread the docs http://developer.android.com/guide/topics/resources/string-resource.html#FormattingAndStyling.
Comment Actions
Yes, I was thinking of b i u tags; but we can instead align summary with comment 0 too.
Comment Actions
You are misreading the docs. We are using those strings inside a webview - so we are actually making regular HTML out of them and putting them in. So no need to have it support only 3. You could make it a CData and add 'formatted=false' to fix any issues.
Comment Actions
Ok, wrapping them in CData fixes it for TWN, but not the app - the full HTML unparsed shows up as the text :(
I think, actual fix would be to just support <b>, <i>, <u> and <a> tags. (All of these are supported elements). Anything more complex would be used only in webviews, and CData can fix that.