How can i uses SVN to translate the openSUSE 12.2 manual

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

How can i uses SVN to translate the openSUSE 12.2 manual

Flashbang
I want to translate the manual into a Chinese version , but the wiki
page " Documentation Contribute " gets me dizzy for it tells little
about how . Anyone could help me ? Thanks!








--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How can i uses SVN to translate the openSUSE 12.2 manual

Luiz Fernando Ranghetti-2
2012/10/5 Flashbang <[hidden email]>:
> I want to translate the manual into a Chinese version , but the wiki
> page " Documentation Contribute " gets me dizzy for it tells little
> about how . Anyone could help me ? Thanks!
>

Hi,

The 'official' workflow to translate the documentation manual is to
translate the 'en' xml files on the openSUSE SVN

http://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/
-> for visualization

Or if you are not comfortable translating xml files and prefer .po
files I have a 'not official' server with .po files managed at
www.vertaal.com.ar

In any way, its a huge task ;-)



I'm thinking that maybe we can create a task for Google Code-In to
joint and automatizate these two forms of translating, what do you
guys think?

Regards,

Luiz
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How can i uses SVN to translate the openSUSE 12.2 manual

Guillaume Gardet
Hi,


Le 05/10/2012 16:46, Luiz Fernando Ranghetti a écrit :

> 2012/10/5 Flashbang <[hidden email]>:
>> I want to translate the manual into a Chinese version , but the wiki
>> page " Documentation Contribute " gets me dizzy for it tells little
>> about how . Anyone could help me ? Thanks!
>>
> Hi,
>
> The 'official' workflow to translate the documentation manual is to
> translate the 'en' xml files on the openSUSE SVN
>
> http://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/
> -> for visualization
>
> Or if you are not comfortable translating xml files and prefer .po
> files I have a 'not official' server with .po files managed at
> www.vertaal.com.ar
>
> In any way, its a huge task ;-)
>
>
>
> I'm thinking that maybe we can create a task for Google Code-In to
> joint and automatizate these two forms of translating, what do you
> guys think?

French (fr) use POT/PO files with some script in openSUSE SVN:
http://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/fr/

We generate POT files from english XML, then create/update french PO files, then translate those PO files, then generate translated XML files from french PO files and english XML files and finally generate HTML or PDF files from translated xml files.

If needed we could move the POT folder out from FR so that all languages have access to it.

If you have any comments or questions, please ask.


Guillaume


>
> Regards,
>
> Luiz

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How can i uses SVN to translate the openSUSE 12.2 manual

Luiz Fernando Ranghetti-2
2012/10/5 Guillaume Gardet <[hidden email]>:

> Hi,
>
>
> Le 05/10/2012 16:46, Luiz Fernando Ranghetti a écrit :
>>
>> 2012/10/5 Flashbang <[hidden email]>:
>>>
>>> I want to translate the manual into a Chinese version , but the wiki
>>> page " Documentation Contribute " gets me dizzy for it tells little
>>> about how . Anyone could help me ? Thanks!
>>>
>> Hi,
>>
>> The 'official' workflow to translate the documentation manual is to
>> translate the 'en' xml files on the openSUSE SVN
>>
>> http://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/
>> -> for visualization
>>
>> Or if you are not comfortable translating xml files and prefer .po
>> files I have a 'not official' server with .po files managed at
>> www.vertaal.com.ar
>>
>> In any way, its a huge task ;-)
>>
>>
>>
>> I'm thinking that maybe we can create a task for Google Code-In to
>> joint and automatizate these two forms of translating, what do you
>> guys think?
>
>
> French (fr) use POT/PO files with some script in openSUSE SVN:
> http://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/fr/
>
> We generate POT files from english XML, then create/update french PO files,
> then translate those PO files, then generate translated XML files from
> french PO files and english XML files and finally generate HTML or PDF files
> from translated xml files.
>
> If needed we could move the POT folder out from FR so that all languages
> have access to it.
>
> If you have any comments or questions, please ask.
>
>
> Guillaume

