This is a tracking bug to find out what we need to do to get the Android app on translate wiki.
Version: 1.0.0 (Android)
Severity: enhancement
This is a tracking bug to find out what we need to do to get the Android app on translate wiki.
Version: 1.0.0 (Android)
Severity: enhancement
Title | Reference | Author | Source Branch | Dest Branch | |
---|---|---|---|---|---|
Advance cert-manager-issuers chart to 1.1 | repos/releng/gitlab-cloud-runner!230 | dancy | review/dancy/T334679 | main |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Nikerabbit | T33467 Getting the Android app on translatewiki | |||
Resolved | • brion | T34324 Write yaml definition file for WikipediaMobile on TranslateWiki.net | |||
Resolved | • brion | T34327 Create stub i18n documentation pages for WikipediaMobile on Translatewiki.net | |||
Resolved | • brion | T34326 Update Android app's i18n files to use .properties format | |||
Resolved | None | T34350 Set Niklas up with commit access on Wikipedia Android app github repo |
The current code has ..... no localization support whatsoever. :)
Need to:
For the StatusNet Desktop client (we never did finish i18n for the mobile version) I made a stub library:
using a simple XML key-value file format based on that used by native localization support that Titanium was adding. PhoneGap doesn't seem to have a built-in standard localization helper, so might be good to adapt some of that (there's some basic logic for merging fallback languages iirc).
The key-value format is pretty straightforward and should be easy to adapt to TWN. Or, if there's something TWN already understands natively we could go with that and maybe be easier. :)
Don't TW already support a couple of formats used in Java projects?
FreeCol is one Java project
Seems like an excellent time to help the phonegap project standardize on locale message files.
All the UI is done in HTML/JS/CSS (Phonegap), so Android or Java-specific formats don't necessarily help us...
FreeCol uses simple .properties stringlist files, which are a pretty straightforward format though so we could easily build on that, I think.
(In reply to comment #3)
Seems like an excellent time to help the phonegap project standardize on locale
message files.
Sounds like a nice plan to somewhat helping upstream! :)
There is a Globalization plugin (thanks IBM!) which can fetch some locale information, format numbers & dates etc -- useful!
https://github.com/phonegap/phonegap-plugins/tree/master/Android/Globalization
etc
Nothing there to help with basic strings and parameter replacement though...
I think my inclination might be to snarf the 'Message' class from MediaWiki's JavaScript code and hook it up to a backend that reads strings from .properties files (unless we find a nicer way to do it). We could repackage that as a nice platform-independent lib...
Here's a stub using MediaWiki's existing front-end localization framework. Just uses messages to do the loader dialog, but it's an example of basic param composing and using the framework. :)
Included a messages-qqq.js with descriptions too -- I'm full service!
Shouldn't be too hard to load other languages, and can consider switching the file format around to something TranslateWiki-friendly (it's just a .js stub setting a map as a variable, much like our MessagesXx.php files).
(In reply to comment #8)
-patch, no patch in sight.
What do you mean? We've already merged in brions patch for this. Now someone just needs to tackle the rest of the strings.
Talked with Niklas during triage about what it would take to get this
app on twn with the current messages and he said the “yes but output
would be plain ugly”
https://github.com/brion/Wikipedia/commit/100720287c7ab00d8c21e3831046a0ac67254e7f#diff-5
So do we still need to write an input/output module for Extension:Translate? Any further process to go through with setup?
Ok stuff should be pretty ready to go -- additional things were split out to blocking bugs and have been closed out.
On TranslateWiki end remains:
(In reply to comment #15)
It's now on twn, but I'm unable to export.
You mean unable to push, right?
One more thing: I need a small logo to add this project into the translatewiki.net front page.
Looks like we have a logo on translate wiki : http://translatewiki.net/w/images/thumb/7/73/WikipediaMobile-icon.png/45px-WikipediaMobile-icon.png
Closing. Thanks guys!