Mailinglist Archive: opensuse-translation (38 mails)

< Previous Next >
Re: [opensuse-translation] Translating openSuse documentation into french language
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
  • Date: Sat, 3 Jan 2009 10:41:15 +0100 (CET)
  • Message-id: <alpine.LSU.2.00.0901031024250.27242@xxxxxxxxxxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Saturday, 2009-01-03 at 09:59 +0100, manchette wrote:

i also read that the spanish community is willing to do something using
wiki (if i got it well), so would it be possible to set up a translating
structure in common ?

I'm one of the Spanish translators, but I'm not sure what you are refering
to :-?


Hello,
i misunderstood what i had 1st read, it said that some of the spanish
community where potentially interested in translating the official opensuse
documentation. Is this the case ? If so, maybe we could try to have a common
structure / platform ?

I still haven't got comments from your post, which I forwarded to our list. But yes, I'm interested, at least in learning what is needed and how could it be done. Then I'll evaluate.

I have done a translation in docbook: of the old "unofficial SuSE howto" by Togan and others. I didn't like docbook much. Even not at all. I don't want to see tokens in the middle of my text, it makes hard reading and writing. To see the result of our typing, we had to ask Togan to compile our writing and produce the pdf or html for us to proofread. Took days.

It is fine for programmers, but not for a writer. I want a tool like openoffice writer or LyX. Personally, I prefer LyX, when it works (not trivial, either).

I have also translated some man pages... I don't like that either.
Programmers do not think of translators when they design the tools for
writing documentation. They think of themselves, code and text like
code. No wonder that the documentation is often behind, and translations
much more behind than the docs in English.


i've got few informations on these technical aspects but read that docbook
makes easy translation because it allows to create .pdf and .html versions
with the same sources (?) ; also that the Linux documentation project has all
the scripts for docbook.

Yes, it is true that it allows easy conversion, if the text "compiles" correctly. You get the formatting commands inside your text. It is like writing HTML in raw. The tools I have seen put the codes in colour, but to me that is horrible. If I select a line to be a "tittle", I want to see the tittle in big letters in the proper, final or nearly final, format; not the token </title begin>.

I can't translate that way. It is not comfortable for me.


So, yes, I'm interested, and I/we need handholding. I'm interested into at least trying, or learning how to do it... depending on the tools and difficulties, I'll participate or not.

- -- Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAklfMsMACgkQtTMYHG2NR9VsFQCffXrHMmw7v6B5l9htGnLAZ8WA
XX0An1yJw8p6IDwkfQDthbhYU+nCzyhb
=R1ce
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-translation+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-translation+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups