On Mon, Sep 20, 2010 at 22:04, Tommy He <lovenemesis(a)fedoraproject.org> wrote:
On 17 September 2010 07:18, Karsten Wade <kwade(a)redhat.com>
wrote:
> On Thu, Sep 16, 2010 at 11:13:54AM +0800, Tommy He wrote:
...
We had couples of discussions on the process of translation work (in
Chinese ;p ) during the weekend and here are some points:
...
2. reStructuredText is mentioned as an alternative to POT/PO
translation process by Zoom.Quiet (also on this mail list,
http://cut.gd/zncs), an experienced book translator in Python field
(OpenBookProject:
http://cut.gd/MUzR). Personally I have not got all
the advantages of rST translation. But judged from his achievements,
it may be a good option to consider. Perhaps Zoom.Quiet could explain
a bit about it?
reStructuredText (zip name is rST)
http://docutils.sourceforge.net/rst.html
is Markup Syntax and Parser Component of Docutils(one perfect Python
text process tools)
is one kinds of WYTIWYG style Markup Syntax ;
not like Target base text(GSML/XML/HTML etc.), just usage very simple
ASCII character to define words Structured, so when we writing:
- we face cleanly text,almost pure content of we want say,not so many
target like <title> noise us mind;
- we no need care abt. what look like when the file print out,
reStructuredText can through so many tools auto transform all kinds of
format,and can usage css to refactory what look like!
Docutils Front-End Tools
http://docutils.sourceforge.net/docs/user/tools.html
for the best, rST now had one perfect tools for book project: Sphinx
http://sphinx.pocoo.org/
this tools can:
+ auto creat one Book Project
+ auto build rST files into html/xhtml/xml/pdf ... and look like one BOOK site;
in fact ,there is so many community move from DocBook into Sphinx,
like Python v2.7 documentation
http://docs.python.org/index.html
TOSW is one great book, but not finished yet;
and y know translation is one kinds of reCreated ;
and POT/PO, translator face picese of words,
that soooo hard to translation into nature source language;
is we need get nature/smooth/readability/popular Chinese version;
i suggest redesign translation flow, base more humanness rST ;-)
3. No matter using POT/PO or rST, there should be a place to hold
those POT/PO files for easy distributing and reviewing. For me, I
would say
Transifex.net because of the pleasant Web-based PO editor. I
have been cooperating with Shotwell project on that for quite a few
releases and feeling happy about it. Though not as powerful as other
offline tools, it's quite handy for the one who wants to contribute
his/her lunch time to TOSW in work place. PS: By now none of the
prospected translators has Git commit privilege.
Simple is better, Translator Oriented Translation is better;
just base reader,
we begin from wiki, one essay by one essay, Translation Chinese,
and reader synchronism feedback suggest, so we can emerge some China
realy case as sample to help people understand FLOSS community;
so in the end, maybe relaese mainland|taiwan etc. Chinese Version ,
for help different area Chinese understand;
BOOK, not like software interface, reading is not click button,
BOOK's translaton is realy different to i18N,
so TOSW can just define the finally Deliverables, support default CSS ...
so local community can usage easy way to organization the learnning process;-)
(Yes, i means people together translation one great BOOK,is one great
learnning process!-)
--
http://zoomquiet.org 人生苦短? Pythonic!