Re: Qualifications of the Reviewer of Translated Doc

> I am concerned about the qualifications of the reviewer of translated doc.
> Is the Apache HTTP Server Documentation Project just request for a fluent
> speaker for the relevant language to have a review on the translated doc?
> Do the reviewers need to be famous or well-reputated? If not, then why do
> we need reviewers? We can just let our friends to put their names there.

We try to get at least one completely indepedent review by a person fluent
in the languange before we add anything to the repository.

However note that this is an open mailing list - and we always solicit and
encourage feedback, bugs (you -can- file a bug against the documentation!)
if a translation is somewhere lacking.

The more people participate the merrier !

Dw

[PATCH] common.dtd

Hi, I sending a patch I made to common.dtd to make it accept the special 
characters required to pt-br translations (punctuation characters).

--

-- 
Luiz Rocha  <luiz <at> lsdr.net>

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe <at> httpd.apache.org
For additional commands, e-mail: docs-help <at> httpd.apache.org

[PATCH] build.xml and manual.pt-br.xst

Hello everyone,

  I sending attached to this email a updated build.xml (to support pt-br 
builds) and the manual.pt-br.xsl (also required).

 The pt-br.xml is already done, but I'm waiting for the revisor to take a 
look before post it here.

--

-- 
Luiz Rocha  <luiz <at> lsdr.net>

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe <at> httpd.apache.org
For additional commands, e-mail: docs-help <at> httpd.apache.org

Re: Qualifications of the Reviewer of Translated Doc

Hi everybody!

I do understand JHKChan's concern about the qualification of the reviewer of 
translated doc. It looks fair to check the quality of job before making it 
publically available.

As far as I understand there is no commit member who can and will check and 
commit my translation to russian. So, now it will be useless to begin 
translation. But I can look to the current improvement process and send my 
comments.

Best wishes,
Boris L. Zanin (aka klootz), 3.IX.2002

> Dear ALL,
>
> I am concerned about the qualifications of the reviewer of translated doc.
> Is the Apache HTTP Server Documentation Project just request for a fluent
> speaker for the relevant language to have a review on the translated doc?
> Do the reviewers need to be famous or well-reputated? If not, then why do
> we need reviewers? We can just let our friends to put their names there.
> This is my real concern.
>
> JHKChan

[TRANSLATION] upgrading.xml - translated into Russian

I've involved one more person into the translation work. So now all aspects of the translation are checked.
May be I'll link up some other people to this work, but actually I see no need of this. If you disagree,
please, inform me. Previous files will be checked by the new reviewer in a couple of days and I will resend
any of them, if any mistakes are found.

And one more question - should I translate the LICENSE file or should I leave it in English?

Translator: Ilia Soldis <rkai <at> tversu.ru>
Reviewers:  Ivan Shvedov <ivan <at> tversu.ru>
            Arthur Reznikov <art1tur <at> mail.ru>
Filename:   upgrading.xml
Repository
revision:   1.2

<?xml version='1.0' encoding='KOI8-R' ?>
<!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="./style/manual.en.xsl"?>
<manualpage>
<relativepath href="."/>

<title>ðÅÒÅÈÏÄ ÏÔ ×ÅÒÓÉÉ 1.3 Ë ×ÅÒÓÉÉ 2.0</title>

<summary>
  <p>íÙ ÓÏÄÅÒÖÉÍ ÜÔÏÔ ÄÏËÕÍÅÎÔ ÄÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÐÏÍÏÞØ ÐÏÌØÚÏ×ÁÔÅÌÑÍ
  ÐÅÒÅÊÔÉ Ë ÉÓÐÏÌØÚÏ×ÁÎÉÀ ÓÅÒ×ÅÒÁ ×ÅÒÓÉÉ 2.0. úÄÅÓØ ×Ù
ÎÁÊÄÅÔÅ ÌÉÛØ
  ËÒÁÔËÉÅ ÚÁÍÅÞÁÎÉÑ; ÂÏÌÅÅ ÐÏÄÒÏÂÎÕÀ ÉÎÆÏÒÍÁÃÉÀ Ï
ÎÏ×Ï××ÅÄÅÎÉÑÈ ÍÏÖÎÏ
  ÎÁÊÔÉ ÌÉÂÏ × ÄÏËÕÍÅÎÔÅ <a href="new_features_2_0.html"
  >îÏ×ÙÅ ×ÏÚÍÏÖÎÏÓÔÉ</a>, ÌÉÂÏ × ÆÁÊÌÅ <code>src/CHANGES</code>.</p>

Re: Qualifications of the Reviewer of Translated Doc

On Tue, 3 Sep 2002, Klootz Morse wrote:

> Hi everybody!
>
> I do understand JHKChan's concern about the qualification of the reviewer of
> translated doc. It looks fair to check the quality of job before making it
> publically available.
>
> As far as I understand there is no commit member who can and will check and
> commit my translation to russian. So, now it will be useless to begin
> translation. But I can look to the current improvement process and send my
> comments.

