Translating VicuñaUploader
Java based MediaWiki/commons uploader. Uses a supported format for localisation strings.
- https://commons.wikimedia.org/wiki/Commons:Vicu%C3%B1aUploader
- https://github.com/yarl/vicuna
- https://github.com/yarl/vicuna/blob/master/src/cuploader/text/messages.properties
After speaking to the user in #wikimedia-commons, they are interested in getting it translated too.
https://commons.wikimedia.org/wiki/User:Yarl Yarl on freenode too
What's needed to get this onto TranslateWiki? :)
Probably Siebrand will now review the i18n features in the code to ensure it can be successfully translated; the project is obviously interesting. Have you read translating:New project? Two things I can probably say myself.
- You need message documentation, I don't see any.
- Have you fixed the bugs/missing pieces reported on the Commons talk?
Small issues from quick review:
- Can you remove the <html> wrapper? That makes it easier to translate.
manual-2 = <html>Fill fileds singly or select files and edit them in a group (Ctrl+E)</html> manual-3 = <html>Select which files you want to upload, Ctrl+Shift+A selects all</html>
- On "(Ctrl+E)" and "Ctrl+Shift+A": Is this correct in Linux, OSX and Windows?
- Can you use XHTML breaks (also in other messages)?
fileedit-num-format-tooltip = Variables:<br>%NAME% - file name<br>%N% - number
- Can you simply use the characters instead of the entities •?
fileedit-coor-info = Insert coordinates. Examples:<br>• 52.2299;21.0628<br>• permalink from OpenStreetMap or Wikimapia<br>• {{Coord|52|14|5.15|N|21|7|51.91|E|region:PL}}
- Why use pl_PL for Polish instead of pl?
- This doesn't really scale for all 7500 languages in the world. We will not support these translations. I suggest you integrate CLDR data in your app, or find another way to get this localised.
#context menu 3 file-wiki-de = Add German description file-wiki-en = Add English description file-wiki-fr = Add French description file-wiki-es = Add Spanish description
Looks simple enough, and the file format is supported. I still have to read up on functionality and have to decide if this tool looks promising enough. Thanks for your request.
* Can you remove the <html> wrapper? That makes it easier to translate.
Done
* On "(Ctrl+E)" and "Ctrl+Shift+A": Is this correct in Linux, OSX and Windows?
Definitely correct on Win and Linux, OSX got Ctrl and Shift keys, so there should't be any problems.
* Can you use XHTML breaks (also in other messages)?
Done
* Can you simply use the characters instead of the entities •?
Done
* Why use pl_PL for Polish instead of pl?
Done
* This doesn't really scale for all 7500 languages in the world. We will not support these translations. I suggest you integrate CLDR data in your app, or find another way to get this localised.
I'm not sure if this is what you mean, but I can ensure that there won't be file-wiki-ml = Add Malayam description, These texts are for context menu for file description [1], and it adds eg. {{en|}} templates. If someone wants to add more templates, he can do it in Settings page
![[1]](http://i.imgur.com/qrTW1.png){kind=link}
There's no good reason to favour some languages over others: people will of course tend to manually add more to the code manually, which doesn't make any sense. Therefore Siebrand suggested to load language names from the standard CLDR code, which would allow you to support all of them at once. (Unless I misenderstood.)
Thanks for looking into all this. There's one thing I overlooked in my first pass: All files we support must be UTF-8 encoded. It looks like you're using ASCII. Please look into converting when building your app. You may want to look at the FreeCol code, because as far as I can tell, they're also doing that...
We'd need someone to write the configuration for adding this product (in Wikimedia namespace). Reference commits:
This would speed up the process considerably, because if I have to do this myself, I don't know when I get to it. FrontlineSMS (accepted, to be enabled) and Fina2 (to be reviewed) are in the queue before this.
gerrit:36518 configures almost everything on our side. Todo are:
- Adding the project to the main page templates.
- Adding a description page for the logo.
- Creating Translating:VicuñaUploader and a redirect from Translating:VicunaUploader to there.
- Creating Template:User_VicunaUploader for Babel templates.
- Categories that belong to the project's pages.
These should only be done when I have push access to the repo, the files of the product are UTF-8 and the project has been enabled.
Please give me commit access to your repo and please confirm that your .properties files are in UTF8 now.