OK.  If the Breton translator wants that, then we can look at a developer
making a very special case for Breton.
Let's avoid  "un pansement sur une jambe de bois".

--James.

On Wed, 4 Nov 2020 at 18:54, Olivier Humbert <[email protected]> wrote:

> Hi all.
>
> It sounds like a shaky idea to me. "A bandage on a wooden leg" ("un
> pansement sur une jambe de bois") as we say in French.
> In my opinion, the suggestion made by Stéphane Ascoet a few days ago is
> the best one: make sure that for strings not translated into Breton, the
> fallback language is French rather than English, because as Stéphane
> mentioned, we can count on the idea that 99.99% of people who speak
> Breton also speak French while the percentage of people who speak Breton
> and also English will be way lower.
>
> The thing we would need in this case is a developer willing to make it
> happen.
> @James: could you please bring that idea to the developers team and
> check if someone is willing/able to do so? (if it hasn't already been
> done, of course). Thank you.
>
> All the best,
> Olivier
>
> PS: note that if that's not possible, that is fine for
> my(personnaly)self, I'm just trying to share and discuss ideas here.
>
>
>
> Le 2020-11-04 18:27, Thomas De Rocker a écrit :
> > Maybe I can offer a (partial) solution to this problem.
> >
> >  When using Transifex, strings have 2 "levels" of completion:
> >
> >       * translated
> >       * reviewed
> >
> > If the Breton translation file would be containing both French and
> > Breton strings, it would show as 100 % translated. But...
> >
> >       * if the Breton strings were to be marked as "reviewed" and
> >       * the French strings were to be marked as "translated"
> >
> > it would be possible to see the percentage of completion by looking at
> > the "reviewed" percentage. This has to be done carefully, though...
> > and importing and exporting translation files in Transifex could break
> > this easily.
> >
> > Regards
> >
> > Thomas
> >
> > -------------------------
> >
> > VAN: James Crook
> > VERZONDEN: woensdag 4 november 2020 16:01
> > AAN: [email protected]
> > <[email protected]>
> > ONDERWERP: Re: [Audacity-translation] Audacity-translation Digest, Vol
> > 158, Issue 16
> >
> > Yes.  Which is why it is not simply up to the translator to choose.
> > Yes.  The translation would appear incorrectly as 100% complete.
> >
> > So all in all it's probably a bad idea for our hypothetical Breton
> > translator to decide to put French into the empty places.  Still, I
> > would allow it, if they told me that in their professional opinion as
> > a Breton speaker that it was for the best.
> >
> > --James.
> >
> > On Wed, 4 Nov 2020 at 14:38, Stephane Ascoet
> > wrote:
> >
> >> James Crook :
> >>> I'd assume they know what they are
> >>> doing.
> >>>
> >>> If Dutch had been neglected for a while and a new translator came
> >> along and
> >>> put German translations in for all the missing items, I'd say "NO"
> >>
> >> The situation is completely different since Breton is one of the two
> >>
> >> languages of Brittany, witch is part of france since centuries.
> >> However,
> >> now it's another problem that I can see: if the translator does
> >> this,
> >> the translation would appear incorrectly to be made at 100%
> >>
> >> --
> >> Sincerely, Stephane Ascoet
>
> --
> Site web : https://librazik.tuxfamily.org/
> Donation : https://liberapay.com/LibraZiK/
> Diaspora :
> https://framasphere.org/people/8c184af0c9450134f6682a0000053625
> Mastodon : https://mastodon.xyz/@LibraZiK
>
>
> _______________________________________________
> 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

Reply via email to