From engelbert.gruber at gmail.com  Thu Aug  3 06:51:59 2017
From: engelbert.gruber at gmail.com (engelbert gruber)
Date: Thu, 3 Aug 2017 12:51:59 +0200
Subject: [Doc-SIG] docutils 0.14 released
Message-ID: <CAHnbgBODT4=F+0z6p1KNOnTi64sVhGmDt6Z6NZbjeyU9jA4hsg@mail.gmail.com>

RELEASE-NOTES

* docutils/docs/ref/docutils.dtd:

  - Enable validation of Docutils XML documents against the DTD:

* docutils/parsers/rst/:

  - Added functionality: escaped whitespace in URI contexts.
  - Consistent handling of all whitespace characters in inline markup
    recognition. (May break documents that relied on some whitespace
    characters (NBSP, ...) *not* to be recognized as whitespace.)

* docutils/utils/smartquotes.py:

  - Update quote definitions for et, fi, fr, ro, sv, tr, uk.
  - Add quote definitions for hr, hsb, hu, lv, sh, sl, sr.
  - Differentiate apostrophe from closing single quote (if possible).
  - Add command line interface for stand-alone use (requires 2.7).

* docutils/writers/_html_base:

  - Provide default title in metadata.
  - The MathJax CDN shut down on April 30, 2017. For security reasons, we
    don't use a third party public installation as default but warn
    if `math-output` is set to MathJax without specifying a URL.
    See math-output_ for details.

* docutils/writers/html4css1:

  - Respect automatic table column sizing.

* docutils/writers/latex2e/__init__.py

  - Handle class arguments for block-level elements by wrapping them
    in a "DUclass" environment. This replaces the special handling for
    "epigraph" and "topic" elements.

* docutils/writers/odf_odt:

  - Language option sets ODF document's default language
  - Image width, scale, ... set image size in generated ODF.

* tools/

  - New front-end ``rst2html4.py``.

cheers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20170803/5524b572/attachment.html>

From julien at palard.fr  Tue Aug  8 05:39:43 2017
From: julien at palard.fr (Julien Palard)
Date: Tue, 08 Aug 2017 05:39:43 -0400
Subject: [Doc-SIG] docs.python.org/fr/3.6/ is online!
In-Reply-To: <NCV_BNfLj19VUcYgykIQHd1ca9OW0qINfvF2cyd80-2du0AIeAVLKOx0TgDMQdBEbP9N_5Jbd2ZV3qCyMp4p2_on98EEN6TeIejNRRwNvrc=@palard.fr>
References: <NCV_BNfLj19VUcYgykIQHd1ca9OW0qINfvF2cyd80-2du0AIeAVLKOx0TgDMQdBEbP9N_5Jbd2ZV3qCyMp4p2_on98EEN6TeIejNRRwNvrc=@palard.fr>
Message-ID: <r3ylRD7oXCaUVzAXOeo0uSe6Q6lN4NWjL0U0KEWg5I05_26KDZEXZiudYhfNw4dyKuVD60JjFVzulKiXpwvnX9yWO5jYkv3Qb_pjEwQAo6I=@palard.fr>

Hi!
The language switch has been merged in python 3.7, so it's now visible here : https://docs.python.org/3.7/ and here [https://docs.python.org/fr/3.7/](https://docs.python.org/3.7/)
Bests,

--
Julien Palard
https://mdk.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20170808/e0300800/attachment.html>

From songofacandy at gmail.com  Tue Aug  8 06:02:50 2017
From: songofacandy at gmail.com (INADA Naoki)
Date: Tue, 8 Aug 2017 19:02:50 +0900
Subject: [Doc-SIG] docs.python.org/fr/3.6/ is online!
In-Reply-To: <r3ylRD7oXCaUVzAXOeo0uSe6Q6lN4NWjL0U0KEWg5I05_26KDZEXZiudYhfNw4dyKuVD60JjFVzulKiXpwvnX9yWO5jYkv3Qb_pjEwQAo6I=@palard.fr>
References: <NCV_BNfLj19VUcYgykIQHd1ca9OW0qINfvF2cyd80-2du0AIeAVLKOx0TgDMQdBEbP9N_5Jbd2ZV3qCyMp4p2_on98EEN6TeIejNRRwNvrc=@palard.fr>
 <r3ylRD7oXCaUVzAXOeo0uSe6Q6lN4NWjL0U0KEWg5I05_26KDZEXZiudYhfNw4dyKuVD60JjFVzulKiXpwvnX9yWO5jYkv3Qb_pjEwQAo6I=@palard.fr>
Message-ID: <CAEfz+Tw1tOp3n+zzbi6vQEeO_dkvf+nO_=snkL5EbBxi0497Nw@mail.gmail.com>

