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:
> Hello,
>
> As a member of Fedora Chinese user group, personally I think that The
> Open Source Way would be a great help to the growing Fedora Community
> in Greater China. Before start translating it into Chinese, I would
> like to hear your valuable advice on the following questions:
>
> 1. What is the plan of localization for TOSW? So far I am unable to
> find specific wiki pages on this topic. I would be very pleased to
> hear from Red Hat Community Architecture team and many other
> contributors on this topic.
>
> 2. If the localization for TOSW could work, what is the ideal place to
> host this Chinese copy? If possible, a branch of TOSW wiki would be
> the best place IMO. But if there are some practical difficulties, will
> it be OK if hosting this on other places(have not decided yet)?
These are great questions. I'm very excited that you are interested
in doing this translation.
I have thought about localization from the start, and generally have
copied the tools and processes used in the production of the Fedora
release notes. A method like this:
1. Write original copy in English on the wiki;
2. Convert that copy to XML;
3. Use PO/POT to handle i18n;
4. Build HTML & PDF in all languages.
So right now the wiki has newer content than is in XML:
https://fedorahosted.org/tosw/
The plan is to update the XML regularly from the work on the wiki; we
are overdue for an update.
One other challenge: the writing is not written well for
translation. I have experience writing technical material for
translation, and this book breaks many of the rules. It uses idioms,
breaks rules of grammar, and has a strong narrative voice.
My goal was to get a lot of content in there and work on rewriting it
over time. For now, I think we can do a close collaboration with
writer and translator. For example, when the idioms in a passage are
unclear, we discuss on list what it means, possibly change the source
to a new version, and so forth.
Perhaps there are a few folks who want to work on the wiki to XML
updating? I'll be training people how to do it while working
alongside. Perhaps we can schedule a work sprint?
- Karsten
--
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture
uri:
http://TheOpenSourceWay.org/wiki
gpg: AD0E0C41
_______________________________________________
tosw mailing list
tosw(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/tosw
Hello,
Since the call on
http://cut.gd/qFgE , I got six responses with
interesting on translating work of TOSW so far. Not a big number but a
fairly acceptable start.
We had couples of discussions on the process of translation work (in
Chinese ;p ) during the weekend and here are some points:
1. Help for upstream (perhaps from this mail list?) is needed to get
the XML up to date and POT/PO generated. If possible, it would be nice
to split into chapters. One POT/PO per chapter is kind of handy to
allocate the job.
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?
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.
4. Job allocation is on-going. Giving the current completeness of
TOSW, it might be more efficient to focus on the first six chapters.
Each prospected translator was asked about his/her preference of
chapters. This work should be done by tomorrow morning GMT+8 time.
But before all, the XML really needs updating and POT/PO file needs
generating. Sincerely hope someone could give us the translators a
hand.
Kind regards,
Tommy He