Slightly off-topic but it may be helpful if we can find a way to tell users that the current locale is not for example 80% translated, such as adding an (Incomplete) / (Inactive) mark to the menu items in locale selection from Preferences > Interface, especially for those are already included in that menu but < 80%.
2020年11月3日(火) 2:01 James Crook <[email protected]>: > I've added the four new (inactive) translations into the inactive folder. > > The criterion for adding a new translation to active source is 80%+ > translated. > Demotion to inactive may happen if less than 50% is translated. > > I've not added the transifex be,km,lt or oc to inactive (or elsewhere). > They already have partial translations in audacity source. Those transifex > alternatives to what we have will be lost. If we get a new translator for > those languages they can start from the versions which were actually > submitted to Audacity by translators in the past. > > If someone disagrees with that policy of just ignoring those four partial > translations, the solution is to 'become the translator' for that language > for 3.0.0, and after string freeze, submit the po file here. > > Thomas, thanks for your work on this, and sending me the files. > > --James. > > > On Sun, 1 Nov 2020 at 15:16, Thomas De Rocker <[email protected]> > wrote: > >> Hi James >> >> My answers are marked in yellow. >> >> Regards >> >> Thomas >> >> ------------------------------ >> *Van:* James Crook <[email protected]> >> *Verzonden:* zondag 1 november 2020 14:24 >> *Aan:* [email protected] < >> [email protected]> >> *Onderwerp:* Re: [Audacity-translation] New translation for Audacity >> (exported from Transifex): Breton >> >> Thanks Thomas. >> I'll take it to the rest of the developer team and get back to you. >> >> We might decide on a cut off to be added as a new language, and a >> different (lower) cutoff for being dropped. >> >> Ok, sounds like a good solution! >> >> On Sun, 1 Nov 2020 at 12:30, Thomas De Rocker <[email protected]> >> wrote: >> >> Hi James >> >> I understand, but then the same goes for these languages that are already >> present in the sourcecode, for example: >> >> Afrikaans (af): 12 % >> Bulgarian (bg): 33 % >> Bengali (bn): 1 % >> Bosnian (bs): 17 % >> Welsh (cy): 7 % >> ... >> >> I know it's not optimal, but in my opinion, it's better to have a partial >> translation than no translation at all. Especially for people who grew up >> never learning English. It will make more software accessible for them, and >> it will attract other translators for that language, too. Seeing a partial >> translation made me want to translate Audacity and VLC Media Player. >> >> >> But I think for you, seeing no translation would also have done that. That >> would probably be true 😅 >> >> Given your concerns, and that transifex actually deletes the work,(to be >> clear: the translations teams were deleted from Transifex by me, to clean >> things up. Transifex will never delete translations by itself) I'll add >> an 'inactive' subdirectory to locale. Perfect! Bengali at least really >> should be there. If you off list send me the po files for the others, I >> can add them there until such time as we gain an active translator for >> each. Ok, I will resend the .po files for the new and updated languages. >> >> >> >> >> >> About the other arguments: >> >> - *With no team/translator behind it, we additionally can't ask for >> fixes to problems**.* What kind of problems are we talking about? >> >> Ah! I had mistakenly thought items which had become fuzzy translations >> might get used rather than being automatically discarded. And that would >> be a problem with no translator around. Also, as far as I know, >> Transifex doesn't use "fuzzy" translations because it uses its built-in >> translation memory instead. >> You're right. We only need to contact active translators for problems >> that are new. >> >> >> - *A new translator has to check all the existing translations >> anyway. The extent that '57% translated' helps them is much much less >> than >> it seems. My partner has worked as a translator, and does not like jobs >> where she is asked to correct someone else's translations. *True, >> correcting existing translations can be a tedious job. I've done it many >> times in the past. But... it will take less time than starting from >> scratch, and ideally, the existing translations are correct (or the >> quality >> is good enough to leave them be). >> >> Eventually, it's a choice that the developers have to make: >> >> - Add every translation to the source code (independent of % >> completed), or >> - Only apply translations with e.g. 80 % completion and make the >> other translations invisible in the software. >> >> Either way, I would add the new translations to the source code to make >> sure the efforts of previous translators aren't in vain (except maybe the 1 >> and 2 % completed ones) >> >> >> I understand your concerns. Hope the approach above is good. >> >> Sure! >> >> --James. >> >> >> >> >> Regards >> >> Thomas >> >> _______________________________________________ >> Audacity-translation mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/audacity-translation >> > _______________________________________________ > Audacity-translation mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/audacity-translation >
_______________________________________________ Audacity-translation mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/audacity-translation