Hi,

I think it's a great and clean solution, this way I can shut down my
'non-official' solution and move the files to openSUSE svn (of course
after contact the other teams that use it).

How to you handle the po2xml for non 100% translated files (in xml2pot
I use it has to be 100% translated). The xml2po you use leave the
untranslated string in english? (this is a good think)

Regards,

Luiz
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How can i uses SVN to translate the openSUSE 12.2 manual

Guillaume Gardet

Le 05/10/2012 17:30, Luiz Fernando Ranghetti a écrit :

> 2012/10/5 Guillaume Gardet <[hidden email]>:
>> Hi,
>>
>>
>> Le 05/10/2012 16:46, Luiz Fernando Ranghetti a écrit :
>>> 2012/10/5 Flashbang <[hidden email]>:
>>>> I want to translate the manual into a Chinese version , but the wiki
>>>> page " Documentation Contribute " gets me dizzy for it tells little
>>>> about how . Anyone could help me ? Thanks!
>>>>
>>> Hi,
>>>
>>> The 'official' workflow to translate the documentation manual is to
>>> translate the 'en' xml files on the openSUSE SVN
>>>
>>> http://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/
>>> -> for visualization
>>>
>>> Or if you are not comfortable translating xml files and prefer .po
>>> files I have a 'not official' server with .po files managed at
>>> www.vertaal.com.ar
>>>
>>> In any way, its a huge task ;-)
>>>
>>>
>>>
>>> I'm thinking that maybe we can create a task for Google Code-In to
>>> joint and automatizate these two forms of translating, what do you
>>> guys think?
>>
>> French (fr) use POT/PO files with some script in openSUSE SVN:
>> http://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/fr/
>>
>> We generate POT files from english XML, then create/update french PO files,
>> then translate those PO files, then generate translated XML files from
>> french PO files and english XML files and finally generate HTML or PDF files
>> from translated xml files.
>>
>> If needed we could move the POT folder out from FR so that all languages
>> have access to it.
>>
>> If you have any comments or questions, please ask.
>>
>>
>> Guillaume
> Hi,
>
> I think it's a great and clean solution, this way I can shut down my
> 'non-official' solution and move the files to openSUSE svn (of course
> after contact the other teams that use it).
>
> How to you handle the po2xml for non 100% translated files (in xml2pot
> I use it has to be 100% translated). The xml2po you use leave the
> untranslated string in english? (this is a good think)

Yes, xml2po leave non translated strings in english, that's all.

Guillaume


>
> Regards,
>
> Luiz
>

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How can i uses SVN to translate the openSUSE 12.2 manual

Guillaume Gardet

Le 05/10/2012 18:29, Flashbang a écrit :

