From julien at palard.fr  Sat Jan  4 09:31:35 2020
From: julien at palard.fr (Julien Palard)
Date: Sat, 04 Jan 2020 14:31:35 +0000
Subject: [Doc-SIG] Python Documentation Translation to Bahasa Indonesia
 (Indonesian Language)
In-Reply-To: <CACUNLpU9hBR4GAXskdjfwtdH3RQ5HVkz_NYSMHN6KM8hdu7zdg@mail.gmail.com>
References: <CACUNLpUjv+RRFb-9TX4uK9QYfkuFyiZPqkqAf9VM_85pK8og6g@mail.gmail.com>
 <K7Ud-asXDvZSg5LLWBDM0ktniYRcRX0uO8m-OwPWIMRENi_B3G-O4bmOd9Uqrjx-U_eFNHuoFEaRCLB6thyJAv0uJiOBaWumVj-R55Fn3GU=@palard.fr>
 <CACUNLpXRqm-m7-oE=DPCbq+j0Q1B3FuBY1P7TVN2y74Cw7dDPw@mail.gmail.com>
 <CACUNLpWECZEO=uOsUZv1DHUGG0D3gqnMqK2FbVWdfkWiO8O2TQ@mail.gmail.com>
 <CAGbohnZKwzqX78q4eKLS0+8GhC4zhQv9vBmrVHgryFawB=BBEw@mail.gmail.com>
 <iXBOyTwToEnt-Al2XHs99jANonm_99ApUWxZpO4IUvQa732vkxPj4V2RZqRwKWiS_9G457qfJOlgaUL-AInvmj_F1oYP9gE_cs2Al0mgkhU=@palard.fr>
 <CACUNLpU9hBR4GAXskdjfwtdH3RQ5HVkz_NYSMHN6KM8hdu7zdg@mail.gmail.com>
Message-ID: <M93PmRK7y8wU5yT0AyR07V3YsZ_epsnEMTYWW4pZXGBPWC1UHGwUlWsHpTNxKT5SwSa0gUBl9e_WCJq7mAqV7EeDaj9KKv8Ph1_CLx6dj-8=@palard.fr>

o/

> Yes, it is. We really need Sphinx 2.3+.

Done, all branches and all languages are building using 2.3.1.

Happy new year!
--?
Julien Palard
https://mdk.fr


From oon.arfiandwi at gmail.com  Sat Jan  4 16:43:52 2020
From: oon.arfiandwi at gmail.com (oon arfiandwi)
Date: Sun, 5 Jan 2020 05:43:52 +0800
Subject: [Doc-SIG] Python Documentation Translation to Bahasa Indonesia
 (Indonesian Language)
In-Reply-To: <M93PmRK7y8wU5yT0AyR07V3YsZ_epsnEMTYWW4pZXGBPWC1UHGwUlWsHpTNxKT5SwSa0gUBl9e_WCJq7mAqV7EeDaj9KKv8Ph1_CLx6dj-8=@palard.fr>
References: <CACUNLpUjv+RRFb-9TX4uK9QYfkuFyiZPqkqAf9VM_85pK8og6g@mail.gmail.com>
 <K7Ud-asXDvZSg5LLWBDM0ktniYRcRX0uO8m-OwPWIMRENi_B3G-O4bmOd9Uqrjx-U_eFNHuoFEaRCLB6thyJAv0uJiOBaWumVj-R55Fn3GU=@palard.fr>
 <CACUNLpXRqm-m7-oE=DPCbq+j0Q1B3FuBY1P7TVN2y74Cw7dDPw@mail.gmail.com>
 <CACUNLpWECZEO=uOsUZv1DHUGG0D3gqnMqK2FbVWdfkWiO8O2TQ@mail.gmail.com>
 <CAGbohnZKwzqX78q4eKLS0+8GhC4zhQv9vBmrVHgryFawB=BBEw@mail.gmail.com>
 <iXBOyTwToEnt-Al2XHs99jANonm_99ApUWxZpO4IUvQa732vkxPj4V2RZqRwKWiS_9G457qfJOlgaUL-AInvmj_F1oYP9gE_cs2Al0mgkhU=@palard.fr>
 <CACUNLpU9hBR4GAXskdjfwtdH3RQ5HVkz_NYSMHN6KM8hdu7zdg@mail.gmail.com>
 <M93PmRK7y8wU5yT0AyR07V3YsZ_epsnEMTYWW4pZXGBPWC1UHGwUlWsHpTNxKT5SwSa0gUBl9e_WCJq7mAqV7EeDaj9KKv8Ph1_CLx6dj-8=@palard.fr>
