I'm the maintainer of a free/open software platform for reviews, called lib.reviews. We're currently in invite-only mode, but invites are available for the asking. The software is under CC-0 (the used libraries are under various other open source licenses), the review content is CC-BY-SA and the metadata for items to be reviewed is under CC-0. For more on the terms of the platform see: https://lib.reviews/terms
I've tried to develop with i18n in mind from the beginning, and there's currently a German version alongside the English one. I use the i18n package for Node.js. By default that package encourages the use of messages-as-keys, but I'm following the convention of separating keys and messages. The package supports multiple plural forms using CLDR conventions, as implemented by its make-plural dependency.
The message files are in JSON format, found here. As you can see there's already a complete qqq file for message documentation. I also use the README page to document translation conventions.
A couple of people have already offered to work on translations and I'd love to point them to the translatewiki.net platform for it. In addition, any help from the TWN community would be very much appreciated. You can read a bit more about the motivation behind this project here.
Are there any obvious blockers for using TWN for internationalization, and if not, could you advise me on next steps? :)
This all sounds very nice! One note: is it possible to use UTF-8 encoding? I am seeing html entities in the German translation.
That was just me being lazy (umlauts are annoying to type on a US keyboard); I just converted them. I just double-checked that all content is served as UTF-8 including API responses and Atom feeds.
Nikerabbit: Checking in (& hope you're feeling better!) -- anything else I can do right now to help move this along?
I'm recovering. Quick note: consider using Unicode CLDR for language names to avoid repetition in their translation. Oh, and what about RTL languages?
Other than that, it is on my queue for new project addition which is again backlogged. For that you can already start preparing the basic information:
- Project name
- Logo (optional, svg preferred)
- Project page in Translating namespace
- Short description that will be placed in Group_descriptions.
- GitHub push access for me and Siebrand
That's a good point re: CLDR. I've filed a bug for that and will get to that shortly.
Re: right-to-left-support, what I'd suggest is: 1) Once we get any RTL translation, I will add the basic LTR/RTL directionality markers alongside activating it. That part, I think, is relatively straightforward. 2) I will, however, need help from an actual speaker of the language, such as a translator, to verify that everything is done correctly, and to identify additional issues to resolve. Does that approach seem reasonable?
Here's the requested info:
Hello, is TranslateWiki a project which accepts new projects for localization? I see at least two open requests and both are waiting for approval by the founder of this wiki, Nike, who is probably busy and hasn't answered for several months. Is there someone else who can help on this thread? Thank you all,
Перевод статьи с русского на французский Translation an article from Russian to French
Здравствуйте! Я бы хотел перевести и опубликовать одну статью на русском на французский. Помогите, пожалуйста, разобраться, как это сделать.
Hello! I would like to translate one article in Russian into French. How can I do that? Tnanks!
Sorry, I didn't understand even after reading your link. I have a translation done in Word document.
Now I try to find something like add a translation or download a document, but I can't find it... Can you help me here, please?
I've sad news. One of the most active translators on translatewiki, user:Purodha, has died on August 25th. See these pages on German Wikipedia:
Unfortunately I don't know where to post this message.
Rest in peace!
Someone within the project NOCC isn't respecting the translations properly done and are replacing them the way he likes to translate / see.
That is wrong and is bad example.
Seems like someone created a template which require a Lua module, I'm not sure if there's one who against this or not.
Is it possible to enable Yandex Translate suggestion for bengali (bn) in this wiki?
However I can't see whether $wgTranslateTranslationServices['Yandex']['pairs'] is customised on this wiki.
What is the issue? Do not that it is soon changing to publish changes.
In Gujarati Language this shows in English and I want to change it with Gujarati.
You can located messages for example with the translation search.
I can't see that message where you sent.
Go to this link and find - Save Changes
So you can see what I want to translate.
The WMF abandoned the Commons app in 2014 and I am now maintaining it (I am only a normal Commons user). I would like to allow users to improve the localizations, as they have not been updated since 2014.
QUESTION: Should I create the localization project on a third-party tool like Crowdin? Or can I somehow "resurrect" the app's localization project here, even though the app is now community-maintained rather than an official WMF app?
If the repository is active, the project can certainly be re-enabled here. These days are quite busy, you may want to send a patch against the "translatewiki" repository in gerrit yourself.
It doesn't matter whether the app is community maintained or not. What is important that the translations end up in front of the users, i.e. for mobile apps there needs to be regular releases.
Nicolas Raoul, I see there are plans for frequent releases. Can you add @Nikerabbit and @Siebrand to the committers so that they can merge l10n updates?
I added both @Nikerabbit and @Siebrand as Github collaborators, waiting for the commits, thanks :-)
I want to publish the translatewiki URL to our users, but where does the localization actually happen? A search does not show any active Commons Android project here.
WLMMobile is a completely different app, with a different purpose (see wireframes), untouched since 2014, and we don't have strings in common.
Could you please create a new project called "Commons Android app" as a sub-project of "Wikimedia Mobile Apps"? I have read https://translatewiki.net/wiki/Translating:New_project and we seem to fit :-) Thanks a lot!
So https://github.com/nicolas-raoul/apps-android-commons the canonical repository now? Nikerabbit and Siebrand will need commit access?
When is the first release planned?
Yes, https://github.com/nicolas-raoul/apps-android-commons is the canonical repository. @siebrand is already a committer. I have invited @yuvipanda and @Nikerabbit for committer access and I am waiting for them to accept the invitation. The app has been released already: https://play.google.com/store/apps/details?id=fr.free.nrw.commons I have signed a contract with WMF allowing me to use the official "Wikimedia Commons" brand name and logo.
Are you waiting for any action on our side? We did everything you asked for, what is blocking? More and more users are asking us where to localize the app, and it is a shame that we have no URL to give them. Looking forward to hearing back from you soon, cheers!
I have been busy. I'll try to re-check the status of this soon to get this sorted out.
On this it says
"an Liability account that is credited on overpayments and credited when refunds are made to client."
particularly it says Liability account is credited in both cases. It is confusing whether both cases is meant to be credited or in one case it is debited. If in both cases the account is to be credited, perhaps it maybe wise to restructure the sentence?
There is a typo in MediaWiki:Editpage-invalidcontentmodel-text/en. It reads: "The content model "$1" is not a supported." while it should read: "The content model "$1" is not supported."
There is a typo in MediaWiki:Tsb-email-promoted-body/en. It reads: "Welcome, and thank you for you contributions!" while it should read: "Welcome, and thank you for your contributions!"
There is a space missing in MediaWiki:Apihelp-aggregategroups-description/en. It reads: "add and remove aggregate messagegroups" while it should read: "add and remove aggregate message groups".
What does parameter $3 indicate in these messages? Is this a username?
The documentation for both messages say that $3 is "the affected page":
I've read the documentation, but yet I did not understand what $3 indicates. What does “the affected page” mean in this case?
How can I see the associated message groups for a specific message?
For example, I want to see which message groups include this message. Is this possible?
Usually I click edit. Now the /en messages are automatically protected, so I go to a translation and see the header "Definizione del messaggio (Echo)".
You can also use the search. Example: https://translatewiki.net/wiki/Special:SearchTranslations?query=MediaWiki%3AJan&language=fi
Accounts can't be deleted either. I can rename that account to a random name though.
I have a small tool and trying to use translatewiki.net to internationalize the messages. How should I do?
I don't know why translatewiki.net has been using the Liquid Threads system in the first place. I assume it was intended to experience and test this "new" system.
However, nowadays this discussion system is barely maintained, because the new "Flow" system took its place.
Due to the lack of maintenance, we're now experiencing a very critical bug. It is very difficult to create new threads, and AFAIK it is not possible at all to reply in an existing thread.
In addition, the Liquid Threads system does not support RTL languages such as Hebrew and Arabic: I.e., every time somebody wants to write in an RTL language, they need to manually add
<div class="mw-content-rtl"> at the beginning of the message; otherwise it's aligned to left, making it very difficult to read.
Apart from the issues written above, there are many more annoying problems with this old discussion system. For example, the "You have a new message" notice keeps appearing even after reading the message. You have to manually mark it as read on Special:NewMessages to get rid of the notice.
Please let me know what you think.
Therefore, I think we need to get rid of the obsolete "Liquid Threads" system, and replace it with the new "Flow" system (or use regular talk pages).
LQT does not support mention notifications, so even if user is explicitely mentioned in thread, s/he doesn't get any notification about that. Which makes it quite hard to join conversations relevant to the user - basically unless the user is explicitely notified by someone involved in the discussion that his/her input is welcome/expected or having such talk page on watchlist, s/he never knows about that. Which may easily result in missing important conversation.
People are used to the fact that if they mention someone, such person is notified. It is not true in LQT but not so many people are aware of that.
Please switch to Flow or regular wikitext discussions, which provide this feature. (Or hack the LQT to do that too...)