> 于 2012年10月05日 23:34, Guillaume Gardet 写道:
>>
>> Le 05/10/2012 17:30, Luiz Fernando Ranghetti a écrit :
>>> 2012/10/5 Guillaume Gardet <[hidden email]>:
>>>> Hi,
>>>>
>>>>
>>>> Le 05/10/2012 16:46, Luiz Fernando Ranghetti a écrit :
>>>>> 2012/10/5 Flashbang <[hidden email]>:
>>>>>> I want to translate the manual into a Chinese version , but the wiki
>>>>>> page " Documentation Contribute " gets me dizzy for it tells little
>>>>>> about how . Anyone could help me ? Thanks!
>>>>>>
>>>>> Hi,
>>>>>
>>>>> The 'official' workflow to translate the documentation manual is to
>>>>> translate the 'en' xml files on the openSUSE SVN
>>>>>
>>>>> http://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/
>>>>>
>>>>> -> for visualization
>>>>>
>>>>> Or if you are not comfortable translating xml files and prefer .po
>>>>> files I have a 'not official' server with .po files managed at
>>>>> www.vertaal.com.ar
>>>>>
>>>>> In any way, its a huge task ;-)
>>>>>
>>>>>
>>>>>
>>>>> I'm thinking that maybe we can create a task for Google Code-In to
>>>>> joint and automatizate these two forms of translating, what do you
>>>>> guys think?
>>>>
>>>> French (fr) use POT/PO files with some script in openSUSE SVN:
>>>> http://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/fr/
>>>>
>>>>
>>>> We generate POT files from english XML, then create/update french PO
>>>> files,
>>>> then translate those PO files, then generate translated XML files from
>>>> french PO files and english XML files and finally generate HTML or
>>>> PDF files
>>>> from translated xml files.
>>>>
>>>> If needed we could move the POT folder out from FR so that all languages
>>>> have access to it.
>>>>
>>>> If you have any comments or questions, please ask.
>>>>
>>>>
>>>> Guillaume
>>> Hi,
>>>
>>> I think it's a great and clean solution, this way I can shut down my
>>> 'non-official' solution and move the files to openSUSE svn (of course
>>> after contact the other teams that use it).
>>>
>>> How to you handle the po2xml for non 100% translated files (in xml2pot
>>> I use it has to be 100% translated). The xml2po you use leave the
>>> untranslated string in english? (this is a good think)
>>
>> Yes, xml2po leave non translated strings in english, that's all.
>>
>> Guillaume
>>
>>
>>>
>>> Regards,
>>>
>>> Luiz
>>>
>>
> Hi,
>
> Glad to get replys. I think I have learned about what you said.I have two questions:How to generate xml to PO files and what is the difference between PO and POT file.

POT is a PO Template. More information here: http://en.opensuse.org/SDB:Localization_work_with_po_files

You need to make :
* XML => POT : for each file, do : "xml2po --mode=docbook -k -o file.pot file.xml" (replacing file.pot and file.xml with the right names)
* POT => PO :
   ** Create PO if it does not exist: "msginit --no-translator --locale=$lang --input=file.pot --output-file=file.$lang.po" (replacing $lang with your language code)
   ** Update PO if it already exist: "msgmerge --previous --update file.po file.pot"

You can do it manually, or use the scripts I made. (Have a look in FR folder).

If others are OK, I can move the POT folder upper to make it available for all languages. The same for scripts.

>
> I tried "svn checkout http://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/en/
> " ,but get error info:svn: E175011: Unable to connect to a repository at URL 'https://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/en'.
>
> Is there something wrong?

Bad adress. For SVN checkout, use:

svn checkouthttps://svn.opensuse.org/svn/opensuse-doc/trunk/documents/distribution/en


Regards,


Guillaume

>
> Regards,
>
> flashbang
>
>
>

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How can i uses SVN to translate the openSUSE 12.2 manual

Frank Sundermeyer
On Fri, 05 Oct 2012 18:47:08 +0200 Guillaume Gardet wrote:

Hi,

> Le 05/10/2012 18:29, Flashbang a écrit :
> > 于 2012年10月05日 23:34, Guillaume Gardet 写道:
> >>
> >> Le 05/10/2012 17:30, Luiz Fernando Ranghetti a écrit :
> >>> 2012/10/5 Guillaume Gardet <[hidden email]>:
> >>>> Hi,
> >>>>
> >>>>
> >>>> Le 05/10/2012 16:46, Luiz Fernando Ranghetti a écrit :
> >>>>> 2012/10/5 Flashbang <[hidden email]>:

> >>>> If needed we could move the POT folder out from FR so that all
> >>>> languages have access to it.

sounds very good!

> > Glad to get replys. I think I have learned about what you said.I
> > have two questions:How to generate xml to PO files and what is the
> > difference between PO and POT file.
>
> POT is a PO Template. More information here:
> http://en.opensuse.org/SDB:Localization_work_with_po_files
>
> You need to make :
> * XML => POT : for each file, do : "xml2po --mode=docbook -k -o
> file.pot file.xml" (replacing file.pot and file.xml with the right
> names)
> * POT => PO :
>    ** Create PO if it does not exist: "msginit --no-translator
> --locale=$lang --input=file.pot
> --output-file=file.$lang.po" (replacing $lang with your language
> code) ** Update PO if it already exist: "msgmerge --previous --update
> file.po file.pot"
>
> You can do it manually, or use the scripts I made. (Have a look in FR
> folder).
>
> If others are OK, I can move the POT folder upper to make it
> available for all languages. The same for scripts.