This seems a very unfortunate position, as this would mean that we are
forever limited to the languages that are already spoken/understood by
the current committers, with no opportunity for this group to expand.

So far, we have had very good success with our current method, with very
little making it through the process that was substandard and/or
incorrect. Each time a translation has been submitted, we have been able
to locate someone who was able to verify its correctness. Sure, the
concern is valid, but has thus far not proven to be a problem. It is
very circular reasoning. If we already had someone on "the team" who was
a native speaker of the language in question, surely we would already
have a translation into that language. The goal is to get translations
into languages that we don't already have, which, necessarily, means
that we'll also have to have an outside source of verification.

--

-- 
Rich Bowen - rbowen <at> rcbowen.com

Re: [TRANSLATION] upgrading.xml - translated into Russian

On Tue, 3 Sep 2002, Ilia Soldis wrote:

> I've involved one more person into the translation work. So now all aspects of the translation are
checked. May be I'll link up some other people to this work, but actually I see no need of this. If you
disagree, please, inform me. Previous files will be checked by the new reviewer in a couple of days and I
will resend any of them, if any mistakes are found.
>
> And one more question - should I translate the LICENSE file or should I leave it in English?

My *opinion* is that it would be nice to have this in other languages.
However, it is more important with the LICENSE than with other files
that it be verified correct, and there may actually be a requirement
that the ASF board and/or lawyer-type-persons verify its correctness. We
probably need a response on this from someone a little higher up. What
have we done with other languages?

--

-- 
And everyone said, "If we only live,
We too will go to sea in a Sieve -
To the hills of the Chankly Bore!"
 (The Jumblies, by Edward Lear)

Re: cvs commit: httpd-2.0/docs STATUS

On Fri, 30 Aug 2002, Joshua Slive wrote:

> > Perhaps we should clarify this in some way. IMO one list would be enough
> > (docs-project/translations.html), and two list only make things a little bit
> > harder to maintain and overlook.
> >
> > If there is no way to contact the authors, I would like to remove the below
> > list from the STATUS file because its somehow more confusing than useful.
>
> +1 on removing the list from STATUS.

+1 also. It's not only confusing, it's actively misleading. Are those
translations *really* in progress? I've not seen much evidence of that.
It would be a shame if a willing participant was turned away by thinking
that someone else was already doing a translation, so there was no need
of their help.

Better just to have a pointer here to the doc on the docs-project site.

--

-- 
Rich Bowen
Apache - mod_perl - Perl - CGI
http://www.ApacheAdmin.com/

Re: [TRANSLATION] upgrading.xml - translated into Russian

On Tue, 3 Sep 2002, Rich Bowen wrote:

> On Tue, 3 Sep 2002, Ilia Soldis wrote:
>
> > I've involved one more person into the translation work. So now all aspects of the translation are
checked. May be I'll link up some other people to this work, but actually I see no need of this. If you
disagree, please, inform me. Previous files will be checked by the new reviewer in a couple of days and I
will resend any of them, if any mistakes are found.
> >
> > And one more question - should I translate the LICENSE file or should I leave it in English?
>
> My *opinion* is that it would be nice to have this in other languages.
> However, it is more important with the LICENSE than with other files
> that it be verified correct, and there may actually be a requirement
> that the ASF board and/or lawyer-type-persons verify its correctness. We
> probably need a response on this from someone a little higher up. What
> have we done with other languages?

Please leave the LICENSE in the -English- language.

If you translate it; then you MUST put something in the translation which
says that it is NOT the license, but just an interpretive note only; and
teh file MUST not be called LICENSE or anything like that. Call it
something like note-about-license.<language>.txt.

But please: always stress that it is not the actual license.

There will only be ONE(1) authoritative and official version of the
license.

Re: [TRANSLATION] upgrading.xml - translated into Russian

Ilidia,

In order to (easily) commit this - could you send those files ether as
attachments or as a diff -u ? I am worried that otherwise we loose some
of the non-ascii characters.

Dw

On Tue, 3 Sep 2002, Ilia Soldis wrote:

> I've involved one more person into the translation work. So now all aspects of the translation are
checked. May be I'll link up some other people to this work, but actually I see no need of this. If you
disagree, please, inform me. Previous files will be checked by the new reviewer in a couple of days and I
will resend any of them, if any mistakes are found.
>
> And one more question - should I translate the LICENSE file or should I leave it in English?
>
> Translator: Ilia Soldis <rkai <at> tversu.ru>
> Reviewers:  Ivan Shvedov <ivan <at> tversu.ru>
>             Arthur Reznikov <art1tur <at> mail.ru>
> Filename:   upgrading.xml
> Repository
> revision:   1.2
>
>
> <?xml version='1.0' encoding='KOI8-R' ?>
> <!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">
> <?xml-stylesheet type="text/xsl" href="./style/manual.en.xsl"?>
> <manualpage>