You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@httpd.apache.org by Luca Toscano <to...@gmail.com> on 2016/11/15 21:01:49 UTC
Re: Translations (IRC conversation)
2016-10-23 12:55 GMT+02:00 Luca Toscano <to...@gmail.com>:
>
>
> 2016-10-20 21:46 GMT+02:00 Mads Toftum <ma...@toftum.dk>:
>
>> On Thu, Oct 20, 2016 at 09:36:51PM +0200, André Malo wrote:
>> > * Rich Bowen wrote:
>> > > * We have translations that are grossly out of date. We should drop
>> > > them. It remains only to define what "tool old" means? If a
>> translation
>> > > hasn't been touched since 2.4.0, I would recommend dropping it.
>> > > Discussion?
>> >
>> > Guilty... However, I think, it would be waste to throw them away. I'm
>> > proposing a "do not transform (and remove html) until current" solution
>> > instead. I can also take a look at the build system to make that happen.
>> >
>> Sounds like a much better solution.
>>
>
> I'd be +1 only if there is a clean way to mark these files as
> "old/stale/out-of-sync", together with a clean statement/note somewhere
> about what to do with them in the medium longer term (even in a page like
> https://httpd.apache.org/docs-project/).
>
>
Bump :)
Can we move forward removing some old and outdated documentations from the
docs?
Luca
Re: Translations (IRC conversation)
Posted by Luca Toscano <to...@gmail.com>.
2016-11-29 18:20 GMT+01:00 André Malo <nd...@perlig.de>:
> * Rich Bowen wrote:
>
> > On 11/20/2016 05:20 AM, Luca Toscano wrote:
> > > My view from takashi's status:
> > >
> > > 1) da, de, pt-b, ru, ko and zh-cn should be put in a holding area and
> > > not shown to the users.
> > > 2) not sure about tr and ja, it would be awesome to ping the last
> > > translators to figure out if they are willing to restart their work.
> > > 3) es and fr seems in a good shape (and we have active translators
> \o/).
> >
> > +1 to the above three designations. Erring on the side of leaving stuff
> > is fine when we're not sure. The languages you mention, I think we're
> > sure, and should drop from trunk and 2.4, as you say.
>
> Ok, there seem to be an unclear consensus (or we suck at being precise).
>
> I'll take the "drop" as "put into holding area" and will invest some time
> to
> adapt the build process to hide the translations until they're more
> current.
>
>
Thanks a lot, let me know if I can help!
Luca
Re: Translations (IRC conversation)
Posted by André Malo <nd...@perlig.de>.
* Rich Bowen wrote:
> On 11/20/2016 05:20 AM, Luca Toscano wrote:
> > My view from takashi's status:
> >
> > 1) da, de, pt-b, ru, ko and zh-cn should be put in a holding area and
> > not shown to the users.
> > 2) not sure about tr and ja, it would be awesome to ping the last
> > translators to figure out if they are willing to restart their work.
> > 3) es and fr seems in a good shape (and we have active translators \o/).
>
> +1 to the above three designations. Erring on the side of leaving stuff
> is fine when we're not sure. The languages you mention, I think we're
> sure, and should drop from trunk and 2.4, as you say.
Ok, there seem to be an unclear consensus (or we suck at being precise).
I'll take the "drop" as "put into holding area" and will invest some time to
adapt the build process to hide the translations until they're more current.
nd
--
Gib' mal folgendes in die Kommandozeile ein (und einen Moment warten):
net send localhost "Buuuh!"
Na, erschreckt? -- Markus Becker in mpdsh
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: Translations (IRC conversation)
Posted by Rich Bowen <rb...@rcbowen.com>.
On 11/20/2016 05:20 AM, Luca Toscano wrote:
> My view from takashi's status:
>
> 1) da, de, pt-b, ru, ko and zh-cn should be put in a holding area and
> not shown to the users.
> 2) not sure about tr and ja, it would be awesome to ping the last
> translators to figure out if they are willing to restart their work.
> 3) es and fr seems in a good shape (and we have active translators \o/).
+1 to the above three designations. Erring on the side of leaving stuff
is fine when we're not sure. The languages you mention, I think we're
sure, and should drop from trunk and 2.4, as you say.
--Rich
--
Rich Bowen - rbowen@rcbowen.com - @rbowen
http://apachecon.com/ - @apachecon
Re: Translations (IRC conversation)
Posted by Luca Toscano <to...@gmail.com>.
Hi Vincent,
2016-11-18 14:41 GMT+01:00 Vincent Deffontaines <vi...@gryzor.com>:
> Hi,
>
> Lucien and I have discussed off-list, regarding the 2.4 .fr doc
> translation.
> Lucien has provided an impressive work of .fr translation during the last
> monthes+years, which is only lacking review.
> We have many 2.4 .fr translated docs in the https://apache-doc-fr.gryzor.c
> om/apache-doc-fr
> SVN repository, that we only need to validate and commit.
>
> We'll be providing an effort so that we can validate and commit them into
> 2.4. This will reduce greatly the big diff on 2.4 status on /~takashi's
> status.
>
>
thanks a lot for this effort, fr is already one of the best up to date
non-en manuals, having it more complete it would improve our (french) users
experience even more.
Just to be clear, I didn't mean to propose to cut off whatever is not in
sync from /~takashi's status, but only to remove translations that are (or
seems to be) in an abandoned state and officially support only a subset of
translations. Of course in case of new translators joining the project we
could review the supported languages, but it should be clear to them how
much work it is to be done (refresh the most of a manual vs only helping
out with some documents).
My view from takashi's status:
1) da, de, pt-b, ru, ko and zh-cn should be put in a holding area and not
shown to the users.
2) not sure about tr and ja, it would be awesome to ping the last
translators to figure out if they are willing to restart their work.
3) es and fr seems in a good shape (and we have active translators \o/).
Opinions are welcome, it would be really great to reach an agreement during
the next days :)
Thanks!
Luc
Re: Translations (IRC conversation)
Posted by Vincent Deffontaines <vi...@gryzor.com>.
Hi,
Lucien and I have discussed off-list, regarding the 2.4 .fr doc
translation.
Lucien has provided an impressive work of .fr translation during the
last monthes+years, which is only lacking review.
We have many 2.4 .fr translated docs in the
https://apache-doc-fr.gryzor.com/apache-doc-fr
SVN repository, that we only need to validate and commit.
We'll be providing an effort so that we can validate and commit them
into 2.4. This will reduce greatly the big diff on 2.4 status on
/~takashi's status.
Cheers,
Vincent
Le 2016-11-18 12:08, Luca Toscano a �crit�:
> 2016-11-15 23:22 GMT+01:00 Andr� Malo <nd...@perlig.de>:
>
>> * Luca Toscano wrote:
>>
>>> 2016-10-23 12:55 GMT+02:00 Luca Toscano <to...@gmail.com>:
>>>> 2016-10-20 21:46 GMT+02:00 Mads Toftum <ma...@toftum.dk>:
>>>>> On Thu, Oct 20, 2016 at 09:36:51PM +0200, Andr� Malo wrote:
>>>>> > * Rich Bowen wrote:
>>>>> > > * We have translations that are grossly out of date. We
>> should
>>>>> > > drop them. It remains only to define what "tool old" means?
>> If a
>>>>>
>>>>> translation
>>>>>
>>>>> > > hasn't been touched since 2.4.0, I would recommend dropping
>> it.
>>>>> > > Discussion?
>>>>> >
>>>>> > Guilty... However, I think, it would be waste to throw them
>> away.
>>>>> > I'm proposing a "do not transform (and remove html) until
>> current"
>>>>> > solution instead. I can also take a look at the build system
>> to make
>>>>> > that happen.
>>>>>
>>>>> Sounds like a much better solution.
>>>>
>>>> I'd be +1 only if there is a clean way to mark these files as
>>>> "old/stale/out-of-sync", together with a clean statement/note
>> somewhere
>>>> about what to do with them in the medium longer term (even in a
>> page
>>>> like https://httpd.apache.org/docs-project/ [1]).
>>>
>>> Bump :)
>>>
>>> Can we move forward removing some old and outdated documentations
>> from
>>> the docs?
>>
>> Sure. Is there a consensus about how?
>
> Only ideas.. For example, we could start from
> http://home.apache.org/~takashi/translation-status/test.html#2.4:
> there are a lot of languages that are out of sync, we should just not
> publish them anymore in my opinion.
>
> WDYT?
>
> Luca
>
>
> Links:
> ------
> [1] https://httpd.apache.org/docs-project/
--
What is it you need, that makes your heart beat ?
Do you really know, cause it doesn't show.
New Order - Round & round
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: Translations (IRC conversation)
Posted by Luca Toscano <to...@gmail.com>.
2016-11-15 23:22 GMT+01:00 André Malo <nd...@perlig.de>:
> * Luca Toscano wrote:
>
> > 2016-10-23 12:55 GMT+02:00 Luca Toscano <to...@gmail.com>:
> > > 2016-10-20 21:46 GMT+02:00 Mads Toftum <ma...@toftum.dk>:
> > >> On Thu, Oct 20, 2016 at 09:36:51PM +0200, André Malo wrote:
> > >> > * Rich Bowen wrote:
> > >> > > * We have translations that are grossly out of date. We should
> > >> > > drop them. It remains only to define what "tool old" means? If a
> > >>
> > >> translation
> > >>
> > >> > > hasn't been touched since 2.4.0, I would recommend dropping it.
> > >> > > Discussion?
> > >> >
> > >> > Guilty... However, I think, it would be waste to throw them away.
> > >> > I'm proposing a "do not transform (and remove html) until current"
> > >> > solution instead. I can also take a look at the build system to make
> > >> > that happen.
> > >>
> > >> Sounds like a much better solution.
> > >
> > > I'd be +1 only if there is a clean way to mark these files as
> > > "old/stale/out-of-sync", together with a clean statement/note somewhere
> > > about what to do with them in the medium longer term (even in a page
> > > like https://httpd.apache.org/docs-project/).
> >
> > Bump :)
> >
> > Can we move forward removing some old and outdated documentations from
> > the docs?
>
> Sure. Is there a consensus about how?
>
Only ideas.. For example, we could start from
http://home.apache.org/~takashi/translation-status/test.html#2.4: there are
a lot of languages that are out of sync, we should just not publish them
anymore in my opinion.
WDYT?
Luca
Re: Translations (IRC conversation)
Posted by André Malo <nd...@perlig.de>.
* Luca Toscano wrote:
> 2016-10-23 12:55 GMT+02:00 Luca Toscano <to...@gmail.com>:
> > 2016-10-20 21:46 GMT+02:00 Mads Toftum <ma...@toftum.dk>:
> >> On Thu, Oct 20, 2016 at 09:36:51PM +0200, André Malo wrote:
> >> > * Rich Bowen wrote:
> >> > > * We have translations that are grossly out of date. We should
> >> > > drop them. It remains only to define what "tool old" means? If a
> >>
> >> translation
> >>
> >> > > hasn't been touched since 2.4.0, I would recommend dropping it.
> >> > > Discussion?
> >> >
> >> > Guilty... However, I think, it would be waste to throw them away.
> >> > I'm proposing a "do not transform (and remove html) until current"
> >> > solution instead. I can also take a look at the build system to make
> >> > that happen.
> >>
> >> Sounds like a much better solution.
> >
> > I'd be +1 only if there is a clean way to mark these files as
> > "old/stale/out-of-sync", together with a clean statement/note somewhere
> > about what to do with them in the medium longer term (even in a page
> > like https://httpd.apache.org/docs-project/).
>
> Bump :)
>
> Can we move forward removing some old and outdated documentations from
> the docs?
Sure. Is there a consensus about how?
nd
--
"Umfassendes Werk (auch fuer Umsteiger vom Apache 1.3)"
-- aus einer Rezension
<http://pub.perlig.de/books.html#apache2>
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org