You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@httpd.apache.org by kajaa zhang <ka...@lycos.com> on 2003/02/01 12:10:24 UTC
Re: HERE is a Simplified Chinese Manual Transalation Project going on.
Sorry, the two emails before are mis-addressed, please remove it, thanks!
From: <nd...@perlig.de>
Happy New Year, this is the Chinese New Year's Day!
* Andr� Malo wrote:
> Thanks for the explanation. I was unsure. In the meantime I've done some
> homework. Well, the difference may be not as much as between Japanese and
> Korean ;-), but anyway sufficient for a separate translation.
Yes, you are right, althought the differences are significant, they are not different languages.
> hmm, adjusting my statement: the correct language tag would be zh-cn, right?
> (traditional would be zh-tw or zh-hk - are there actual differences
between taiwan traditional and honkong traditional?)
like JHKChan said, it is not neccesary to define zh-tw and zh-hk
because there are no autual diferences between them.
Since in DEFAULT Apache httpd.conf, there are the following configs:
AddCharset GB2312 .gb2312 .gb
AddCharset big5 .big5 .b5
, so I think it's OK to let it be as *.xml.zh & *.html.zh.gb, and
avoid additional modifications to the config file by the end users.
But, I think some modifications to the DEFAULT config file are necessary,
because Traditional Chinese is just a charset of Chinese, not a
independent language, so the default settings:
AddLanguage tw .tw
AddLanguage zh-tw .tw
are not reasonable, and should be replaced of:
AddLanguage zh .zh.
>> - the <!-- English Revision --> notes the CVS revision number of the
>> particular english original document, so it can't be 2.0
>
> Oh. They _are_ useful. The docs are not static. Noting the original CVS
> revision number at translation time will help you to track the changes and
> keep the translation in sync.
it can't be 2.0, so what it should be? 1.3? for documents version 2.0?
> yep, I think it's clear now. I've done a first CVS checkout from your site.
> If nobody beats me before and there are no objections, I'll try to
> integrate it into our CVS next time (read: 1-2 weeks).
> Thanks anyway for the contribution!
This is the very thing we hope to happen. :)
kajaa
_____________________________________________________________
Get 25MB, POP3, Spam Filtering with LYCOS MAIL PLUS for $19.95/year.
http://login.mail.lycos.com/brandPage.shtml?pageId=plus&ref=lmtplus
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: HERE is a Simplified Chinese Manual Transalation Project going on.
Posted by kajaa <ka...@eastday.com>.
William A. Rowe, Jr. wrote:
> I am interested (as I'm totally ignorant here) about the difference
between
> traditional and simplified Chinese... are the readers of one able to read
> the other? How disparate are they?
Thanks for your attentions!
I wrote a page for Simplified Chinese and Traditional Chinese, please look
at: http://kajaa.bbs.us/ami/ami-s2t.html
Note, for reference only, no any political opinions even if it may be there.
kajaa
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: HERE is a Simplified Chinese Manual Transalation Project
going on.
Posted by "William A. Rowe, Jr." <wr...@apache.org>.
At 09:07 PM 2/6/2003, kajaa wrote:
>In the Apache distribute releases, there are many translations including
>Japanese, Korean, and even Traditional Chinese, but no Simplified Chinese,
>which is used by more than 1.3 billion peoples in the world, while
>Traditional Chinese is used in some areas by approximately 10-20 million
>peoples. As a Simplified Chinese user, I think I should do something if
>possible, so the project started.
Undoubtedly goodness. Obviously this docs@ list is an english dialog,
and where we have momentum of many individuals a seperate mailing list
for those efforts makes much sense. I'd ask (but don't need to since you
are already here) that any such effort contribute at least one or two english
speakers to follow the docs@httpd.apache.org and filter the info on (at least
in a digest) to the other-language communities.
Please note that that we would be happy to host such lists (in fact
we would prefer to be the authoritative resource so there isn't confusion
between competing projects, but that's another discussion) and want
to involve individuals in maintaining the documentation as distributed
with Apache releases.
I am interested (as I'm totally ignorant here) about the difference between
traditional and simplified Chinese... are the readers of one able to read
the other? How disparate are they?
>While the project going on, we do concern about the official Apache Docs
>Project, and noticed that it had upgrated to version 2.1. Although it may
>cause confusion, I decided by fetch some new XML files in version 2.1 from
>Apache CVS server to replace some old *.html.zh.gb, so, the versions we are
>working on are newer than 2.0, and older than 2.1. Since the Simplified
>Chinese translation is whole new to the Apache Releases, I think it may be
>tolerable. Do you (others) have good sugguestions about this?
To clarify...
Apache 2.0.x is in maintenance. We won't be making major changes that
make modules incompatible with one another, or causing users to modify
their configuration files between updates (at least that's the hope.)
Apache 2.1 will never exist as a release. The next release, once all of
the new features (whatever those new features turn out to be) will be
numbered 2.2.0. The 2.1 documentation is the effort to get us to 2.2.
Betas of 2.1 will probably be released, but these won't be considered GA.
Apache 2.1 docs already have big changes for the mod_auth/authn/authz
schema that makes no sense to Apache 2.0 users. That's the biggest
discrepancy. Others changes are really minor so far.
>Erik Abele wrote:
>> For example Mozilla defines the language by an ISO 639 two character
>> code in lower case, plus a ¡°-¡° to connect an ISO 3166 code in upper
>> case: If the font setting make sense to only one language used in a
>> particular region/country: for example: ¡°zh-TW¡± for Chinese used in
>Taiwan.
>
>> # ¡°zh-CN¡±: for document encoded in Simplified Chinese encodings
>> # ¡°zh-TW¡±: for document encoded in Traditional Chinese encodings
>
>How about keep Simplified Chinese docs as *.xml.zh-cn and *.html.zh-cn.gb,
>and Traditional Chinese as *.xml.zh-tw and *.html.zh.big5? I think it's
>better to make a decision ASAP without more modifications in the future,
>isn't it?
Please review http://www.ietf.org/rfc/rfc3066.txt for best practices.
I really found this page very enlightening...
http://www.loc.gov/standards/iso639-2/faq.html#23
It sites section 4.4 of http://www.loc.gov/standards/iso639-2/normtext.html
I note that your forum, in terms of metadata, Simply defines
Content-Type: text/html; charset=gb2312.
Rather than by region of dialect, I think we would be happy to simplify
this to *.xml.zh.gb which is denotes simplifed Chinese (correct?)
Your feedback, relative to ISO 639 is most appreciated! Sorry if we've
flipflopped on this, but since we have no eastern language gurus here,
we are sort of floating on input from the handful of folks who write us
about the 'correct' way. We are looking for some authoritative references
since we aren't in the standards-writing business (although many of our
members are :-)
Thanks, and great work!
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: HERE is a Simplified Chinese Manual Transalation Project going on.
Posted by kajaa <ka...@eastday.com>.
Thanks for the reply of André Malo and Erik Abele!
André Malo wrote:
> This was, however, a short summary of a somewhat complicated thing.
> I don't know about your knowledge about these issues, and especially I
> don't know which files your translation is based on. Since these
> information are neccessary for migrating your work into the apache
> repository (you probably want to contribute to both branches), we have to
> clarify that. But that should not stop us to work on it. :-)
>
> I think, it would be helpful, if you explain, what files you are using and
> how you get/got it.
This is the whole story of our Simplified Chinese Translation Project.
In the Apache distribute releases, there are many translations including
Japanese, Korean, and even Traditional Chinese, but no Simplified Chinese,
which is used by more than 1.3 billion peoples in the world, while
Traditional Chinese is used in some areas by approximately 10-20 million
peoples. As a Simplified Chinese user, I think I should do something if
possible, so the project started.
At the beginning, more than one month ago, I translated some files from
installed Apache httpd server 2.0.43 documents. For now, there are nearly
100 people participating in this project for translating and reviewing (see
our project forum, http://kajaa.bbs.us/cgi/forums.cgi?forum=2, of course in
Chinese, :) ), and there are nearly 60 pages are translated more than the
number in the Traditional Chinese translation.
While the project going on, we do concern about the official Apache Docs
Project, and noticed that it had upgrated to version 2.1. Although it may
cause confusion, I decided by fetch some new XML files in version 2.1 from
Apache CVS server to replace some old *.html.zh.gb, so, the versions we are
working on are newer than 2.0, and older than 2.1. Since the Simplified
Chinese translation is whole new to the Apache Releases, I think it may be
tolerable. Do you (others) have good sugguestions about this?
Erik Abele wrote:
> For example Mozilla defines the language by an ISO 639 two character
> code in lower case, plus a “-“ to connect an ISO 3166 code in upper
> case: If the font setting make sense to only one language used in a
> particular region/country: for example: “zh-TW” for Chinese used in
Taiwan.
> # “zh-CN”: for document encoded in Simplified Chinese encodings
> # “zh-TW”: for document encoded in Traditional Chinese encodings
How about keep Simplified Chinese docs as *.xml.zh-cn and *.html.zh-cn.gb,
and Traditional Chinese as *.xml.zh-tw and *.html.zh.big5? I think it's
better to make a decision ASAP without more modifications in the future,
isn't it?
Thanks for André Malo's detailed descriptions about CVS revision. I
mis-understood the revision number in XML files, and now it becomes clear.
kajaa
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: HERE is a Simplified Chinese Manual Transalation Project going
on.
Posted by Erik Abele <er...@codefaktor.de>.
André Malo wrote:
> * kajaa zhang wrote:
>
> <snip>
>
> ok, let's sort a bit:
>
> - simplified chinese = *.xml.zh-cn and *.html.zh-cn.gb
> - traditional chinese = *.xml.zh and *.html.zh.big5
-1, see below.
> that way? We have _at least_ at xml stage to use different language
> extensions (because they are different translations).
> But IMHO we should be so consistent to overtake the language extension also
> to the resulting html files
>
> Hmm ... While lookinhg around in the net, I find the differences between
> the "two Chineses" expressed as "zh-cn" and "zh-tw". I think, we should
> stick with it.
> What's your (or other) opinion about that?
>
Just took also a chinese lesson with Google and I can more or less
verify this.
For example Mozilla defines the language by an ISO 639 two character
code in lower case, plus a “-“ to connect an ISO 3166 code in upper
case: If the font setting make sense to only one language used in a
particular region/country: for example: “zh-TW” for Chinese used in Taiwan.
# “zh-CN”: for document encoded in Simplified Chinese encodings
# “zh-TW”: for document encoded in Traditional Chinese encodings
References:
http://www.mozilla.org/projects/intl/changefontpref2.html
http://www.oasis-open.org/cover/iso639-2a.html
http://www.geocities.com/dtmcbride/tech/charsets/chinese.html
(nd: take a look at the last URL, there are also downloadable fonts for
windows; sorry I don't have a win machine at home. As far as I can
recall you've mentioned this together with the PDF concept [didn't
forget you!])
>>Since in DEFAULT Apache httpd.conf, there are the following configs:
>
> Note, that the default is not only for the docs, it tries to be as much
> common as possible (or so ;-).
>
>>AddLanguage tw .tw
>>AddLanguage zh-tw .tw
>
> That's wrong in the default config anyway. Having some more chinese
> documents is a good reason to fix it ;-)
+1; this is really confusing :)
<snip>
cheers,
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: HERE is a Simplified Chinese Manual Transalation Project going on.
Posted by André Malo <nd...@perlig.de>.
* kajaa zhang wrote:
> Happy New Year, this is the Chinese New Year's Day!
Happy new year! ;-)
> like JHKChan said, it is not neccesary to define zh-tw and zh-hk
> because there are no autual diferences between them.
<snip>
ok, let's sort a bit:
- simplified chinese = *.xml.zh-cn and *.html.zh-cn.gb
- traditional chinese = *.xml.zh and *.html.zh.big5
that way? We have _at least_ at xml stage to use different language
extensions (because they are different translations).
But IMHO we should be so consistent to overtake the language extension also
to the resulting html files.
Hmm ... While lookinhg around in the net, I find the differences between
the "two Chineses" expressed as "zh-cn" and "zh-tw". I think, we should
stick with it.
What's your (or other) opinion about that?
> Since in DEFAULT Apache httpd.conf, there are the following configs:
Note, that the default is not only for the docs, it tries to be as much
common as possible (or so ;-).
> AddLanguage tw .tw
> AddLanguage zh-tw .tw
That's wrong in the default config anyway. Having some more chinese
documents is a good reason to fix it ;-)
>>> - the <!-- English Revision --> notes the CVS revision number of the
>>> particular english original document, so it can't be 2.0
>>
>> Oh. They _are_ useful. The docs are not static. Noting the original CVS
>> revision number at translation time will help you to track the changes and
>> keep the translation in sync.
>
> it can't be 2.0, so what it should be? 1.3? for documents version 2.0?
It should be the CVS revision number of the English original document, the
particular translation is based on. For example, see this German document:
http://cvs.apache.org/viewcvs.cgi/httpd-docs-2.0/manual/new_features_2_0.xml.de?rev=HEAD&content-type=text/vnd.viewcvs-markup
It has the CVS revision number "1.4" (which is not interesting at all) and
is based on the english CVS revision "1.5" (see in the 4th line of the
document).
The english original is here:
http://cvs.apache.org/viewcvs.cgi/httpd-docs-2.0/manual/new_features_2_0.xml?rev=HEAD&content-type=text/vnd.viewcvs-markup
You can see, it has the revision number "1.5" (which is, at this time equal
to HEAD, i.e. it is the recent version of that file), that means the german
file is up to date.
Once the original is changed, the revision will be changed, too
(automatically by CVS). Then you can make a diff between the versions and
translate the changes. To see the changes, say, between revision 1.4 and
1.5 of the original document, you simply go into your checkout directory
and type:
cvs diff -u -r1.4 -r1.5 new_features_2_0.xml >diff_file
Said that, it seems, I should to explain some more stuff (whenever there
are questions, please ask!):
As you may or may not know that we've started the development of httpd-2.1.
The current CVS repository contains (with the help of some CVS magic)
_both_ versions of the Apache httpd, and the docs, of course, too.
That means, if you do a normal CVS checkout, you'll get httpd-2.1 instead
of httpd-2.0 files. The CVS feature, which makes that possible is called
"branching". For each file, one stage of development (called "branchpoint")
is taken and splitted into two branches, one branch gets a name
(APACHE_2_0_BRANCH in the interesting case) and one stays as main
development branch (always called HEAD).
This was, however, a short summary of a somewhat complicated thing.
I don't know about your knowledge about these issues, and especially I
don't know which files your translation is based on. Since these
information are neccessary for migrating your work into the apache
repository (you probably want to contribute to both branches), we have to
clarify that. But that should not stop us to work on it. :-)
I think, it would be helpful, if you explain, what files you are using and
how you get/got it.
And remember, don't hesitate to ask about all that weird stuff until it's
all clear to you.
nd
--
>kann mir jemand sagen, was genau @-Domains sind?
Ein Mythos. Ein Werbetrick. Verarsche. Nenn es wie du willst...
-- Alexandra Buss und Björn Höhrmann in dciwam
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org