2017-03-10 1:03 GMT+01:00 Victor Stinner :
> FYI we are already working on a PEP with Julien Palard (FR) and INADA
> Naoki (JP). We will post it when it will be ready ;-)
Ok, Julien wrote the PEP with the help of Naoki and myself. He posted
it on python-ideas for a first review:
https://mail.pytho
2017-03-10 0:35 GMT+01:00 Ned Deily :
> I don't know exactly what you mean by an "official GO" but I don't think
> there has been any agreement yet since there hasn't been a specific proposal
> yet to review. I think what *was* agreed is that, in principle, translation
> *sounds* like a good id
[catching up on an older thread]
On Feb 27, 2017, at 05:31, Victor Stinner wrote:
> 2017-02-25 19:19 GMT+01:00 Brett Cannon :
>> It's getting a little hard to tease out what exactly is being asked at this
>> point. Perhaps it's time to move the discussion over to a translation SIG
>> (which proba
I support having an official translated doc.
I have seen several groups trying to translate part of our official doc.
But their efforts are disperse and quickly become lost because they
are not organized to work towards a single common result and their
results are hold anywhere on the Web and hard
2017-02-24 16:10 GMT+01:00 Steven D'Aprano :
>> …And then you need another one to
>> check what was written. These are practical problems. There are
>> extant services to support this, they are expensive in either money or
>> time, and the docs produced usually lag behind English quite a bit.
>
>
2017-02-24 13:20 GMT+01:00 Berker Peksağ :
>> If the original text (english) changes, untranslated text is
>> displayed, not outdated text.
>
> I think that's much worse than showing the outdated text. I don't see
> any point on showing half English and half French text if the reader
> can't unders
2017-02-25 19:19 GMT+01:00 Brett Cannon :
> It's getting a little hard to tease out what exactly is being asked at this
> point. Perhaps it's time to move the discussion over to a translation SIG
> (which probably needs to be created unless the old
> https://mail.python.org/mailman/listinfo/i18n-si
On Sun, Feb 26, 2017 at 11:30 PM, Nick Coghlan wrote:
> On 27 February 2017 at 14:03, David Mertz wrote:
>
>> Could we have side-by-side English and whatever translated language? Then
>> also use some sort of typographic indicator like color to show when the
>> translation is out of date?
>>
>
>
On 27 February 2017 at 14:03, David Mertz wrote:
> Could we have side-by-side English and whatever translated language? Then
> also use some sort of typographic indicator like color to show when the
> translation is out of date?
>
This kind of interface is what services like Transifex and Zanata
Could we have side-by-side English and whatever translated language? Then
also use some sort of typographic indicator like color to show when the
translation is out of date?
On Feb 26, 2017 6:39 PM, "Rob Cliffe" wrote:
>
>
> On 24/02/2017 12:20, Berker Peksağ wrote:
>
>> On Thu, Feb 23, 2017 at
On 24/02/2017 12:20, Berker Peksağ wrote:
On Thu, Feb 23, 2017 at 12:01 AM, Victor Stinner
wrote:
2017-02-22 19:04 GMT+01:00 Serhiy Storchaka :
What percent of lines is changed between bugfix releases? Feature releases?
My largest apprehension is that the documentation can be outdated and
q
On Sat, 25 Feb 2017 at 11:59 INADA Naoki wrote:
> Yes, right place to discussion is one of important things what I want.
> I haven't know about i18n-sig. Is it better than docs-sig?
>
Probably not (I honestly forgot about docs-sig).
>
>
> Another thing I want is agreement to use project name
On 26 February 2017 at 05:57, INADA Naoki wrote:
> Yes, right place to discussion is one of important things what I want.
> I haven't know about i18n-sig. Is it better than docs-sig?
>
>
> Another thing I want is agreement to use project name looks like
> (semi)official project.
>
> We used "pyt
Yes, right place to discussion is one of important things what I want.
I haven't know about i18n-sig. Is it better than docs-sig?
Another thing I want is agreement to use project name looks like
(semi)official project.
We used "python-doc-jp" name on Transifex at first. But since some people
o
On Feb 25, 2017, at 13:19, Brett Cannon wrote:
> It's getting a little hard to tease out what exactly is being asked at this
> point. Perhaps it's time to move the discussion over to a translation SIG
> (which probably needs to be created unless the old
> https://mail.python.org/mailman/listinf
On Fri, 24 Feb 2017 at 03:50 INADA Naoki wrote:
> > Where should these translated docs live and how does one make it clear to
> > users reading them that doc bugs shouldn't be submitted to the main bug
> > tracker/github repo?
> >
>
> We setup github page. See https://python-doc-ja.github.io/py3
On 25 February 2017 at 04:54, MRAB wrote:
> On 2017-02-24 15:10, Steven D'Aprano wrote:
>
>> Nevertheless, I certainly wouldn't object if people wanted to try
>> writing Simple English translations of the docs. But I don't think they
>> would be as useful as translations into non-English.
>>
>> [
On 25 February 2017 at 01:10, Steven D'Aprano wrote:
> On Fri, Feb 24, 2017 at 06:01:59AM -0500, tritium-l...@sdamon.com wrote:
> > …And then you need another one to
> > check what was written. These are practical problems. There are
> > extant services to support this, they are expensive in ei
On 2017-02-24 15:10, Steven D'Aprano wrote:
On Fri, Feb 24, 2017 at 06:01:59AM -0500, tritium-l...@sdamon.com wrote:
My gut splits the difference on this issue; I suggest an approach to
meet in the middle – a version of the docs written in simplified
English (Not quite Up Goer Five simplified,
On Fri, Feb 24, 2017 at 06:01:59AM -0500, tritium-l...@sdamon.com wrote:
> My gut splits the difference on this issue; I suggest an approach to
> meet in the middle – a version of the docs written in simplified
> English (Not quite Up Goer Five simplified, but simplified.)
As an English speaker
On 24 February 2017 at 23:05, INADA Naoki wrote:
> On Fri, Feb 24, 2017 at 9:20 PM, Berker Peksağ
> wrote:
> >
> > As someone who have spent a lot of time reviewing and committing
> > documentation patches, I'm strongly against on marking documentation
> > translations as official.
>
> I totally
On Fri, Feb 24, 2017 at 9:20 PM, Berker Peksağ wrote:
> On Thu, Feb 23, 2017 at 12:01 AM, Victor Stinner
> wrote:
>> 2017-02-22 19:04 GMT+01:00 Serhiy Storchaka :
>>> What percent of lines is changed between bugfix releases? Feature releases?
>>>
>>> My largest apprehension is that the documentat
On Thu, Feb 23, 2017 at 12:01 AM, Victor Stinner
wrote:
> 2017-02-22 19:04 GMT+01:00 Serhiy Storchaka :
>> What percent of lines is changed between bugfix releases? Feature releases?
>>
>> My largest apprehension is that the documentation can be outdated and
>> quickly become degraded if main cont
> Where should these translated docs live and how does one make it clear to
> users reading them that doc bugs shouldn't be submitted to the main bug
> tracker/github repo?
>
We setup github page. See https://python-doc-ja.github.io/py36/ (note that
version switcher won't work because this html i
I've recently been translating the Tutorial in Greek as a side thing that
also helps me catch some doc bugs :-). So it's an obvious +1 from me.
I really like this idea and would like to see it come to fruition. I think
some issues need to be addressed first, though:
Where should these translated
I've recently been translating the Tutorial in Greek as a side thing that
also helps me catch some doc bugs :-). So it's an obvious +1 from me.
I really like this idea and would like to see it come to fruition. I think
some issues need to be addressed first, though:
Where should these translated
@python.org]
On Behalf Of Nick Coghlan
Sent: Friday, February 24, 2017 5:02 AM
To: Victor Stinner
Cc: Antoine Pitrou ; Python Dev
Subject: Re: [Python-Dev] Translated Python documentation
On 23 February 2017 at 02:15, Victor Stinner mailto:victor.stin...@gmail.com> > wrote:
2017-02-22
On 23 February 2017 at 02:15, Victor Stinner
wrote:
> 2017-02-22 16:40 GMT+01:00 Antoine Pitrou :
> > As long as you are asking for "moral" support and not actually
> > vouching for the accuracy of third-party translations, then +1 from me.
>
> The main complain about these translations is the ac
2017-02-22 19:04 GMT+01:00 Serhiy Storchaka :
> What percent of lines is changed between bugfix releases? Feature releases?
>
> My largest apprehension is that the documentation can be outdated and
> quickly become degraded if main contributors left it.
If the original text (english) changes, untr
On Wed, Feb 22, 2017 at 3:04 PM, Serhiy Storchaka wrote:
> My largest apprehension is that the documentation can be outdated and
> quickly become degraded if main contributors left it.
This is why we focus in the Tutorial only, but also:
a) The tutorial is mostly the "entry point" to Python's d
On 22.02.17 18:15, Victor Stinner wrote:
2017-02-22 16:40 GMT+01:00 Antoine Pitrou :
As long as you are asking for "moral" support and not actually
vouching for the accuracy of third-party translations, then +1 from me.
The main complain about these translations is the accuracy.
My bet is tha
On Wed, Feb 22, 2017 at 9:10 AM, Victor Stinner
wrote:
> There are a least 3 groups of people who are translating the Python
> documentation in their mother language (french, japanese, spanish).
We translated (and even printed/published) the Tutorial (we're
currently maintaining the Py2 and Py3
2017-02-22 16:40 GMT+01:00 Antoine Pitrou :
> As long as you are asking for "moral" support and not actually
> vouching for the accuracy of third-party translations, then +1 from me.
The main complain about these translations is the accuracy.
My bet is that making these translations "official" an
Hi Victor,
On Wed, 22 Feb 2017 13:10:17 +0100
Victor Stinner wrote:
>
> IMHO a reference in this domain is PHP: PHP documentation is
> translated to at least 10 languages. See for example the "Change
> language: [...]" list at:
>
>http://php.net/echo
>
> I'm not asking you to take any tec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/22/2017 07:10 AM, Victor Stinner wrote:
> Hi,
>
> I'm a member of the french #python-fr IRC channel on Freenode: it's
> common to meet people who don't speak english and so are unable to
> read the Python official documentation. Python wants t
Hi,
I'm a member of the french #python-fr IRC channel on Freenode: it's
common to meet people who don't speak english and so are unable to
read the Python official documentation. Python wants to be widely
available, for all users, in any language: that's also why Python 3
now allows any non-ASCII
36 matches
Mail list logo
