translation branch and stable/2.20 branch

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

translation branch and stable/2.20 branch

Masamichi HOSODA-2
2.19.65 has been released,
it seems that it does not contain some recent translations.

e.g.
eb38c33a95 Doc-ja: fix cindex in NR
eccad9a9f8 Doc-ja: update Usage
1c1a932358 Doc-es: update one texidoc.
e7385f6e58 Web-es: update Introduction.
2cfed6cc93 Doc-es: update Notation/Simultaneous.
9f53d74eaf Web: Add a new document to what We Wrote list.
ce1c9d0ea4 Doc-ca: Catalan translation of the notation manual: expressive.itely and text.itely
etc.

Is the translation branch not contained in the release?
Or will it be contained in the next release?

On the other hand,
the current "translation" branch does not seem to contain
recent document updates.

e.g.
0712559601 Issue 5164: Doc: Add usage of OpenType font feature
97956152eb Issue 5166/2: Doc: Delete note for svg backend which become unnecessary
f40aa7dc74 Issue 5166/1: Doc: Update default font description
0e23f12caa Issue 5163: Update URW++ OTF files
68dbc841e3 Doc: CG, explain other git prompt variables
54a35cdc57 Web: Authors.itexi update
2dcca6dacd Doc: add comment about automatically generated documentation
etc.

Which branch should the translators translate?
e.g. translate the English document in the master branch,
commit to the translation branch, etc.

_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: translation branch and stable/2.20 branch

James Lowe
Hosoda-san,

You may also want to include the translation email alias.

James

On Tue, 08 Aug 2017 23:48:50 +0900 (JST)
Masamichi Hosoda <[hidden email]> wrote:

> 2.19.65 has been released,
> it seems that it does not contain some recent translations.
>
> e.g.
> eb38c33a95 Doc-ja: fix cindex in NR
> eccad9a9f8 Doc-ja: update Usage
> 1c1a932358 Doc-es: update one texidoc.
> e7385f6e58 Web-es: update Introduction.
> 2cfed6cc93 Doc-es: update Notation/Simultaneous.
> 9f53d74eaf Web: Add a new document to what We Wrote list.
> ce1c9d0ea4 Doc-ca: Catalan translation of the notation manual:
> expressive.itely and text.itely etc.
>
> Is the translation branch not contained in the release?
> Or will it be contained in the next release?
>
> On the other hand,
> the current "translation" branch does not seem to contain
> recent document updates.
>
> e.g.
> 0712559601 Issue 5164: Doc: Add usage of OpenType font feature
> 97956152eb Issue 5166/2: Doc: Delete note for svg backend which
> become unnecessary f40aa7dc74 Issue 5166/1: Doc: Update default font
> description 0e23f12caa Issue 5163: Update URW++ OTF files
> 68dbc841e3 Doc: CG, explain other git prompt variables
> 54a35cdc57 Web: Authors.itexi update
> 2dcca6dacd Doc: add comment about automatically generated
> documentation etc.
>
> Which branch should the translators translate?
> e.g. translate the English document in the master branch,
> commit to the translation branch, etc.
>
> _______________________________________________
> lilypond-devel mailing list
> [hidden email]
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
>


_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: translation branch and stable/2.20 branch

Jean-Charles Malahieude-2
In reply to this post by Masamichi HOSODA-2
Le 08/08/2017 à 16:48, Masamichi Hosoda a écrit :
> 2.19.65 has been released,
> it seems that it does not contain some recent translations.
>
> [...]
>
> Which branch should the translators translate?
> e.g. translate the English document in the master branch,
> commit to the translation branch, etc.
>

Sorry for the delay, but holidays keeps me pretty much off-line.

According to the thread "Any objections to branching off a stable branch
for 2.20?" and especially
http://lists.gnu.org/archive/html/lilypond-devel/2017-07/msg00090.html 
translating only apply to the translation branch.

New material, improvements and amendments will be cherry-picked from
master into stable/2.20. I'll let David K. list which commits are to be
part of it.

Cheers,
Jean-Charles


_______________________________________________
lilypond-devel mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Loading...