Checking for updates on translations

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Checking for updates on translations

Walter Garcia-Fontes
I'm trying to check for updates in already translated
documentation. Are the commands explained in :
http://lilypond.org/doc/v2.19/Documentation/contributor-big-page#check-state-of-translation
still valid? I tried them and they don't seem to work.

Otherwise what is the best way to check my translations against the
existing state of the documentation?

Thanks,

--
Walter Garcia-Fontes



Reply | Threaded
Open this post in threaded view
|

Re: Checking for updates on translations

Jean-Charles MALAHIEUDE
Le 05/05/2016 à 17:17, Walter Garcia-Fontes a écrit :
> I'm trying to check for updates in already translated
> documentation. Are the commands explained in :
> http://lilypond.org/doc/v2.19/Documentation/contributor-big-page#check-state-of-translation
> still valid? I tried them and they don't seem to work.
>

What I usually do for the French version is

cd Documentation/

make ISOLANG=fr NO_COLOR=1 check-translation > ../../chktrans

and then open chktrans which is located one step beyond my local repo.

Just replace fr with ca for Catalan.

Cheers,
Jean-Charles



Reply | Threaded
Open this post in threaded view
|

Re: Checking for updates on translations

Francisco Vila
> make ISOLANG=fr NO_COLOR=1 check-translation > ../../chktrans

The variant I use is

  make ISOLANG=es check-translation > chktrans

Then

  less -R chktrans

Colors are very important when decoding that information.

Then I compare <file> with es/<file> using the meld tool, for example

  meld notation/input.itely es/notation/input.itely

called in turn by a script that simply adds the es/ part to generate
the second path.

Also, I select context lines from the « less -R chktrans » command and
copy them with Ctrl-Shift-C. Then paste them into the search box in
meld, the key sequence being

Ctrl-F Ctrl-V [Enter]

And the cursor jumps toe the context lines I first selected on the console.

--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com


Reply | Threaded
Open this post in threaded view
|

Re: Checking for updates on translations

Walter Garcia-Fontes
* Francisco Vila, [hidden email] [06/05/16 01:17]:
> > make ISOLANG=fr NO_COLOR=1 check-translation > ../../chktrans
>
> The variant I use is
>
>   make ISOLANG=es check-translation > chktrans

Thanks a lot for all the tips. But this last command doesn't work for
me.

I cd into my build tree, and there I cd into Documentation.

When I use the above command, what I get in the "chktrans" file is:

ISOLANG=ca /usr/bin/python -tt /home/wgarcia/lilypond-git/scripts/auxiliar/check_translation.py

and nothing else.

Or should I be issuing this command from some other place? I tried at
the directory above this (the root of the build tree) and at
build/Documentation/ca and there it complains of no rules to do check-translation.

--
Walter Garcia-Fontes
L'Hospitalet de Llobregat