if there is anything the SUSE documentation team can do to make things
easier for you, just let us know.

I am not sure if such a thing is possible, but it would probably be of
a lot of help to have an SVN hook that automatically creates a pod
file (although I fear this is not possible, it sounds like it is
something worth looking into).

jw: I always forget this:
    How to encrypt the password so you can use it to create an svn
    account for flashback?

flashback: In order top get write access to our SVN we need a login and
           an encrypted password from you (you can freely choose both).
           jw will provide the command needed to encrypt the password.

--
Regards
        Frank

Frank Sundermeyer, Technical Writer, Documentation
SUSE Linux Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
Tel: +49-911-74053-0, Fax: +49-911-7417755;  http://www.opensuse.org/
SUSE Linux Products GmbH, GF:
Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
"Reality is always controlled by the people who are most insane" Dogbert
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How can i uses SVN to translate the openSUSE 12.2 manual

Flashbang
In reply to this post by Guillaume Gardet
于 2012年10月06日 00:47, Guillaume Gardet 写道:

>
> Le 05/10/2012 18:29, Flashbang a écrit :
>> 于 2012年10月05日 23:34, Guillaume Gardet 写道:
>>>
>>> Le 05/10/2012 17:30, Luiz Fernando Ranghetti a écrit :
>>>> 2012/10/5 Guillaume Gardet <[hidden email]>:
>>>>> Hi,
>>>>>
>>>>>
>>>>> Le 05/10/2012 16:46, Luiz Fernando Ranghetti a écrit :
>>>>>> 2012/10/5 Flashbang <[hidden email]>:
>>>>>>> I want to translate the manual into a Chinese version , but the wiki
>>>>>>> page " Documentation Contribute " gets me dizzy for it tells little
>>>>>>> about how . Anyone could help me ? Thanks!
>>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> The 'official' workflow to translate the documentation manual is to
>>>>>> translate the 'en' xml files on the openSUSE SVN
>>>>>>
>>>>>> http://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/
>>>>>>
>>>>>>
>>>>>> -> for visualization
>>>>>>
>>>>>> Or if you are not comfortable translating xml files and prefer .po
>>>>>> files I have a 'not official' server with .po files managed at
>>>>>> www.vertaal.com.ar
>>>>>>
>>>>>> In any way, its a huge task ;-)
>>>>>>
>>>>>>
>>>>>>
>>>>>> I'm thinking that maybe we can create a task for Google Code-In to
>>>>>> joint and automatizate these two forms of translating, what do you
>>>>>> guys think?
>>>>>
>>>>> French (fr) use POT/PO files with some script in openSUSE SVN:
>>>>> http://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/fr/
>>>>>
>>>>>
>>>>>
>>>>> We generate POT files from english XML, then create/update french PO
>>>>> files,
>>>>> then translate those PO files, then generate translated XML files from
>>>>> french PO files and english XML files and finally generate HTML or
>>>>> PDF files
>>>>> from translated xml files.
>>>>>
>>>>> If needed we could move the POT folder out from FR so that all
>>>>> languages
>>>>> have access to it.
>>>>>
>>>>> If you have any comments or questions, please ask.
>>>>>
>>>>>
>>>>> Guillaume
>>>> Hi,
>>>>
>>>> I think it's a great and clean solution, this way I can shut down my
>>>> 'non-official' solution and move the files to openSUSE svn (of course
>>>> after contact the other teams that use it).
>>>>
>>>> How to you handle the po2xml for non 100% translated files (in xml2pot
>>>> I use it has to be 100% translated). The xml2po you use leave the
>>>> untranslated string in english? (this is a good think)
>>>
>>> Yes, xml2po leave non translated strings in english, that's all.
>>>
>>> Guillaume
>>>
>>>
>>>>
>>>> Regards,
>>>>
>>>> Luiz
>>>>
>>>
>> Hi,
>>
>> Glad to get replys. I think I have learned about what you said.I have
>> two questions:How to generate xml to PO files and what is the
>> difference between PO and POT file.
>
> POT is a PO Template. More information here:
> http://en.opensuse.org/SDB:Localization_work_with_po_files
>
> You need to make :
> * XML => POT : for each file, do : "xml2po --mode=docbook -k -o file.pot
> file.xml" (replacing file.pot and file.xml with the right names)
> * POT => PO :
>    ** Create PO if it does not exist: "msginit --no-translator
> --locale=$lang --input=file.pot --output-file=file.$lang.po" (replacing
> $lang with your language code)
>    ** Update PO if it already exist: "msgmerge --previous --update
> file.po file.pot"
>
> You can do it manually, or use the scripts I made. (Have a look in FR
> folder).
>
> If others are OK, I can move the POT folder upper to make it available
> for all languages. The same for scripts.
>
>>
>> I tried "svn checkout
>> http://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/en/
>>
>> " ,but get error info:svn: E175011: Unable to connect to a repository
>> at URL
>> 'https://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/en'.
>>
>>
>> Is there something wrong?
>
> Bad adress. For SVN checkout, use:
>
> svn
> checkouthttps://svn.opensuse.org/svn/opensuse-doc/trunk/documents/distribution/en
>
>
>
> Regards,
>
>
> Guillaume
>
>>
>> Regards,
>>
>> flashbang
>>
>>
>>
>
Hi,