Congrats, Julien!

But I can't see language switcher on Python 3.6 document.

We (Japanese translators) translates latest stable release, not
development branch.
Is it possible to publish Japanese only for 3.6 branch?
INADA Naoki  <songofacandy at gmail.com>


On Tue, Aug 8, 2017 at 6:39 PM, Julien Palard via Doc-SIG
<doc-sig at python.org> wrote:
> Hi!
>
> The language switch has been merged in python 3.7, so it's now visible here
> : https://docs.python.org/3.7/ and here https://docs.python.org/fr/3.7/
>
> Bests,
> --
> Julien Palard
> https://mdk.fr
>
>
>
> _______________________________________________
> Doc-SIG maillist  -  Doc-SIG at python.org
> https://mail.python.org/mailman/listinfo/doc-sig
>

From julien at palard.fr  Tue Aug  8 07:25:43 2017
From: julien at palard.fr (Julien Palard)
Date: Tue, 08 Aug 2017 07:25:43 -0400
Subject: [Doc-SIG] docs.python.org/fr/3.6/ is online!
In-Reply-To: <CAEfz+Tw1tOp3n+zzbi6vQEeO_dkvf+nO_=snkL5EbBxi0497Nw@mail.gmail.com>
References: <NCV_BNfLj19VUcYgykIQHd1ca9OW0qINfvF2cyd80-2du0AIeAVLKOx0TgDMQdBEbP9N_5Jbd2ZV3qCyMp4p2_on98EEN6TeIejNRRwNvrc=@palard.fr>
 <r3ylRD7oXCaUVzAXOeo0uSe6Q6lN4NWjL0U0KEWg5I05_26KDZEXZiudYhfNw4dyKuVD60JjFVzulKiXpwvnX9yWO5jYkv3Qb_pjEwQAo6I=@palard.fr>
 <CAEfz+Tw1tOp3n+zzbi6vQEeO_dkvf+nO_=snkL5EbBxi0497Nw@mail.gmail.com>
Message-ID: <iAzKMmrsfZIvqRbHIFNMydSnF-M_AiDkvMzsy9L6hvoqV2e9RLHGcLBPuIKBgk_tfAtYXnXQsD45HW8D4g6hwm_jeujFTfzZ7Kid5aj7FKA=@palard.fr>

Hi Inada,

> But I can"t see language switcher on Python 3.6 document.

Yes I'm currently backporting it to older branches (3.6 and 2.7 at least).

> We (Japanese translators) translates latest stable release, not
> development branch.

> Is it possible to publish Japanese only for 3.6 branch?

Current implementation of the switcher can't do it, see: https://github.com/python/cpython/blob/dff9b5f9d62aa0b23f8a255867d09d11890efd1b/Doc/tools/static/switchers.js but if it make sense, it may be enhanced.
We're also limited by the fact that switchers are versionned in cpython itself, so they will follow the freez (security only) cycles, typically blocking us to add/remove a translations to a frozen versions, which may or may not be a problem as old versions documentation are built without switchers (see: https://docs.python.org/3.4/).
Last comment about this is that the current script building the documentation will automatically find the nearest branch for translations, see: https://github.com/python/docsbuild-scripts/blob/master/build_docs.py#L132
meaning that if you're working on the 3.6 branch, the ja/3.7 directory will be built using your 3.6 po files, which may (or may not) be desirable. Advantages are:
- If a translation team want to translate 3.7 only, then can and 3.6 will be partially build using it
- If a translation team is late adding a new branch, the new branch will still be built for them using their old translations, which for an unknown timespan will not diverge a lot
- Crawlers can start discovering / indexing new branches before translators start working on them
Disadvantages are more obvious: Translations are only partials.
So, currently, if you push a 3.6 branch to python-docs-ja, ja/{2.7,3.5,3.6,3.7} will be built using it.

--
Julien Palard
https://mdk.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20170808/bfc75ddd/attachment.html>

