[sylpheed:33104] Re: Sylpheed documentation (was: Sylpheed 2.7.0 released)
ospite at studenti.unina.it
Sun Jul 26 07:22:44 JST 2009
On Sat, 25 Jul 2009 19:57:56 +0200
Petr Kovar <pknbe at volny.cz> wrote:
> rhubbell <Rhubbell at iHubbell.com>, Thu, 23 Jul 2009 22:32:44 -0700:
> > On Thu, 23 Jul 2009 18:43:03 -0400
> > Petr Kovar wrote:
> > --snip--snip--
> > I think we should ask the maintainer of Sylpheed, H. Yamamoto, what
> > document format would have the best chance of being released each time
> > Sylpheed is released. If the answer is xml then that's what we do.
> > And we start with an translation of the Japanese edition of the html pages
> > using one of the online translators. I'm not a doc expert or even a novice
> > but I'll try to help anyway. Doing a recursive wget of the translated
> > page would be a starting point.
> I very much agree that we need to know Hiro's view on the situation.
> As he follows this list, he'll probably give us some insight as to
> whether he's his own plans for the Sylpheed docs, or whether he seeks
> volunteers help.
> Nevertheless, since the said SGML to XML migration has already begun some
> time (well, years) ago, it'd be nothing but a step back to use completely
> deprecated tools like linuxdoc SGML. It should be also said that at the
> end, we need to work with the source documents anyway, as we only export
> the documentation to HTML when we're finished.
If the doc is in any XML format and it is going to be a 1:1 translation
of the Japanese version, then XLIFF can be used as intermediate format
for translators, I've recently come across this very interesting article
about it: http://www.ibm.com/developerworks/xml/library/x-localis2/
> > If the answer is something else then we figure it out. Just keep it
> > simple. The simpler it is the more likely it will get done and be
> > maintained. I say start easy/simple.
> That's definitely true, and we should try to search for tools and work flow
> processes that would suit needs of that not-so-big Sylpheed documentation
> best. Perhaps have the not-so-skilled contributors work with plain text or
> simple HTML, and then have the maintainer convert it to valid DocBook? Not
> That being said, I'm playing with some fancy XML editors more or less
> suitable for DocBook, like XXE, epcEdit or Vex, and hopefully find
> something that is usable enough.
> Petr Kovar
PGP public key ID: 0x4553B001
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
Q: What is the most annoying thing in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: not available
Url : http://www.sraoss.jp/pipermail/sylpheed/attachments/20090726/0ab7dd83/attachment.bin
More information about the Sylpheed