* 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