From songofacandy at gmail.com  Tue Aug  8 08:53:31 2017
From: songofacandy at gmail.com (INADA Naoki)
Date: Tue, 8 Aug 2017 21:53:31 +0900
Subject: [Doc-SIG] docs.python.org/fr/3.6/ is online!
In-Reply-To: <iAzKMmrsfZIvqRbHIFNMydSnF-M_AiDkvMzsy9L6hvoqV2e9RLHGcLBPuIKBgk_tfAtYXnXQsD45HW8D4g6hwm_jeujFTfzZ7Kid5aj7FKA=@palard.fr>
References: <NCV_BNfLj19VUcYgykIQHd1ca9OW0qINfvF2cyd80-2du0AIeAVLKOx0TgDMQdBEbP9N_5Jbd2ZV3qCyMp4p2_on98EEN6TeIejNRRwNvrc=@palard.fr>
 <r3ylRD7oXCaUVzAXOeo0uSe6Q6lN4NWjL0U0KEWg5I05_26KDZEXZiudYhfNw4dyKuVD60JjFVzulKiXpwvnX9yWO5jYkv3Qb_pjEwQAo6I=@palard.fr>
 <CAEfz+Tw1tOp3n+zzbi6vQEeO_dkvf+nO_=snkL5EbBxi0497Nw@mail.gmail.com>
 <iAzKMmrsfZIvqRbHIFNMydSnF-M_AiDkvMzsy9L6hvoqV2e9RLHGcLBPuIKBgk_tfAtYXnXQsD45HW8D4g6hwm_jeujFTfzZ7Kid5aj7FKA=@palard.fr>
Message-ID: <CAEfz+Tzv6p1Hp+EJ6X59MFf3_-aDtRojDPCobhr1OO9Y_GTtog@mail.gmail.com>

>
> Last comment about this is that the current script building the
> documentation will automatically find the nearest branch for translations,
> see:
> https://github.com/python/docsbuild-scripts/blob/master/build_docs.py#L132
> meaning that if you're working on the 3.6 branch, the ja/3.7 directory will
> be built using your 3.6 po files, which may (or may not) be desirable.
> Advantages are:
>
> - If a translation team want to translate 3.7 only, then can and 3.6 will be
> partially build using it
> - If a translation team is late adding a new branch, the new branch will
> still be built for them using their old translations, which for an unknown
> timespan will not diverge a lot
> - Crawlers can start discovering / indexing new branches before translators
> start working on them
>
> Disadvantages are more obvious: Translations are only partials.

Make sense.

>
> So, currently, if you push a 3.6 branch to python-docs-ja,
> ja/{2.7,3.5,3.6,3.7} will be built using it.

OK, I pushed 2.7 and 3.6 branch.
I won't push 3.5 branch because we haven't maintenanced it for months.

> --
> Julien Palard
> https://mdk.fr
>
>

Thanks

From julien at palard.fr  Tue Aug  8 09:04:36 2017
From: julien at palard.fr (Julien Palard)
Date: Tue, 08 Aug 2017 09:04:36 -0400
Subject: [Doc-SIG] docs.python.org/fr/3.6/ is online!
In-Reply-To: <CAEfz+Tzv6p1Hp+EJ6X59MFf3_-aDtRojDPCobhr1OO9Y_GTtog@mail.gmail.com>
References: <NCV_BNfLj19VUcYgykIQHd1ca9OW0qINfvF2cyd80-2du0AIeAVLKOx0TgDMQdBEbP9N_5Jbd2ZV3qCyMp4p2_on98EEN6TeIejNRRwNvrc=@palard.fr>
 <r3ylRD7oXCaUVzAXOeo0uSe6Q6lN4NWjL0U0KEWg5I05_26KDZEXZiudYhfNw4dyKuVD60JjFVzulKiXpwvnX9yWO5jYkv3Qb_pjEwQAo6I=@palard.fr>
 <CAEfz+Tw1tOp3n+zzbi6vQEeO_dkvf+nO_=snkL5EbBxi0497Nw@mail.gmail.com>
 <iAzKMmrsfZIvqRbHIFNMydSnF-M_AiDkvMzsy9L6hvoqV2e9RLHGcLBPuIKBgk_tfAtYXnXQsD45HW8D4g6hwm_jeujFTfzZ7Kid5aj7FKA=@palard.fr>
 <CAEfz+Tzv6p1Hp+EJ6X59MFf3_-aDtRojDPCobhr1OO9Y_GTtog@mail.gmail.com>
Message-ID: <uf3ZJj8w5iV_GHEYy_m6HBeKHXegVmyjuBk0IiykhIm2WX2kc3jEg_GRft-3AlLVyrRiWEpPwz08lGfTmqJMchWttLH_YPdroT-Paoq4jz4=@palard.fr>

o/

> OK, I pushed 2.7 and 3.6 branch.
> I won"t push 3.5 branch because we haven"t maintenanced it for months.

I added it to docsbuild-scripts: https://github.com/python/docsbuild-scripts/commit/00dbec7f463ba8c06091d05149ac57324293d9f0
So it will be built, you'll be able to check if everything is OK and if it's OK we'll add it to the language pickers too.

While I'm thinking, even if we're currently unable to skip building a given version in a given language, we can just not add 'ja' for a given release in the language picker (language pickers are versionned), so it will be built but not publicly, what do you think?

--
Julien Palard
https://mdk.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20170808/616e3ddb/attachment-0001.html>