Re: Fw: Re: [installation-guide] convert xml-based translation to po format

[Holger Wansing]

Hi,

I finally converted the manual to po format for Czech now.
So, all languages the manual is currently built for are now po-based.


Holger



Holger Wansing  wrote:
> Hi,
> 
> Holger Wansing  wrote:
> > Hi,
> > 
> > what do you think about the xml-to-po conversion?
> > Would that be a sensible solution for you?
> 
> I got not answer from Miroslav regarding this issue, so what to do about this?
> 
> Apparently it seems to be a solution for translators, to leave everything as
> is. 
> 
> Miroslav has already quoted, there is no problem for him, he quoted:
>   "There is no problem for me, as I keep copy of the last translated
>   version of the files, so I can easily diff with trunk and translate
>   what was changed since the last time, not relying on the SVN numbers."
> 
> 
> As a consequence, in the future we can not judge if Czech translation is 
> up-to-date and we need to rely on Miroslav.
> 
> However, I don't want to loose Miroslav as Czech translator (he is a 
> longstanding
> Debian contributor and Czech translator !!! )
> 
> 
> 
> Holger
> 
> 
> > Holger Wansing  wrote:
> > > Mail did not make it to the list, because of the attachment size ...
> > > Po files sent to Miroslav.
> > > 
> > > 
> > > 
> > > 
> > > Date: Mon, 21 May 2018 12:13:40 +0200
> > > From: Holger Wansing 
> > > To: Miroslav Kure 
> > > Cc: debian-boot 
> > > Subject: Re: [installation-guide] convert xml-based translation to po 
> > > format
> > > 
> > > 
> > > Hi,
> > > 
> > > Holger Wansing  wrote:
> > > > Hi,
> > > > 
> > > > Miroslav Kure  wrote:
> > > > > > The workflow for xml-based translation is based on the svn revision 
> > > > > > numbers, 
> > > > > > which are no longer available now, since the repository has been 
> > > > > > moved to git.
> > > > > > Because of that, there is now a problem to get this workflow 
> > > > > > running again
> > > > > > for git.
> > > > > 
> > > > > There is no problem for me, as I keep copy of the last translated
> > > > > version of the files, so I can easily diff with trunk and translate
> > > > > what was changed since the last time, not relying on the SVN numbers.
> > > > > 
> > > > > > Do you have any objections against the conversion to po format for 
> > > > > > Czech?
> > > > > > For po format we have a possible way to get the workflow running 
> > > > > > again.
> > > > > 
> > > > > I am not too fond of having longer texts in PO format, but I guess you
> > > > > can try to run the conversion script so we can see how much work it
> > > > > would require to clean up after the conversion.
> > > 
> > > I have completed the conversion now.
> > > The resulting po files are attached.
> > > The manual builds fine based on that files.
> > > 
> > > The xml version was partly not in exact sync with English, so the 
> > > automatic
> > > conversion did not work at all for some chapters.
> > > This all results in several fuzzies and untranslated strings.
> > > Please update the attached files.
> > > 
> > > Thanks
> > > Holger
> > > 
> > > 
> > > 
> > > -- 
> > > 
> > > Created with Sylpheed 3.5.1 under 
> > >   D E B I A N   L I N U X   9   " S T R E T C H " .
> > > 
> > > Registered Linux User #311290 - https://linuxcounter.net/
> > > 
> > > 
> > 
> > 
> > -- 
> > 
> > Created with Sylpheed 3.5.1 under 
> > D E B I A N   L I N U X   9   " S T R E T C H " .
> > 
> > Registered Linux User #311290 - https://linuxcounter.net/
> > 
> > 
> 
> 
> -- 
> 
> Created with Sylpheed 3.5.1 under 
>   D E B I A N   L I N U X   9   " S T R E T C H " .
> 
> Registered Linux User #311290 - https://linuxcounter.net/
> 


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Fw: Re: [installation-guide] convert xml-based translation to po format

[Holger Wansing]

Hi,

Holger Wansing  wrote:
> Hi,
> 
> what do you think about the xml-to-po conversion?
> Would that be a sensible solution for you?

I got not answer from Miroslav regarding this issue, so what to do about this?

Apparently it seems to be a solution for translators, to leave everything as
is. 

Miroslav has already quoted, there is no problem for him, he quoted:
"There is no problem for me, as I keep copy of the last translated
version of the files, so I can easily diff with trunk and translate
what was changed since the last time, not relying on the SVN numbers."


As a consequence, in the future we can not judge if Czech translation is 
up-to-date and we need to rely on Miroslav.

However, I don't want to loose Miroslav as Czech translator (he is a 
longstanding
Debian contributor and Czech translator !!! )



Holger