Thanks to your scripts, I have successfully generated pot and po files
from English xml files.

I am now learning the format of pot and po files,trying translating
tools such as lokalize and poEdit .


Regards,

flashbang
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How can i uses SVN to translate the openSUSE 12.2 manual

Flashbang
In reply to this post by Frank Sundermeyer
于 2012年10月06日 04:04, Frank Sundermeyer 写道:

> On Fri, 05 Oct 2012 18:47:08 +0200 Guillaume Gardet wrote:
>
> Hi,
>
>> Le 05/10/2012 18:29, Flashbang a écrit :
>>> 于 2012年10月05日 23:34, Guillaume Gardet 写道:
>>>>
>>>> Le 05/10/2012 17:30, Luiz Fernando Ranghetti a écrit :
>>>>> 2012/10/5 Guillaume Gardet <[hidden email]>:
>>>>>> Hi,
>>>>>>
>>>>>>
>>>>>> Le 05/10/2012 16:46, Luiz Fernando Ranghetti a écrit :
>>>>>>> 2012/10/5 Flashbang <[hidden email]>:
>
>>>>>> If needed we could move the POT folder out from FR so that all
>>>>>> languages have access to it.
>
> sounds very good!
>
>>> Glad to get replys. I think I have learned about what you said.I
>>> have two questions:How to generate xml to PO files and what is the
>>> difference between PO and POT file.
>>
>> POT is a PO Template. More information here:
>> http://en.opensuse.org/SDB:Localization_work_with_po_files
>>
>> You need to make :
>> * XML => POT : for each file, do : "xml2po --mode=docbook -k -o
>> file.pot file.xml" (replacing file.pot and file.xml with the right
>> names)
>> * POT => PO :
>>     ** Create PO if it does not exist: "msginit --no-translator
>> --locale=$lang --input=file.pot
>> --output-file=file.$lang.po" (replacing $lang with your language
>> code) ** Update PO if it already exist: "msgmerge --previous --update
>> file.po file.pot"
>>
>> You can do it manually, or use the scripts I made. (Have a look in FR
>> folder).
>>
>> If others are OK, I can move the POT folder upper to make it
>> available for all languages. The same for scripts.
>
> if there is anything the SUSE documentation team can do to make things
> easier for you, just let us know.
>
> I am not sure if such a thing is possible, but it would probably be of
> a lot of help to have an SVN hook that automatically creates a pod
> file (although I fear this is not possible, it sounds like it is
> something worth looking into).
>
> jw: I always forget this:
>      How to encrypt the password so you can use it to create an svn
>      account for flashback?
>
> flashback: In order top get write access to our SVN we need a login and
>             an encrypted password from you (you can freely choose both).
>             jw will provide the command needed to encrypt the password.
>
Hi,

