I am now āinā at Transifex and will be updating in coming days.
Do you have any date of your next update release?
Iāve also picked up the Canadian and Aussie language files alongside the UK and US.
4 Likes
No. The plan is currently to go for a 2.3, which we will do once we think we have enough features ready and it is time to ship again. So we are talking about longer, and also there will likely be string changes. I donāt want to have long delays like in the past where we had a year or more between releases. But > 2 months for sure, maybe longer.
If we get some issues that require a faster fixing we could slip in a 2.2.2 release (also it is a nice version number).
3 Likes
The Transifex site is surprisingly easy to use. That means ācolourā and ācoloursā have been corrected for UK, Australian and Canadian English.
I think it is booked in correctly, but having never used the site before I cannot be sure.
A different typing error has been spotted and corrected in translation. I cannot edit the US English original, but a search for āoccuredā with one ārā will show up a mistake that needs correcting to āoccurredā with two rās.
I also notice that English (Australian) is a language available for translation, but it does not appear in the list of available languages within Picard.
I will be doing a much deeper read and check of these language files, but for now I think those corrections should be available for any 2.2.2 release.
6 Likes
Thanks, I fix āoccurredā.
The correct way would be to actually add a English (US) ātranslationā, currently this does not exist as such.
This is because we only inlcude languages that are reasonable complete. We have low standards here, as I think a partial translations helps users already and maybe encourages some to help improve the translation. But still I think the last time we went for at least 40 or 50 percent translation. This doesnāt make much sense for Australian English, as this can be seen more like an extension of the existing default texts. I could forcefully include it, but currently it also does not seem to provide much value except the fixed typo you mentioned (https://www.transifex.com/musicbrainz/musicbrainz/viewstrings/#en_AU/picard/157984455?q=translated%3Ayes)
1 Like
The strange side of āEnglishā translation from a US original is that they will never be complete. No need to be. There literally is only a very small number of words that the Americanās spell incorrectly.
Words like āColour, Licence, Practiceā are all that need to be corrected. There is no point in blindly copying over every sentence that would stay identical. That just leads to transposition errors creeping in.
The Australianās and Canadianās share our Britās native spelling. I donāt think there will be much that is ever different between the three. But we all appreciate not being lumped in with a nation that canāt spell 
So far Iāve given the whole file a speed read through whilst loaded up in a British spell checker. Hence spotting āoccuredā. Pretty sure the most obvious items have been swept up this way.
I will be combing deeper into the file in the days to come, but personally Iād be more inclined to REMOVE more of the untranslated lines to allow the English (UK) file to shrink to only those lines that actually need translation.
2 Likes
Gimme a brake. 
Seriously though, nice work.
1 Like
us Australianās do share the same spelling as the uk but we sometimes use different words to the UK and USA for things like gumboots instead of Wellington boots and so on
2 Likes
I am not denying you USAians your choice of butchering our beautifully crafted language that took us many centuries to steal piece by piece from all our neighbours.
And there is at least one Aussie around here who would appreciate the āuā back in Colour. Gāday @St3v3p - I have now duly noted the requirement of using gumboots in the language file. And you can be assured Iāll be going over the whole US language file with a slang dictionary looking for anything else relevant.
2 Likes
Just in case your head hasnāt exploded yet, we might need to Conversate a little more. You may wish to consider adding the āUrban Dictionaryā to your resources. https://www.urbandictionary.com/define.php?term=Conversate 
TTFN
1 Like
That valuable resource is already in the list. Way ahead of you there. Along with the Oxford English Dictionary. That is rather handy as they will show the differences with that USAian language you speak. (Why is it called āAmericanā when it is only spoken in the āUnited States of Americaā?)
(I am seeing this translation conversation is drifting away from the main Picard 2.2 bug threadā¦ Iām expecting this tangent to be suddenly split away a few posts back ( Around Post 23 or Post 27 ))
2 Likes
@IvanDobsky here is a source for Australian english it is used in the unis and here https://www.macquariedictionary.com.au/ and here is some of our slang some words have different meanings depending on who is asking like old fella it can mean your father http://www.koalanet.com.au/australian-slang.html
1 Like
Thanks @st3v3p, very handy. Iāll give 'em a check through. I was making use of this fella to check up that colour and other words are generally spelt the same as us Brits. https://australiandictionary.blogspot.com/2017/11/is-it-colour-or-color.html
And listened to plenty of McGrath on the cricket commentaries this past summer. 
Hopefully this will go back to being a thread on the forum again soon once @Freso works out the buttons to press. There were valid questions to @outsidecontext lost up there which Iāll otherwise need to repostā¦
2 Likes
Ok. Iāll wait and see what happens.
@outsidecontext I think my question has got lost in this bizarre dance. So Iāll ask again and re-phrase it. 
What is a ācompletedā translation? Do I need to load up every sentence\phrase and copy it across even if there is no change?
90% of USA English is going to be identical. There are only a small selection of words like Colour, Aluminium, Licence, Organise that are affected. It makes more sense to me to be only translating that small selection of phrases to avoid introducing other errors, and to literally save on resources.
If I only translate the phrases that need translation, will this still set the āfully translatedā flag for the language?
Is there a way for me to set a phrase as ātranslation not neededā for those 90% of cases where the English (UK) and English (UK\Aus\Can) require no translation?
1 Like
I donāt think it makes sense to translate all, I would only translate those parts that are actually different. That is much easier to maintain. But of course Transifex will not show the translation as complete. The percentage shows how many of the segments or words (not sure which metric it uses) of the total source have translations. If it is missing it is not counted. Otherwise all translations would be complete all the time 
For us this is not really an issue. We have basically two metrics in play:
-
When we update translations we only synchronize translations that are at least 5% complete. That shields us from those empty translations that are not really useful. Everything above this we synchronize with the Picard source code. But we can also manually synchronize the files, and since the English spelling variants donāt change often Iām fine with just syncing them manually from time to time. We could also adapt our sync script to separately sync those.
-
We donāt enable all languages for selection in the options, to have at least a minimum of UI coverage. If the user selects a language we donāt want them to search for something translated in the UI, they should at least see parts of it translated. If you change language and nothing visible gets translated thatās frustrating and not understandable. If you see at least parts translated you can understand that translation is incomplete, maybe you even look into helping translate it.
Currently we take translations into the UI if they are at least 40% complete, but this is just some arbitrary threshold really. This is also manual, not something automated so does not apply for the case here.
In general I would like to improve the visibility of the translation thing and get more people contribute translations. We have many translations that where created years ago and maybe once even where in a good shape, but are now rotting away slowly. But it is no surprise, we donāt make it easy for people to discover that they can help translating.
Iām thinking about a contribution page with details on how to do translation on the website and some links to it from inside the application. Especially if you choose a incomplete translation there should be some hint for the user that they can help improve it.
2 Likes
Excellent. We are on the same page. That is what Iāll be doing. Whilst making sure the file gets past your āat least 5% translatedā level.
I will be doing a direct compare offline, but I am pretty sure there is nothing major that will change between UK\Aus\Can. Once I have confirmed that, Iāll be pulling all three into line so they are clones of each other. Making them easier to maintain. This also means they may well shrink in completeness if I sling out blocks that donāt need translating.
First stage - make them correct translations. (Already improved from what was previously there.)
Second stage - make them more inline with each other. (Take a few more weeks to comb through.)
Yeah, that logic makes sense. Iāll now make the offical request to āEnable Australian Englishā as I know there is at least one person who will be using that. And there are Canadianās around the forum too. We all like avoiding that Broken US English. 
LOLZ - that is why I was trying to get us into our own thread. And then we fell down into a Discourse black hole. 
The Transifex site is a comical combination of incredibly geeky to make sense of, whilst being comically simple to work with. I donāt yet have a clue as to what most of the site is up to, but I have successfully used the built in GUI to correct the three relevant languages.
I assume I am mainly supposed to focus on only the āPICARDā file and ignore everything else like Android Apps and so forth. (Though I did correct āLicenceā in the āServerā text file)
The Australian English file is only ā1.4% translatedā. And yet it looks like it is probably the most correct English file there.
The only strings translated in the Australian version are the strings that actually need translating. Which makes it much easier to check.
The UK and Canadian versions are full of text just copied from US to UK without change. Artificially bloating the file and the ācompletenessā stat.
If it is okay with you @outsidecontext, I will strip the UK and Canadian versions back to the same levels as Australian. This makes the stats look āoddā but is more correct. It also makes the language file much easier to check through.
Another time Iāll go through the online manuals for Transifex and see if I can find a way to tick off the items that donāt need translation so that percentage can come up a bit.
-=-=-
Meanwhileā¦ I have found a place where those Crazy Canucks use USA spelling for words like customise\customize. Need to check deeper on that one, but is a good divergence from the US and UK versions.
This is a handy resource as it picks out those US \ British \ Canadian differences
https://www.lukemastin.com/testing/spelling/cgi-bin/database.cgi?database=spelling
1 Like
Already done
Iām fine with this, makes sense.
1 Like
Excellent. Bruce, Sheila and the Kangaroo 
will be happy to get rid of that broken English spelling.
I also promise not to add any cheeky references to Broad, Archer or Stokesā¦ ( 
)
As an Engineer, my Dad taught me to write U/S onto kit that is broken or UnServiceable. Which does make me laugh when I see English (US) as it is an accurate description
I will also be stripping back those UK and Canadian version at the weekend. Make the differences much clearer then. It will have a comedic effect of looking like I had done LESS translation at the end of this task than when I started.
4 Likes