it's migration time. What about Fedora Docs ?

[Valentin Laskov]

Hi,

It's so easy to maintain a wiki!

What do you think about migrating Fedora Docs to wiki ?

Regards,

Valentin

I apologize if this was discussed before, or if the idea sounds stupid, or 
... something else, like a ... who says "wrong mail list" ?  :)

[Cheng-Chia Tseng]

Wiki is uneasy to translate, there is no useful tool such as Poedit,
Lokalize etc. to do the work offline.

It is also hard to know that if the source language has been updated
or not without notification.

-- 
Sincerely,
by Cheng-Chia Tseng

[Valentin Laskov]

From: "Tseng, Cheng-Chia" <pswo10680(a)gmail.com&gt;
| Wiki is uneasy to translate, there is no useful tool such as Poedit,
| Lokalize etc. to do the work offline.
|
| It is also hard to know that if the source language has been updated
| or not without notification.
|
| -- 
| Sincerely,
| by Cheng-Chia Tseng
| --

Every text editor is suitable for offline work. You can easy copy-paste source of the page
from wiki to text editor and back to the 
wiki. Here is an example of main documentation in wiki [1].

Wiki provides watchlists with pages for notification upon change/update.

[1] http://wiki.blender.org/index.php/Doc:Manual

Valentin

[Domingo Becker]

2011/3/2 Valentin Laskov <laskov(a)festa.bg&gt;:
>  From: "Tseng, Cheng-Chia" <pswo10680(a)gmail.com&gt;
>  | Wiki is uneasy to translate, there is no useful tool such as Poedit,
>  | Lokalize etc. to do the work offline.
>  |
>  | It is also hard to know that if the source language has been updated
>  | or not without notification.
>  |
>  | --
>  | Sincerely,
>  | by Cheng-Chia Tseng
>  | --
>
>  Every text editor is suitable for offline work. You can easy copy-paste source of the
> page from wiki to text editor and back to the
>  wiki. Here is an example of main documentation in wiki [1].
>
>  Wiki provides watchlists with pages for notification upon change/update.
>  
I'm not from the Docs Team, but I saw a few things:

1. Docs writers don't want anyone to touch their original work. They
only accept (and sometimes they don't) comments and requests through
bugzilla. Perhaps this is the main reason why not using a wiki.
2. The same way, no one wants docs.fedoraproject.org content to be modifiable.
3. Docs writers use publican, which allows them  to write once and
produce many formats: html, html-single, pdf and epub.
4. The current workflow allows them to automate the publishing
process. You will see many times that as you translate and upload
translations, it will take 4 hours to a couple of days for your
content to be published somewhere in the web in all the formats
mentioned in 3. The automation is up to the doc-writer.

Perhaps you would get a more appropriate answer from the docs(a)l.fp.o list.

kind regards

Domingo Becker (es)

[Yuri Chornoivan]

Hi!

>  Wiki is uneasy to translate, there is no useful tool such as Poedit,
>  Lokalize etc. to do the work offline. 
In fact, TranslateWiki (TW) extension [1] offers PO export and import capabilities. KDE
uses this extension to translate UserBase [2] documentation. It is very easy to use.
Online translation memory is also included.

BTW, translation memory is not very efficient for docs translation. Moreover, Tx.net does
not offer this at all by now.

>  
>  It is also hard to know that if the source language has been updated
>  or not without notification. 
It can be easily handled by RSS or Atom feed (the news on updates can be read right from
your desktop). Very handy.

I do not like the idea of wiki documentation much, because it breaks my workflow, but it
is already broken by migration. So it can be vital solution.

Best regards,
Yuri

[1] http://translation.wikia.com/wiki/TranslateWiki:Main_Page
[2] http://userbase.kde.org/