Message-ID: <CACUNLpXYuSvNnYVAKyMEhvq9BbS4QENPkEXiZb20pC2NC=X9pA@mail.gmail.com>

Dear Julien,
happy new year.
what a great news!

yes, I have checked it,
got the Sphinx 2.3.1 with the latest translation update.

thank you very much.

sincerely,
oon arfiandwi


On Sat, Jan 4, 2020, 10:31 PM Julien Palard <julien at palard.fr> wrote:

> o/
>
> > Yes, it is. We really need Sphinx 2.3+.
>
> Done, all branches and all languages are building using 2.3.1.
>
> Happy new year!
> --
> Julien Palard
> https://mdk.fr
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20200105/625e36cf/attachment.html>

From maciej.olko at gmail.com  Sat Jan 25 17:31:26 2020
From: maciej.olko at gmail.com (Maciek Olko)
Date: Sat, 25 Jan 2020 23:31:26 +0100
Subject: [Doc-SIG] Make code blocks translatable
Message-ID: <CALYYG831_KAcKC9oE90j79zYTaLmbgzHzDu4y2w4WN5WCbv20g@mail.gmail.com>

Hello,

I'd like to set up discussion about making code blocks in documentation
translatable. From my experience many of code blocks would benefit from
being translated. Especially comments and string literals. For example this
code block from tutorial:

# this is the first commentspam = 1  # and this is the second comment
          # ... and now a third!text = "# This is not a comment
because it's inside quotes."

To enable their translation, it requires slight modification of Sphinx call
? gettext_additional_targets = ['literal-block'] configuration option value
would do this. The option has been introduced in Sphinx 1.3.

If there would be consensus about that I'd willingly add pull request
in docsbuild-scripts repository.

Kind regards,
Maciej
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20200125/2bd8f868/attachment.html>

From maciej.olko at gmail.com  Sun Jan 26 11:10:41 2020
From: maciej.olko at gmail.com (Maciek Olko)
Date: Sun, 26 Jan 2020 17:10:41 +0100
Subject: [Doc-SIG] Revision of resources' Transifex priorities
Message-ID: <CALYYG81hLt3PWKCofpWWJq9ghaFwH9Ez-LUG+9o82M8i3sPpMw@mail.gmail.com>

Hello,

I am wondering if it would be difficult to revise Transifex priority values
of resources. Now all resources have the same priority value ("high").
Would it be possible to highlight resources:

   - bugs,
   - all in tutorial directory,
   - library/functions, [1]
   - and sphinx,

among others by making their priority higher?

In my opinion it would ease the work with resources e.g. being able to
filter them by importance.

Looking forward to your opinion,
Kind regards,
Maciej

[1] Those first three are required for a translation to be in languge
switcher, therefore they are already made priorities by PEP 545.
https://www.python.org/dev/peps/pep-0545/#add-translation-to-the-language-switcher
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20200126/1311023b/attachment.html>

From songofacandy at gmail.com  Sun Jan 26 23:14:19 2020
From: songofacandy at gmail.com (Inada Naoki)
Date: Mon, 27 Jan 2020 13:14:19 +0900
Subject: [Doc-SIG] Make code blocks translatable
In-Reply-To: <CALYYG831_KAcKC9oE90j79zYTaLmbgzHzDu4y2w4WN5WCbv20g@mail.gmail.com>
References: <CALYYG831_KAcKC9oE90j79zYTaLmbgzHzDu4y2w4WN5WCbv20g@mail.gmail.com>
Message-ID: <CAEfz+TyFJfHB1sMbV-KeR=J_2LLBhpp7L+G8o9MJRs_kifKVSQ@mail.gmail.com>

