<div dir="ltr">Hello translators,<br><div class="gmail_quote"><div dir="ltr"><div><div>
<br>
the translations wasn't really maintained for a very long time until now and although the decision was made<br>
to leave Transifex and get weblate (<a href="https://translate.videolan.org" target="_blank">https://translate.videolan.<wbr>org</a>) I reactivated Tx for the 3.0 translation now.<br>
<br>
The URL is still the same:<br>
<a href="https://www.transifex.com/yaron/vlc-trans/" rel="noopener noreferrer" id="m_8613599896818640526gmail-LPlnk812988" class="m_8613599896818640526gmail-x_OWAAutoLink" target="_blank">https://www.transifex.com/<wbr>yaron/vlc-trans/</a><br>
<br>
But for now these are plans for the future (weblate) and in the meantime
the new vlc 3.0 is getting ready (RC) and need fresh translations.<br>
Some months ago I created my own project on Tx to start the 3.0 translation but since I got access to Yaron-project,<br>
I cleaned up some old translations and unused languages there and revoke Tx for the 3.0 process because it's the fastest<br>
way to get translation and most of the longtime translators are there.<br>
<br>The 3.0 translation use the same pot source
file from the git. Nearly all reported typos (from Tx-reports and the videolan forum)<br>
were fixed. Some big and not so urged fixes (especially this "period in
LONGTEXT variable") were put as an issue-comment there.<br>
<br>
An important rule for the translation workflow on Tx:<br>
Please keep the report issue function here clean for bugs and do NOT
write suggestions or your own thoughts about the sense of the string
here!<br>
No developer will be ever reading this on Tx. Such things had to be
discuss first. Use the <a href="http://forum.videolan.org" target="_blank">forum.videolan.org</a> to publish your ideas.<br>
I already put some important notes for the translators so every entry on Tx, that is NOT a typo or bug, will be deleted!<br>
<br>
<br>
-- what to translate:<br>
<br>
VLC 2.2.x<br>
Actually it's too late to starting with translations/corrections for 2.2.x now, we had some time in the past months for it.<br>
VLC 2.2.8 will be probably the last version from the 2.2 series. But we need this translation for 3.0, so it will be needed<br>
and you can, of course use that translations with the latest vlc 2.2.8<br>
<br>
<br>
VLC 3.0<br>
This is at the moment the most important translation, so focus on this translation at next.<br></div>After a completed translation please check and update the header information or ask the maintainer for it.<br></div><div><div>
<br>
VLSub:<br>
This is not very active in developing at the moment but I forked my own
VLSub version and updated some of the translations from here.<br>
</div><div>You can test you translation with this version:<br>
<a href="https://github.com/mtrz/vlsub/archive/master.zip" target="_blank">https://github.com/mtrz/vlsub/<wbr>archive/master.zip</a><br>
<br>
You can also put the "locale" folder
with the xml langs to the working directory of VLSub and delete the config file (vlsub_conf.xml) from there.<br>
<br>
<br>
WinRT:<br>
This version is receiving translations and some of them were already
included, so it's not usless to do
translations for this version here.<br>I will send complete ones from here.
The store info can be included after the main translation of the app is
finished and MUST be<br>
supported by the webpage. The next version should be released soon.<br>
<br>
<br>
Google Play Info:<br>
This has the lowest priority. Google started to active the
auto-translator on the play page as default in Chrome and that give us
very terrible translations. So this will be collected and send if we
have some more translations complete.<br>
Translate it after the other translations or when you have some time left for it.<br>
<br>
<br>
<br>
For now:<br>
Until the switching to Weblate, I'll collect additional translations on
Transifex to keep them together for switching to weblate someday.<br>
You can also do your translation not on Transifex but keep in mind that
there are already many long time vlc translators and you have to ask<br>
them first if a help is needed. We had some insight about that in the past.<br>
If there's already a team leader on Tx, we just let the leader choose
whether to approve the people on the team because there are many<br>
unqualified translators out there that will cause a lot of headache fixing after some bad or incompatible words.<br>
<div>And some translators can be very stubborn, instead of just
complying with the current way they usually insist on going their own
way and there are translation differences for the same term. We have to
make sure, we are not breaking things apart due to new translators with
different agenda then the current members. So, first ask around BEFORE
you start your own translation!<br>
</div>
<br>
<br>
Thank you for your attention. </div></div></div>
</div><br></div>