> Holger Wansing  wrote:
> > Mail did not make it to the list, because of the attachment size ...
> > Po files sent to Miroslav.
> > 
> > 
> > 
> > 
> > Date: Mon, 21 May 2018 12:13:40 +0200
> > From: Holger Wansing 
> > To: Miroslav Kure 
> > Cc: debian-boot 
> > Subject: Re: [installation-guide] convert xml-based translation to po format
> > 
> > 
> > Hi,
> > 
> > Holger Wansing  wrote:
> > > Hi,
> > > 
> > > Miroslav Kure  wrote:
> > > > > The workflow for xml-based translation is based on the svn revision 
> > > > > numbers, 
> > > > > which are no longer available now, since the repository has been 
> > > > > moved to git.
> > > > > Because of that, there is now a problem to get this workflow running 
> > > > > again
> > > > > for git.
> > > > 
> > > > There is no problem for me, as I keep copy of the last translated
> > > > version of the files, so I can easily diff with trunk and translate
> > > > what was changed since the last time, not relying on the SVN numbers.
> > > > 
> > > > > Do you have any objections against the conversion to po format for 
> > > > > Czech?
> > > > > For po format we have a possible way to get the workflow running 
> > > > > again.
> > > > 
> > > > I am not too fond of having longer texts in PO format, but I guess you
> > > > can try to run the conversion script so we can see how much work it
> > > > would require to clean up after the conversion.
> > 
> > I have completed the conversion now.
> > The resulting po files are attached.
> > The manual builds fine based on that files.
> > 
> > The xml version was partly not in exact sync with English, so the automatic
> > conversion did not work at all for some chapters.
> > This all results in several fuzzies and untranslated strings.
> > Please update the attached files.
> > 
> > Thanks
> > Holger
> > 
> > 
> > 
> > -- 
> > 
> > Created with Sylpheed 3.5.1 under 
> > D E B I A N   L I N U X   9   " S T R E T C H " .
> > 
> > Registered Linux User #311290 - https://linuxcounter.net/
> > 
> > 
> 
> 
> -- 
> 
> Created with Sylpheed 3.5.1 under 
>   D E B I A N   L I N U X   9   " S T R E T C H " .
> 
> Registered Linux User #311290 - https://linuxcounter.net/
> 
> 


-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Re: Fw: Re: [installation-guide] convert xml-based translation to po format

[Holger Wansing]

Hi,

what do you think about the xml-to-po conversion?
Would that be a sensible solution for you?

Greetings
Holger



Holger Wansing  wrote:
> Mail did not make it to the list, because of the attachment size ...
> Po files sent to Miroslav.
> 
> 
> 
> 
> Date: Mon, 21 May 2018 12:13:40 +0200
> From: Holger Wansing 
> To: Miroslav Kure 
> Cc: debian-boot 
> Subject: Re: [installation-guide] convert xml-based translation to po format
> 
> 
> Hi,
> 
> Holger Wansing  wrote:
> > Hi,
> > 
> > Miroslav Kure  wrote:
> > > > The workflow for xml-based translation is based on the svn revision 
> > > > numbers, 
> > > > which are no longer available now, since the repository has been moved 
> > > > to git.
> > > > Because of that, there is now a problem to get this workflow running 
> > > > again
> > > > for git.
> > > 
> > > There is no problem for me, as I keep copy of the last translated
> > > version of the files, so I can easily diff with trunk and translate
> > > what was changed since the last time, not relying on the SVN numbers.
> > > 
> > > > Do you have any objections against the conversion to po format for 
> > > > Czech?
> > > > For po format we have a possible way to get the workflow running again.
> > > 
> > > I am not too fond of having longer texts in PO format, but I guess you
> > > can try to run the conversion script so we can see how much work it
> > > would require to clean up after the conversion.
> 
> I have completed the conversion now.
> The resulting po files are attached.
> The manual builds fine based on that files.
> 
> The xml version was partly not in exact sync with English, so the automatic
> conversion did not work at all for some chapters.
> This all results in several fuzzies and untranslated strings.
> Please update the attached files.
> 
> Thanks
> Holger
> 
> 
> 
> -- 
> 
> Created with Sylpheed 3.5.1 under 
>   D E B I A N   L I N U X   9   " S T R E T C H " .
> 
> Registered Linux User #311290 - https://linuxcounter.net/
> 
> 


-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Fw: Re: [installation-guide] convert xml-based translation to po format

[Holger Wansing]

Mail did not make it to the list, because of the attachment size ...
Po files sent to Miroslav.




Date: Mon, 21 May 2018 12:13:40 +0200
From: Holger Wansing 
To: Miroslav Kure 
Cc: debian-boot 
Subject: Re: [installation-guide] convert xml-based translation to po format


Hi,

Holger Wansing  wrote:
> Hi,
> 
> Miroslav Kure  wrote:
> > > The workflow for xml-based translation is based on the svn revision 
> > > numbers, 
> > > which are no longer available now, since the repository has been moved to 
> > > git.
> > > Because of that, there is now a problem to get this workflow running again
> > > for git.
> > 
> > There is no problem for me, as I keep copy of the last translated
> > version of the files, so I can easily diff with trunk and translate
> > what was changed since the last time, not relying on the SVN numbers.
> > 
> > > Do you have any objections against the conversion to po format for Czech?
> > > For po format we have a possible way to get the workflow running again.
> > 
> > I am not too fond of having longer texts in PO format, but I guess you
> > can try to run the conversion script so we can see how much work it
> > would require to clean up after the conversion.

I have completed the conversion now.
The resulting po files are attached.
The manual builds fine based on that files.

The xml version was partly not in exact sync with English, so the automatic
conversion did not work at all for some chapters.
This all results in several fuzzies and untranslated strings.
Please update the attached files.

Thanks
Holger



-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/