Being new to svn and document-translation, I have to be some clever with
these tools .It will be done in a day or two and then I will get to work.

Regards,

flashbang
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How can i uses SVN to translate the openSUSE 12.2 manual

Marguerite Su
In reply to this post by Luiz Fernando Ranghetti-2
Hi, Guillaume,

The generate_POT.sh seems to need some improvement...

it mix all the <para> in 64bit_issues.xml into one <para> in POT.

then generate_localised_xml.sh add some <!ENTITY vpnclient2
"&subnetII;.111"> to the generated xmls...

finally daps don't know how to deal with them and prompt errors.

here:

https://github.com/marguerite/openSUSE-zh-manuals/blob/master/zh_CN/draft_xml/64bit_issues.xml

It seems sometimes it needs manual interrupt to compost it right...


PS:

BTW opensuse-i18n and opensuse-doc use different logins? I have full
i18n access but can't commit anything to doc.

Marguerite
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How can i uses SVN to translate the openSUSE 12.2 manual

Guillaume Gardet
Hi,

Le 08/10/2012 17:41, Marguerite Su a écrit :
> Hi, Guillaume,
>
> The generate_POT.sh seems to need some improvement...

I am opened to any improvement! :)

>
> it mix all the <para> in 64bit_issues.xml into one <para> in POT.

I do not have this problem with this file. Could you check your version of xml2po? (xml2po --version)

>
> then generate_localised_xml.sh add some <!ENTITY vpnclient2
> "&subnetII;.111"> to the generated xmls...

It is normal that ENTITY are added to XML files.

>
> finally daps don't know how to deal with them and prompt errors.
>
> here:
>
> https://github.com/marguerite/openSUSE-zh-manuals/blob/master/zh_CN/draft_xml/64bit_issues.xml
>
> It seems sometimes it needs manual interrupt to compost it right...
>
>
> PS:
>
> BTW opensuse-i18n and opensuse-doc use different logins? I have full
> i18n access but can't commit anything to doc.

Same login but maybe different rights.


Guillaume

>
> Marguerite

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How can i uses SVN to translate the openSUSE 12.2 manual

Marguerite Su
On Tue, Oct 9, 2012 at 12:06 AM, Guillaume Gardet
<[hidden email]> wrote:
> I do not have this problem with this file. Could you check your version of
> xml2po? (xml2po --version)

It's 0.20.10


Marguerite
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How can i uses SVN to translate the openSUSE 12.2 manual

Guillaume Gardet
Now I remember.

You need to patch the entity-decl.ent file with this patch:
./english-entity-decl-patch-to-fix-xml2po.patch
(available in FR folder).

Guilaume




Le 08/10/2012 18:59, Marguerite Su a écrit :
> On Tue, Oct 9, 2012 at 12:06 AM, Guillaume Gardet
> <[hidden email]> wrote:
>> I do not have this problem with this file. Could you check your version of
>> xml2po? (xml2po --version)
> It's 0.20.10
>
>
> Marguerite
>

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

EGD
Reply | Threaded
Open this post in threaded view
|

Re: How can i uses SVN to translate the openSUSE 12.2 manual

EGD
In reply to this post by Luiz Fernando Ranghetti-2
On 5 октября 2012 11:46:17 Luiz Fernando Ranghetti wrote:

> 2012/10/5 Flashbang <[hidden email]>:
> > I want to translate the manual into a Chinese version , but the wiki
> > page " Documentation Contribute " gets me dizzy for it tells little
> > about how . Anyone could help me ? Thanks!
>
> Hi,
>
> The 'official' workflow to translate the documentation manual is to
> translate the 'en' xml files on the openSUSE SVN
>
> http://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/
> -> for visualization
>
> Or if you are not comfortable translating xml files and prefer .po
> files I have a 'not official' server with .po files managed at
> www.vertaal.com.ar
>
> In any way, its a huge task ;-)