I don't have a strong objection, but I think translating sample code
is much less important than translating regular docs.

For example, see https://docs.python.org/3/library/functools.html
There are many example code blocks.  Translating strings in them
doesn't help much.

So I think focusing to regular doc is better for effort-benefit ratio.

Regards,

On Sun, Jan 26, 2020 at 7:31 AM Maciek Olko <maciej.olko at gmail.com> wrote:
>
> Hello,
>
> I'd like to set up discussion about making code blocks in documentation translatable. From my experience many of code blocks would benefit from being translated. Especially comments and string literals. For example this code block from tutorial:
>
> # this is the first comment
> spam = 1  # and this is the second comment
>           # ... and now a third!
> text = "# This is not a comment because it's inside quotes."
>
> To enable their translation, it requires slight modification of Sphinx call ? gettext_additional_targets = ['literal-block'] configuration option value would do this. The option has been introduced in Sphinx 1.3.
>
> If there would be consensus about that I'd willingly add pull request in docsbuild-scripts repository.
>
> Kind regards,
> Maciej
> _______________________________________________
> Doc-SIG maillist  -  Doc-SIG at python.org
> https://mail.python.org/mailman/listinfo/doc-sig



-- 
Inada Naoki  <songofacandy at gmail.com>

From maciej.olko at gmail.com  Mon Jan 27 19:02:19 2020
From: maciej.olko at gmail.com (Maciek Olko)
Date: Tue, 28 Jan 2020 01:02:19 +0100
Subject: [Doc-SIG] Make code blocks translatable
In-Reply-To: <CAEfz+TyFJfHB1sMbV-KeR=J_2LLBhpp7L+G8o9MJRs_kifKVSQ@mail.gmail.com>
References: <CALYYG831_KAcKC9oE90j79zYTaLmbgzHzDu4y2w4WN5WCbv20g@mail.gmail.com>
 <CAEfz+TyFJfHB1sMbV-KeR=J_2LLBhpp7L+G8o9MJRs_kifKVSQ@mail.gmail.com>
Message-ID: <CALYYG80+PnaOmp1x=yMuKiAfdXwQdKVb+M3_KHxor46+OAYOsA@mail.gmail.com>

Thank you for response.

I guess the tutorial is my main concern, because it especially (and maybe
only (?)) contains some documentation sentences in comments. Having those
translated would make a final step to native translated look and feel of
tutorial.

Would it be potentially possible to treat tutorial differently and
translate code blocks contained in it only?

Kind regards,
Maciej

pon., 27 sty 2020 o 05:15 Inada Naoki <songofacandy at gmail.com> napisa?(a):

> I don't have a strong objection, but I think translating sample code
> is much less important than translating regular docs.
>
> For example, see https://docs.python.org/3/library/functools.html
> There are many example code blocks.  Translating strings in them
> doesn't help much.
>
> So I think focusing to regular doc is better for effort-benefit ratio.
>
> Regards,
>
> On Sun, Jan 26, 2020 at 7:31 AM Maciek Olko <maciej.olko at gmail.com> wrote:
> >
> > Hello,
> >
> > I'd like to set up discussion about making code blocks in documentation
> translatable. From my experience many of code blocks would benefit from
> being translated. Especially comments and string literals. For example this
> code block from tutorial:
> >
> > # this is the first comment
> > spam = 1  # and this is the second comment
> >           # ... and now a third!
> > text = "# This is not a comment because it's inside quotes."
> >
> > To enable their translation, it requires slight modification of Sphinx
> call ? gettext_additional_targets = ['literal-block'] configuration option
> value would do this. The option has been introduced in Sphinx 1.3.
> >
> > If there would be consensus about that I'd willingly add pull request in
> docsbuild-scripts repository.
> >
> > Kind regards,
> > Maciej
> > _______________________________________________
> > Doc-SIG maillist  -  Doc-SIG at python.org
> > https://mail.python.org/mailman/listinfo/doc-sig
>
>
>
> --
> Inada Naoki  <songofacandy at gmail.com>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20200128/7d908c42/attachment.html>