<div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Dear Torinthiel,</blockquote>
<div> </div>
<div> </div>
<div>Thank you for your advice. Thank you for your advice.</div>
<div>I'll follow your instructions.</div>
<div>It's true that I read some docs yesterday.</div>
<div>It's really a long page. But I'd like to make the tool more useful and helpful to my firends.</div>
<div>Can I send the file as an attachment when submitting?</div>
<div> </div>
<div>Sincerely,</div>
<div>Kun</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Thu, Dec 14, 2006 at 12:45:16PM +0800, Kun Niu wrote:<br>> Dear all,<br>><br>> I'm new here. And I found that the simplified doc for mplayer is outdated.
<br>> And I would like to participate in the translation.<br>> Can anyone be kind enough to tell me what I should do for the participation?<br><br>Well, Chinese doc's is so much outdated, the best thing to do is<br>
retranslate from scratch.<br><br>Now, there are three areas: the manpage, the xml docs, and the console<br>messages. In all cases, start by checkin out MPlayer from SVN and<br>reading DOCS/tech/translations.txt and DOCS/tech/patches.txt
<br><br>1) manpage: begin by reading DOCS/tech/manpage, than create your<br>directory under DOCS/man, copy the English manpage and start editing ;)<br>As for format: as long as you don't touch .sth at start of line, and<br>
anything after \ you should be safe, and should soon find out what means<br>what. Ask otherwise.<br>For encoding: choose what you think is the most popular, and don't<br>forget to mark your choice in comments in the beginning.
<br>You don't have to translate everything at once, parts are welcome as<br>well, leaving the rest in English is probably the best choice.<br><br>2) console messages: go to help subdirectory, start by copying<br>help_mp-en.h
to help_mp-zh.h (I hope I got the name correct ;)<br>and start editing. It's a simple C header file, so keep quotes around<br>text, don't touch #define MSGTR_* strings before quotes and keep the<br>"%sth" markers intact and in order. Test by running top-level configure
<br>with --language=zh, making and running MPlayer.<br>The encoding is utf-8 mandatory.<br><br>3) XML doc's: MPlayer changed it's documentation format since CHinceese<br>was updated, so now, IMHO it's easier to translate from scratch than try
<br>to copy parts from different .html files.<br>Go to the DOCS/xml directory, read README and README.maintainers there,<br>create a new directory for the translation, copy Makefile from any<br>language, make sure USE_SYMLINKS is set to yes, copy any .xml file from
<br>en/ directory and start translating. .xml files are normal text files,<br>you should find out the meaning of everything easily and if not don't<br>hesitate to ask. Try to use UTF-8 encoding, if you really can't than<br>
use whatever you like, just remember to change it in <?xml?> tag at<br>start of EACH file.<br><br>To test your translation, go to DOCS/xml directory, edit Makefile adding<br>your language directory to SUBDIRS variable, and run make. Should work,
<br>unless you don't have all the tools installed - in that case the best<br>place to look is DOCS/xml/README.<br><br>You don't have to do things in any particular order, and remember it's<br>quite some work, so if you can get some friends to help you, it's even
<br>better. When you've done something, send the files (or patches, for<br>files that already exist) here, and they'll get applied.<br>And if you have any further questions, don't hesitate to ask.<br>Torinthiel<br></blockquote>
</div>