Hello,

how i add Russian team to openSUSE Guides & Manuals project?

--
Friendly openSUSE Community
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How can i uses SVN to translate the openSUSE 12.2 manual

Luiz Fernando Ranghetti-2
2012/11/21 EGD <[hidden email]>:

> On 5 октября 2012 11:46:17 Luiz Fernando Ranghetti wrote:
>> 2012/10/5 Flashbang <[hidden email]>:
>> > I want to translate the manual into a Chinese version , but the wiki
>> > page " Documentation Contribute " gets me dizzy for it tells little
>> > about how . Anyone could help me ? Thanks!
>>
>> Hi,
>>
>> The 'official' workflow to translate the documentation manual is to
>> translate the 'en' xml files on the openSUSE SVN
>>
>> http://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/
>> -> for visualization
>>
>> Or if you are not comfortable translating xml files and prefer .po
>> files I have a 'not official' server with .po files managed at
>> www.vertaal.com.ar
>>
>> In any way, its a huge task ;-)
>
> Hello,
>
> how i add Russian team to openSUSE Guides & Manuals project?
>


Hi,

I prefer that you start using the svn method that .fr use within the
openSUSE svn.

Maybe we can talk to vertaal's author to include the translations
project from openSUSE-doc project that are using .po files.


Regards,

Luiz
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How can i uses SVN to translate the openSUSE 12.2 manual

Guillaume Gardet
Hi,


Le 22/11/2012 20:22, Luiz Fernando Ranghetti a écrit :

> 2012/11/21 EGD <[hidden email]>:
>> On 5 октября 2012 11:46:17 Luiz Fernando Ranghetti wrote:
>>> 2012/10/5 Flashbang <[hidden email]>:
>>>> I want to translate the manual into a Chinese version , but the wiki
>>>> page " Documentation Contribute " gets me dizzy for it tells little
>>>> about how . Anyone could help me ? Thanks!
>>> Hi,
>>>
>>> The 'official' workflow to translate the documentation manual is to
>>> translate the 'en' xml files on the openSUSE SVN
>>>
>>> http://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/
>>> -> for visualization
>>>
>>> Or if you are not comfortable translating xml files and prefer .po
>>> files I have a 'not official' server with .po files managed at
>>> www.vertaal.com.ar
>>>
>>> In any way, its a huge task ;-)
>> Hello,
>>
>> how i add Russian team to openSUSE Guides & Manuals project?
>>
>
> Hi,
>
> I prefer that you start using the svn method that .fr use within the
> openSUSE svn.

I added 50-pot/ and 50-tools/ folders to have a cross-languages POT files support.

Currently, I only added fr to the list of supported languages.

To add a new language to it, just add it to the list in 50-tools/lang_list.inc.sh
and create a po folder (not PO, please use lower case) in your language folder and use scripts in 50-tools/.

More information in the README file:
http://svn.opensuse.org/viewvc/opensuse-doc/trunk/documents/distribution/50-tools/README


Guillaume


>
> Maybe we can talk to vertaal's author to include the translations
> project from openSUSE-doc project that are using .po files.
>
>
> Regards,
>
> Luiz

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

EGD
Reply | Threaded
Open this post in threaded view
|

Re: How can i uses SVN to translate the openSUSE 12.2 manual

EGD
On 23 ноября 2012 11:56:59 Guillaume Gardet wrote:

> Hi,
>
> I added 50-pot/ and 50-tools/ folders to have a cross-languages POT files
> support.
>
> Currently, I only added fr to the list of supported languages.
>
> To add a new language to it, just add it to the list in
> 50-tools/lang_list.inc.sh and create a po folder (not PO, please use lower
> case) in your language folder and use scripts in 50-tools/.
>

I add line on main language into lang_list.inc.sh, create po files and commit
changes.

--
Friendly openSUSE Community
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]