Re: Build error

[Daniel Mustieles García via gnome-i18n]

Look at this string:

msgid "Purge trash  temporary files"
msgstr "Prullenbak legen & tijdelijke bestanden definitief verwijderen"

It might be the & what it's breaking the build.

I don't know what gtml is but it doesn't seem to the same as gtxml... to
make gtxml work you have to download PyG3t (see previous email to get the
link). It very easy to compile and install it, but if you get stuck I could
help you with it.

Hope this helps.

Regards

El jue, 20 may 2021 a las 10:04, hannie () escribió:

> Sorry guys, but the errors are not yet fixed. I fixed the 3 tag errors
> André mentioned here, but I still get this build error. And uploading
> Daniel's attached file did not work either.
> I also tried Daniel's gtxml -c  command, but it does not work
> in Ubuntu. I will have to do further reading to try and get gtml working.
> Hannie
>
> Op 18-05-2021 om 10:52 schreef Andre Klapper via gnome-i18n:
> > On Tue, 2021-05-18 at 10:20 +0200, Hannie Dumoleyn wrote:
> >> Entity: line 1: parser error : Premature end of data in tag p line 1
> >>
> >> Can anyone help?
> > "Open het Systeemmenu
> > aan de rechterzijde van de bovenbalk." and "Kies welk apparaat,
> > Wifi" and "Energie" are broken markup.
> >
> > Cheers,
> > andre
> > --
> > Andre Klapper  |  ak...@gmx.net
> > https://blogs.gnome.org/aklapper/
> >
> >
> > ___
> > gnome-i18n mailing list
> > gnome-i18n@gnome.org
> > https://mail.gnome.org/mailman/listinfo/gnome-i18n
>
>
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[hannie]

Sorry guys, but the errors are not yet fixed. I fixed the 3 tag errors 
André mentioned here, but I still get this build error. And uploading 
Daniel's attached file did not work either.
I also tried Daniel's gtxml -c  command, but it does not work 
in Ubuntu. I will have to do further reading to try and get gtml working.

Hannie

Op 18-05-2021 om 10:52 schreef Andre Klapper via gnome-i18n:

On Tue, 2021-05-18 at 10:20 +0200, Hannie Dumoleyn wrote:

Entity: line 1: parser error : Premature end of data in tag p line 1

Can anyone help?

"Open het Systeemmenu
aan de rechterzijde van de bovenbalk." and "Kies welk apparaat,
Wifi" and "Energie" are broken markup.

Cheers,
andre
--
Andre Klapper  |  ak...@gmx.net
https://blogs.gnome.org/aklapper/


___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n



___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[hannie]

Hello André and Daniel,
Thank you for your help, it worked!
Hannie

Op 18-05-2021 om 10:52 schreef Andre Klapper via gnome-i18n:

On Tue, 2021-05-18 at 10:20 +0200, Hannie Dumoleyn wrote:

Entity: line 1: parser error : Premature end of data in tag p line 1

Can anyone help?

"Open het Systeemmenu
aan de rechterzijde van de bovenbalk." and "Kies welk apparaat,
Wifi" and "Energie" are broken markup.

Cheers,
andre
--
Andre Klapper  |  ak...@gmx.net
https://blogs.gnome.org/aklapper/


___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n



___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Andre Klapper via gnome-i18n]

On Tue, 2021-05-18 at 10:20 +0200, Hannie Dumoleyn wrote:
> Entity: line 1: parser error : Premature end of data in tag p line 1
>
> Can anyone help?

"Open het Systeemmenu
aan de rechterzijde van de bovenbalk." and "Kies welk apparaat,
Wifi" and "Energie" are broken markup.

Cheers,
andre
--
Andre Klapper  |  ak...@gmx.net
https://blogs.gnome.org/aklapper/


___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Build error

[Hannie Dumoleyn]

On https://l10n.gnome.org/vertimus/gnome-user-docs/master/gnome-help/nl/ 
I get the following error message:


Build failed (itstool): Error: Could not merge translations: Entity: 
line 1: parser error : Opening and ending tag mismatch: gui line 1 and p 
Entity: line 1: parser error : Premature end of data in tag p line 1


In terminal I tried this:
msgfmt -cv -o /dev/null 
gnome-user-docs-master-gnome-help-nl-241183.merged.po


Reply: 2593 translated, 516 fuzzy, 208 untransated.

I opened the .po file in Gedit, but there is no tag p in line 1.

Can anyone help?

Hannie


___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Rafael Fontenelle]

Awesome, thanks Daniel and Claude for making our translation platform better.

Em qua., 11 de mar. de 2020 às 10:25, Daniel Mustieles García via
gnome-i18n  escreveu:
>
> Great, thanks!
>
> El mié., 11 mar. 2020 a las 14:20, Claude Paroz () 
> escribió:
>>
>> Should be OK now, thanks for re-applying.
>>
>> Claude
>>
>> Le 11.03.20 à 08:48, Daniel Mustieles García a écrit :
>> > Sure, I've reverted the commit I did, so LINGUAS is again called from
>> > Makefile.
>> >
>> > Thanks Claude!
>> >
>> > El mié., 11 mar. 2020 a las 8:30, Claude Paroz (> > >) escribió:
>> >
>> > I'm sorry, I didn't check if the LINGUAS thing was working for
>> > release-notes. I would have fixed D-L if I had known.
>> >
>> > Maybe you could re-apply the LINGUAS patch and I'll fix D-L ASAP. Just
>> > tell me.
>> >
>> > Claude
>> >
>> > Le 11.03.20 à 08:21, Daniel Mustieles García via gnome-i18n a écrit :
>> > > We can watch it and add new languages to Makefile if they are
>> > added into
>> > > DL, there is no problem with it.
>> > >
>> > > About DL, yes, it would be great if it would allow doing things
>> > like you
>> > > did, but it doesn't. The best option would be adding new languages
>> > > automagically to Makefile, but it was difficult to implement properly
>> > >
>> > > El mar., 10 mar. 2020 a las 23:00, Rafael Fontenelle
>> > > (mailto:rafae...@gnome.org>
>> > >>) escribió:
>> > >
>> > > Hi Daniel,
>> > >
>> > > I notice the warning, but I'm afraid that D-L might allow
>> > adding new
>> > > translation to Release Notes by adding it to the LINGUAS file, 
>> > and
>> > > right now Release Notes does not read the LINGUAS file.  Don't 
>> > you
>> > > think this can be a problem like translation being added but not
>> > > effectively enabled?
>> > >
>> > > Em ter., 10 de mar. de 2020 às 18:55, Daniel Mustieles García
>> > > > > 
>> > > > >>
>> > > escreveu:
>> > > >
>> > > > Hi Rafael,
>> > > >
>> > > > I've done it because DL was not able to read languages variable
>> > > from the Makefile, showing warnings in every language shown in DL
>> > > for release-notes module.
>> > > >
>> > > > I know adding languages manually to Makefile is not the best
>> > > option, but that's the way it's done in other modules and
>> > avoids DL
>> > > showing warnings.
>> > > >
>> > > > Maybe I should have noticed you before applying it, sorry. Hope
>> > > you understand why I made that change.
>> > > >
>> > > > Regards
>> > > >
>> > > > El mar., 10 mar. 2020 22:10, Rafael Fontenelle
>> > mailto:rafae...@gnome.org>
>> > > >> 
>> > escribió:
>> > > >>
>> > > >> Hello Daniel,
>> > > >>
>> > > >> I notice you partially reverted the addition of LINGUAS to
>> > > >> release-notes, which might cause new translations added via
>> > Damned
>> > > >> Lies to not be made available to the resulting
>> > documentation. Can
>> > > >> please explain your reasons?
>> > > >>
>> > > >> Best regards,
>> > > >> Rafael Fontenelle
>
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Daniel Mustieles García via gnome-i18n]

Great, thanks!

El mié., 11 mar. 2020 a las 14:20, Claude Paroz ()
escribió:

> Should be OK now, thanks for re-applying.
>
> Claude
>
> Le 11.03.20 à 08:48, Daniel Mustieles García a écrit :
> > Sure, I've reverted the commit I did, so LINGUAS is again called from
> > Makefile.
> >
> > Thanks Claude!
> >
> > El mié., 11 mar. 2020 a las 8:30, Claude Paroz ( > >) escribió:
> >
> > I'm sorry, I didn't check if the LINGUAS thing was working for
> > release-notes. I would have fixed D-L if I had known.
> >
> > Maybe you could re-apply the LINGUAS patch and I'll fix D-L ASAP.
> Just
> > tell me.
> >
> > Claude
> >
> > Le 11.03.20 à 08:21, Daniel Mustieles García via gnome-i18n a écrit :
> > > We can watch it and add new languages to Makefile if they are
> > added into
> > > DL, there is no problem with it.
> > >
> > > About DL, yes, it would be great if it would allow doing things
> > like you
> > > did, but it doesn't. The best option would be adding new languages
> > > automagically to Makefile, but it was difficult to implement
> properly
> > >
> > > El mar., 10 mar. 2020 a las 23:00, Rafael Fontenelle
> > > (mailto:rafae...@gnome.org>
> > >>) escribió:
> > >
> > > Hi Daniel,
> > >
> > > I notice the warning, but I'm afraid that D-L might allow
> > adding new
> > > translation to Release Notes by adding it to the LINGUAS file,
> and
> > > right now Release Notes does not read the LINGUAS file.  Don't
> you
> > > think this can be a problem like translation being added but
> not
> > > effectively enabled?
> > >
> > > Em ter., 10 de mar. de 2020 às 18:55, Daniel Mustieles García
> > >  > 
> > >>
> > > escreveu:
> > > >
> > > > Hi Rafael,
> > > >
> > > > I've done it because DL was not able to read languages
> variable
> > > from the Makefile, showing warnings in every language shown in
> DL
> > > for release-notes module.
> > > >
> > > > I know adding languages manually to Makefile is not the best
> > > option, but that's the way it's done in other modules and
> > avoids DL
> > > showing warnings.
> > > >
> > > > Maybe I should have noticed you before applying it, sorry.
> Hope
> > > you understand why I made that change.
> > > >
> > > > Regards
> > > >
> > > > El mar., 10 mar. 2020 22:10, Rafael Fontenelle
> > mailto:rafae...@gnome.org>
> > > >>
> escribió:
> > > >>
> > > >> Hello Daniel,
> > > >>
> > > >> I notice you partially reverted the addition of LINGUAS to
> > > >> release-notes, which might cause new translations added via
> > Damned
> > > >> Lies to not be made available to the resulting
> > documentation. Can
> > > >> please explain your reasons?
> > > >>
> > > >> Best regards,
> > > >> Rafael Fontenelle
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Claude Paroz]

Should be OK now, thanks for re-applying.

Claude

Le 11.03.20 à 08:48, Daniel Mustieles García a écrit :
> Sure, I've reverted the commit I did, so LINGUAS is again called from
> Makefile.
> 
> Thanks Claude!
> 
> El mié., 11 mar. 2020 a las 8:30, Claude Paroz ( >) escribió:
> 
> I'm sorry, I didn't check if the LINGUAS thing was working for
> release-notes. I would have fixed D-L if I had known.
> 
> Maybe you could re-apply the LINGUAS patch and I'll fix D-L ASAP. Just
> tell me.
> 
> Claude
> 
> Le 11.03.20 à 08:21, Daniel Mustieles García via gnome-i18n a écrit :
> > We can watch it and add new languages to Makefile if they are
> added into
> > DL, there is no problem with it.
> >
> > About DL, yes, it would be great if it would allow doing things
> like you
> > did, but it doesn't. The best option would be adding new languages
> > automagically to Makefile, but it was difficult to implement properly
> >
> > El mar., 10 mar. 2020 a las 23:00, Rafael Fontenelle
> > (mailto:rafae...@gnome.org>
> >>) escribió:
> >
> >     Hi Daniel,
> >
> >     I notice the warning, but I'm afraid that D-L might allow
> adding new
> >     translation to Release Notes by adding it to the LINGUAS file, and
> >     right now Release Notes does not read the LINGUAS file.  Don't you
> >     think this can be a problem like translation being added but not
> >     effectively enabled?
> >
> >     Em ter., 10 de mar. de 2020 às 18:55, Daniel Mustieles García
> >      
> >>
> >     escreveu:
> >     >
> >     > Hi Rafael,
> >     >
> >     > I've done it because DL was not able to read languages variable
> >     from the Makefile, showing warnings in every language shown in DL
> >     for release-notes module.
> >     >
> >     > I know adding languages manually to Makefile is not the best
> >     option, but that's the way it's done in other modules and
> avoids DL
> >     showing warnings.
> >     >
> >     > Maybe I should have noticed you before applying it, sorry. Hope
> >     you understand why I made that change.
> >     >
> >     > Regards
> >     >
> >     > El mar., 10 mar. 2020 22:10, Rafael Fontenelle
> mailto:rafae...@gnome.org>
> >     >> escribió:
> >     >>
> >     >> Hello Daniel,
> >     >>
> >     >> I notice you partially reverted the addition of LINGUAS to
> >     >> release-notes, which might cause new translations added via
> Damned
> >     >> Lies to not be made available to the resulting
> documentation. Can
> >     >> please explain your reasons?
> >     >>
> >     >> Best regards,
> >     >> Rafael Fontenelle
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Daniel Mustieles García via gnome-i18n]

Sure, I've reverted the commit I did, so LINGUAS is again called from
Makefile.

Thanks Claude!

El mié., 11 mar. 2020 a las 8:30, Claude Paroz ()
escribió:

> I'm sorry, I didn't check if the LINGUAS thing was working for
> release-notes. I would have fixed D-L if I had known.
>
> Maybe you could re-apply the LINGUAS patch and I'll fix D-L ASAP. Just
> tell me.
>
> Claude
>
> Le 11.03.20 à 08:21, Daniel Mustieles García via gnome-i18n a écrit :
> > We can watch it and add new languages to Makefile if they are added into
> > DL, there is no problem with it.
> >
> > About DL, yes, it would be great if it would allow doing things like you
> > did, but it doesn't. The best option would be adding new languages
> > automagically to Makefile, but it was difficult to implement properly
> >
> > El mar., 10 mar. 2020 a las 23:00, Rafael Fontenelle
> > (mailto:rafae...@gnome.org>>) escribió:
> >
> > Hi Daniel,
> >
> > I notice the warning, but I'm afraid that D-L might allow adding new
> > translation to Release Notes by adding it to the LINGUAS file, and
> > right now Release Notes does not read the LINGUAS file.  Don't you
> > think this can be a problem like translation being added but not
> > effectively enabled?
> >
> > Em ter., 10 de mar. de 2020 às 18:55, Daniel Mustieles García
> > mailto:daniel.mustie...@gmail.com>>
> > escreveu:
> > >
> > > Hi Rafael,
> > >
> > > I've done it because DL was not able to read languages variable
> > from the Makefile, showing warnings in every language shown in DL
> > for release-notes module.
> > >
> > > I know adding languages manually to Makefile is not the best
> > option, but that's the way it's done in other modules and avoids DL
> > showing warnings.
> > >
> > > Maybe I should have noticed you before applying it, sorry. Hope
> > you understand why I made that change.
> > >
> > > Regards
> > >
> > > El mar., 10 mar. 2020 22:10, Rafael Fontenelle  > > escribió:
> > >>
> > >> Hello Daniel,
> > >>
> > >> I notice you partially reverted the addition of LINGUAS to
> > >> release-notes, which might cause new translations added via Damned
> > >> Lies to not be made available to the resulting documentation. Can
> > >> please explain your reasons?
> > >>
> > >> Best regards,
> > >> Rafael Fontenelle
>
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> https://mail.gnome.org/mailman/listinfo/gnome-i18n
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Claude Paroz]

I'm sorry, I didn't check if the LINGUAS thing was working for
release-notes. I would have fixed D-L if I had known.

Maybe you could re-apply the LINGUAS patch and I'll fix D-L ASAP. Just
tell me.

Claude

Le 11.03.20 à 08:21, Daniel Mustieles García via gnome-i18n a écrit :
> We can watch it and add new languages to Makefile if they are added into
> DL, there is no problem with it.
> 
> About DL, yes, it would be great if it would allow doing things like you
> did, but it doesn't. The best option would be adding new languages
> automagically to Makefile, but it was difficult to implement properly
> 
> El mar., 10 mar. 2020 a las 23:00, Rafael Fontenelle
> (mailto:rafae...@gnome.org>>) escribió:
> 
> Hi Daniel,
> 
> I notice the warning, but I'm afraid that D-L might allow adding new
> translation to Release Notes by adding it to the LINGUAS file, and
> right now Release Notes does not read the LINGUAS file.  Don't you
> think this can be a problem like translation being added but not
> effectively enabled?
> 
> Em ter., 10 de mar. de 2020 às 18:55, Daniel Mustieles García
> mailto:daniel.mustie...@gmail.com>>
> escreveu:
> >
> > Hi Rafael,
> >
> > I've done it because DL was not able to read languages variable
> from the Makefile, showing warnings in every language shown in DL
> for release-notes module.
> >
> > I know adding languages manually to Makefile is not the best
> option, but that's the way it's done in other modules and avoids DL
> showing warnings.
> >
> > Maybe I should have noticed you before applying it, sorry. Hope
> you understand why I made that change.
> >
> > Regards
> >
> > El mar., 10 mar. 2020 22:10, Rafael Fontenelle  > escribió:
> >>
> >> Hello Daniel,
> >>
> >> I notice you partially reverted the addition of LINGUAS to
> >> release-notes, which might cause new translations added via Damned
> >> Lies to not be made available to the resulting documentation. Can
> >> please explain your reasons?
> >>
> >> Best regards,
> >> Rafael Fontenelle

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Daniel Mustieles García via gnome-i18n]

We can watch it and add new languages to Makefile if they are added into
DL, there is no problem with it.

About DL, yes, it would be great if it would allow doing things like you
did, but it doesn't. The best option would be adding new languages
automagically to Makefile, but it was difficult to implement properly

El mar., 10 mar. 2020 a las 23:00, Rafael Fontenelle ()
escribió:

> Hi Daniel,
>
> I notice the warning, but I'm afraid that D-L might allow adding new
> translation to Release Notes by adding it to the LINGUAS file, and
> right now Release Notes does not read the LINGUAS file.  Don't you
> think this can be a problem like translation being added but not
> effectively enabled?
>
> Em ter., 10 de mar. de 2020 às 18:55, Daniel Mustieles García
>  escreveu:
> >
> > Hi Rafael,
> >
> > I've done it because DL was not able to read languages variable from the
> Makefile, showing warnings in every language shown in DL for release-notes
> module.
> >
> > I know adding languages manually to Makefile is not the best option, but
> that's the way it's done in other modules and avoids DL showing warnings.
> >
> > Maybe I should have noticed you before applying it, sorry. Hope you
> understand why I made that change.
> >
> > Regards
> >
> > El mar., 10 mar. 2020 22:10, Rafael Fontenelle 
> escribió:
> >>
> >> Hello Daniel,
> >>
> >> I notice you partially reverted the addition of LINGUAS to
> >> release-notes, which might cause new translations added via Damned
> >> Lies to not be made available to the resulting documentation. Can
> >> please explain your reasons?
> >>
> >> Best regards,
> >> Rafael Fontenelle
> >>
> >> Em seg., 9 de mar. de 2020 às 15:49, Rafael Fontenelle
> >>  escreveu:
> >> >
> >> > Em seg., 9 de mar. de 2020 às 12:50, Link Dupont 
> escreveu:
> >> > >
> >> > > Thanks for the MR Rafael. I just merged it. Don't worry about
> opening
> >> > > an MR against master right now. master is very outdated. The current
> >> > > branching process is to branch off the previous gnome-3-xx version
> (so
> >> > > for example, I branched off gnome-3-34 to create gnome-3-36). I
> plan on
> >> > > cleaning up master after 3.36 is done so that we properly branch off
> >> > > master for each release, like other modules do.
> >> > >
> >> >
> >> > Thanks for merging it!
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Rafael Fontenelle]

Hi Daniel,

I notice the warning, but I'm afraid that D-L might allow adding new
translation to Release Notes by adding it to the LINGUAS file, and
right now Release Notes does not read the LINGUAS file.  Don't you
think this can be a problem like translation being added but not
effectively enabled?

Em ter., 10 de mar. de 2020 às 18:55, Daniel Mustieles García
 escreveu:
>
> Hi Rafael,
>
> I've done it because DL was not able to read languages variable from the 
> Makefile, showing warnings in every language shown in DL for release-notes 
> module.
>
> I know adding languages manually to Makefile is not the best option, but 
> that's the way it's done in other modules and avoids DL showing warnings.
>
> Maybe I should have noticed you before applying it, sorry. Hope you 
> understand why I made that change.
>
> Regards
>
> El mar., 10 mar. 2020 22:10, Rafael Fontenelle  escribió:
>>
>> Hello Daniel,
>>
>> I notice you partially reverted the addition of LINGUAS to
>> release-notes, which might cause new translations added via Damned
>> Lies to not be made available to the resulting documentation. Can
>> please explain your reasons?
>>
>> Best regards,
>> Rafael Fontenelle
>>
>> Em seg., 9 de mar. de 2020 às 15:49, Rafael Fontenelle
>>  escreveu:
>> >
>> > Em seg., 9 de mar. de 2020 às 12:50, Link Dupont  
>> > escreveu:
>> > >
>> > > Thanks for the MR Rafael. I just merged it. Don't worry about opening
>> > > an MR against master right now. master is very outdated. The current
>> > > branching process is to branch off the previous gnome-3-xx version (so
>> > > for example, I branched off gnome-3-34 to create gnome-3-36). I plan on
>> > > cleaning up master after 3.36 is done so that we properly branch off
>> > > master for each release, like other modules do.
>> > >
>> >
>> > Thanks for merging it!
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Daniel Mustieles García via gnome-i18n]

Hi Rafael,

I've done it because DL was not able to read languages variable from the
Makefile, showing warnings in every language shown in DL for release-notes
module.

I know adding languages manually to Makefile is not the best option, but
that's the way it's done in other modules and avoids DL showing warnings.

Maybe I should have noticed you before applying it, sorry. Hope you
understand why I made that change.

Regards

El mar., 10 mar. 2020 22:10, Rafael Fontenelle 
escribió:

> Hello Daniel,
>
> I notice you partially reverted the addition of LINGUAS to
> release-notes, which might cause new translations added via Damned
> Lies to not be made available to the resulting documentation. Can
> please explain your reasons?
>
> Best regards,
> Rafael Fontenelle
>
> Em seg., 9 de mar. de 2020 às 15:49, Rafael Fontenelle
>  escreveu:
> >
> > Em seg., 9 de mar. de 2020 às 12:50, Link Dupont 
> escreveu:
> > >
> > > Thanks for the MR Rafael. I just merged it. Don't worry about opening
> > > an MR against master right now. master is very outdated. The current
> > > branching process is to branch off the previous gnome-3-xx version (so
> > > for example, I branched off gnome-3-34 to create gnome-3-36). I plan on
> > > cleaning up master after 3.36 is done so that we properly branch off
> > > master for each release, like other modules do.
> > >
> >
> > Thanks for merging it!
>
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Rafael Fontenelle]

Hello Daniel,

I notice you partially reverted the addition of LINGUAS to
release-notes, which might cause new translations added via Damned
Lies to not be made available to the resulting documentation. Can
please explain your reasons?

Best regards,
Rafael Fontenelle

Em seg., 9 de mar. de 2020 às 15:49, Rafael Fontenelle
 escreveu:
>
> Em seg., 9 de mar. de 2020 às 12:50, Link Dupont  escreveu:
> >
> > Thanks for the MR Rafael. I just merged it. Don't worry about opening
> > an MR against master right now. master is very outdated. The current
> > branching process is to branch off the previous gnome-3-xx version (so
> > for example, I branched off gnome-3-34 to create gnome-3-36). I plan on
> > cleaning up master after 3.36 is done so that we properly branch off
> > master for each release, like other modules do.
> >
>
> Thanks for merging it!
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Rafael Fontenelle]

Em seg., 9 de mar. de 2020 às 12:50, Link Dupont  escreveu:
>
> Thanks for the MR Rafael. I just merged it. Don't worry about opening
> an MR against master right now. master is very outdated. The current
> branching process is to branch off the previous gnome-3-xx version (so
> for example, I branched off gnome-3-34 to create gnome-3-36). I plan on
> cleaning up master after 3.36 is done so that we properly branch off
> master for each release, like other modules do.
>

Thanks for merging it!
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Link Dupont]

Thanks for the MR Rafael. I just merged it. Don't worry about opening
an MR against master right now. master is very outdated. The current
branching process is to branch off the previous gnome-3-xx version (so
for example, I branched off gnome-3-34 to create gnome-3-36). I plan on
cleaning up master after 3.36 is done so that we properly branch off
master for each release, like other modules do.

Link

On Sun, 2020-03-08 at 18:17 -0300, Rafael Fontenelle wrote:
> Em dom., 8 de mar. de 2020 às 08:17, Claude Paroz  > escreveu:
> > Le 08.03.20 à 11:57, Rafael Fontenelle a écrit :
> > > Claude, Link,
> > > 
> > > Em dom., 8 de mar. de 2020 às 07:21, Claude Paroz <
> > > cla...@2xlibre.net> escreveu:
> > > > Yes, that's the reason. D-L is not able to add a new
> > > > translation when
> > > > the language list is inside a file other than LINGUAS.
> > > > 
> > > > Link, would you be able to make the release-notes make process
> > > > use an
> > > > external LINGUAS file for the language list? Would be awesome!
> > > > 
> > > 
> > > I already provided a patch that enables LINGUAS support for
> > > Release
> > > Notes during discussion of Meson port [1], although it was more
> > > like a
> > > workaround. Applying this or any other solution would awesome
> > > indeed.
> > > 
> > > [1] 
> > > https://gitlab.gnome.org/Teams/Engagement/release-notes/-/merge_requests/8#note_309128
> > 
> > Thanks Rafael for refreshing my memory!
> > 
> > Unless Link disagrees, I would be for you to commit your small
> > workaround patch and see if it works for the various toolchains.
> > 
> > Claude
> > --
> > www.2xlibre.net
> 
> Filed a merge request with a patch that worked for me:
> https://gitlab.gnome.org/Teams/Engagement/release-notes/-/merge_requests/18
> 
> This is for gnome-3-36 branch. My intention is to propose the same to
> master branch afterwards.
> 
> Rafael Fontenelle

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Rafael Fontenelle]

Em dom., 8 de mar. de 2020 às 08:17, Claude Paroz  escreveu:
>
> Le 08.03.20 à 11:57, Rafael Fontenelle a écrit :
> > Claude, Link,
> >
> > Em dom., 8 de mar. de 2020 às 07:21, Claude Paroz  
> > escreveu:
> >>
> >> Yes, that's the reason. D-L is not able to add a new translation when
> >> the language list is inside a file other than LINGUAS.
> >>
> >> Link, would you be able to make the release-notes make process use an
> >> external LINGUAS file for the language list? Would be awesome!
> >>
> >
> > I already provided a patch that enables LINGUAS support for Release
> > Notes during discussion of Meson port [1], although it was more like a
> > workaround. Applying this or any other solution would awesome indeed.
> >
> > [1] 
> > https://gitlab.gnome.org/Teams/Engagement/release-notes/-/merge_requests/8#note_309128
>
> Thanks Rafael for refreshing my memory!
>
> Unless Link disagrees, I would be for you to commit your small
> workaround patch and see if it works for the various toolchains.
>
> Claude
> --
> www.2xlibre.net

Filed a merge request with a patch that worked for me:
https://gitlab.gnome.org/Teams/Engagement/release-notes/-/merge_requests/18

This is for gnome-3-36 branch. My intention is to propose the same to
master branch afterwards.

Rafael Fontenelle
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Hannie Dumoleyn]

Ok guys, all of you thanks for solving this for the Dutch team. Please 
let me know when it is fixed.

Cheers,
Hannie

Op 08-03-2020 om 12:08 schreef Claude Paroz:

Le 08.03.20 à 11:57, Rafael Fontenelle a écrit :

Claude, Link,

Em dom., 8 de mar. de 2020 às 07:21, Claude Paroz  escreveu:

Yes, that's the reason. D-L is not able to add a new translation when
the language list is inside a file other than LINGUAS.

Link, would you be able to make the release-notes make process use an
external LINGUAS file for the language list? Would be awesome!


I already provided a patch that enables LINGUAS support for Release
Notes during discussion of Meson port [1], although it was more like a
workaround. Applying this or any other solution would awesome indeed.

[1] 
https://gitlab.gnome.org/Teams/Engagement/release-notes/-/merge_requests/8#note_309128

Thanks Rafael for refreshing my memory!

Unless Link disagrees, I would be for you to commit your small
workaround patch and see if it works for the various toolchains.

Claude



___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Claude Paroz]

Le 08.03.20 à 11:57, Rafael Fontenelle a écrit :
> Claude, Link,
> 
> Em dom., 8 de mar. de 2020 às 07:21, Claude Paroz  
> escreveu:
>>
>> Yes, that's the reason. D-L is not able to add a new translation when
>> the language list is inside a file other than LINGUAS.
>>
>> Link, would you be able to make the release-notes make process use an
>> external LINGUAS file for the language list? Would be awesome!
>>
> 
> I already provided a patch that enables LINGUAS support for Release
> Notes during discussion of Meson port [1], although it was more like a
> workaround. Applying this or any other solution would awesome indeed.
> 
> [1] 
> https://gitlab.gnome.org/Teams/Engagement/release-notes/-/merge_requests/8#note_309128

Thanks Rafael for refreshing my memory!

Unless Link disagrees, I would be for you to commit your small
workaround patch and see if it works for the various toolchains.

Claude
-- 
www.2xlibre.net
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Rafael Fontenelle]

Claude, Link,

Em dom., 8 de mar. de 2020 às 07:21, Claude Paroz  escreveu:
>
> Le 07.03.20 à 23:38, Rafael Fontenelle a écrit :
> > Normally, after "Ready for submission" (Klaar voor committen) you
> > should see an "Submit to repository" (Naar repository inzenden)
> > action.
> >
> > In this particular case, my bet is that you need first to enable your
> > language in 
> > https://gitlab.gnome.org/Teams/Engagement/release-notes/-/blob/gnome-3-36/help/Makefile.am
> > -- I suggest that you create a merge request adding Netherland
> > translation also enabling that language in Makefile.am.
>
> Yes, that's the reason. D-L is not able to add a new translation when
> the language list is inside a file other than LINGUAS.
>
> Link, would you be able to make the release-notes make process use an
> external LINGUAS file for the language list? Would be awesome!
>

I already provided a patch that enables LINGUAS support for Release
Notes during discussion of Meson port [1], although it was more like a
workaround. Applying this or any other solution would awesome indeed.

[1] 
https://gitlab.gnome.org/Teams/Engagement/release-notes/-/merge_requests/8#note_309128

Best regards,
Rafael Fontenelle
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Claude Paroz]

Le 07.03.20 à 23:38, Rafael Fontenelle a écrit :
> Normally, after "Ready for submission" (Klaar voor committen) you
> should see an "Submit to repository" (Naar repository inzenden)
> action.
> 
> In this particular case, my bet is that you need first to enable your
> language in 
> https://gitlab.gnome.org/Teams/Engagement/release-notes/-/blob/gnome-3-36/help/Makefile.am
> -- I suggest that you create a merge request adding Netherland
> translation also enabling that language in Makefile.am.

Yes, that's the reason. D-L is not able to add a new translation when
the language list is inside a file other than LINGUAS.

Link, would you be able to make the release-notes make process use an
external LINGUAS file for the language list? Would be awesome!

Claude
-- 
www.2xlibre.net
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Rafael Fontenelle]

Hannie,

Em sáb., 7 de mar. de 2020 às 17:57, Hannie Dumoleyn
 escreveu:
>
> Forgive me for bothering you with this, but I still do not get it.
> Perhaps my commit experience has become a bit rusty ): Ok, I went
> through all the steps again.

Don't worry!

> 1. "Ready for submission" (Klaar voor committen) I chose the file on my
> PC (button Browse)
> 2. "Reserve to submit" (Reserveren voor inzenden).
> ??? Here I should get "Submit to repository", but instead I get "Inform
> of submission"
>
> What I do NOT get is "Submit to repository". I have committed another
> translation (gnome-control-center) where I do get this step, and here
> all goes well.

Normally, after "Ready for submission" (Klaar voor committen) you
should see an "Submit to repository" (Naar repository inzenden)
action.

In this particular case, my bet is that you need first to enable your
language in 
https://gitlab.gnome.org/Teams/Engagement/release-notes/-/blob/gnome-3-36/help/Makefile.am
-- I suggest that you create a merge request adding Netherland
translation also enabling that language in Makefile.am.

Regards,
Rafael Fontenelle
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Hannie Dumoleyn]

Forgive me for bothering you with this, but I still do not get it. 
Perhaps my commit experience has become a bit rusty ): Ok, I went 
through all the steps again.


1. "Ready for submission" (Klaar voor committen) I chose the file on my 
PC (button Browse)

2. "Reserve to submit" (Reserveren voor inzenden).
??? Here I should get "Submit to repository", but instead I get "Inform 
of submission"


What I do NOT get is "Submit to repository". I have committed another 
translation (gnome-control-center) where I do get this step, and here 
all goes well.


I suppose that this is why the status bar at the top is still red and I 
see 0% 0 (green) 0 (red), see

https://l10n.gnome.org/vertimus/release-notes/gnome-3-36/help/nl/

Hannie

Op 07-03-2020 om 18:00 schreef Rafael Fontenelle:

Hello Hannie,

Em sáb., 7 de mar. de 2020 às 13:40, Hannie Dumoleyn
 escreveu:

Hello Rafael,

I will go through the steps again so I can explain what is happening.

On [1] I reserved the module for proofreading again, then I uploaded the
fully translated file from my PC.
It now shows 155 (green) / 0 / 0, but there is a button "Help compiling"
which, when clicked, shows the message about 'Gresik', see [2]

Could you be more clear on what is the error message you are getting?

When I click on the [2] link, which I assume is the URL
https://l10n.gnome.org/HTML/574645/index.html, I see your translated
version of the Release Notes. This translated page is expected when
clicking the "Build help" button in a documentation module in Damned
Lies.


I do not know what this means, so I will not continue as yet. I am
afraid it will end up in the same red status bar at the top and a status
0% 0 0 115.

Please notice the stats bar is still all red with "0 0 115" (0%
translated) because you *did not* push the translation file to the
source code repository, you simply archived the actions (i.e. you
discarded all edits).

Regards,
Rafael Fontenelle



___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Rafael Fontenelle]

Hello Hannie,

Em sáb., 7 de mar. de 2020 às 13:40, Hannie Dumoleyn
 escreveu:
>
> Hello Rafael,
>
> I will go through the steps again so I can explain what is happening.
>
> On [1] I reserved the module for proofreading again, then I uploaded the
> fully translated file from my PC.
> It now shows 155 (green) / 0 / 0, but there is a button "Help compiling"
> which, when clicked, shows the message about 'Gresik', see [2]

Could you be more clear on what is the error message you are getting?

When I click on the [2] link, which I assume is the URL
https://l10n.gnome.org/HTML/574645/index.html, I see your translated
version of the Release Notes. This translated page is expected when
clicking the "Build help" button in a documentation module in Damned
Lies.

>
> I do not know what this means, so I will not continue as yet. I am
> afraid it will end up in the same red status bar at the top and a status
> 0% 0 0 115.

Please notice the stats bar is still all red with "0 0 115" (0%
translated) because you *did not* push the translation file to the
source code repository, you simply archived the actions (i.e. you
discarded all edits).

Regards,
Rafael Fontenelle
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Fwd: Re: Build error

[Hannie Dumoleyn]

Hello Andre,

I forgot to CC my answer to Rafael to this list. Why do I see this 
button "Help compiling" (Hulp bij compileren) next to the name of the 
uploaded file and why does it change to Hulpindex after I have clicked 
that button?


In a previous attempt where I clicked that Help button I remember having 
seen the message "Build error" and in that file the Dutch text after the 
link to gnome.asia was grey instead of black. That is why I translated 
the whole string again. For the rest, see my explanation to Rafael.


@ Rafael: I forgot to send you the link to 403 Forbidden when I try to 
open the last uploaded translation on [1]. Here it is:


https://l10n.gnome.org/media/upload-backup/release-notes-gnome-3-36-help-nl-961396_ZRWsmL9.po



 Doorgestuurd bericht 
Onderwerp:  Re: Build error
Datum:  Sat, 7 Mar 2020 17:15:44 +0100
Van:Hannie Dumoleyn 
Antwoord-naar:  lafeber-dumole...@zonnet.nl
Aan:Rafael Fontenelle 



Hello Rafael,

I will go through the steps again so I can explain what is happening.

On [1] I reserved the module for proofreading again, then I uploaded the 
fully translated file from my PC.
It now shows 155 (green) / 0 / 0, but there is a button "Help compiling" 
which, when clicked, shows the message about 'Gresik', see [2]


I do not know what this means, so I will not continue as yet. I am 
afraid it will end up in the same red status bar at the top and a status 
0% 0 0 115.


Regards,
Hannie

[1] https://l10n.gnome.org/vertimus/release-notes/gnome-3-36/help/nl/level1/

Op 07-03-2020 om 15:16 schreef Rafael Fontenelle:

Hello, Hannie

Em sáb., 7 de mar. de 2020 às 10:22, Hannie Dumoleyn
 escreveu:

Hello,

The Dutch translation of
https://l10n.gnome.org/vertimus/release-notes/gnome-3-36/help/nl/level1/
is not accepted.

What do you mean by "is not accepted"? Who or what did not accepted?

All I see in the history of actions is that the translation was not
sent to the repository using Damned Lies web interface. It was just
reserved for submission, informed submission and then the actions were
archived. Was it committed via Git command-line interface?

I think the link in the following string may be the

culprit:

[2] https://l10n.gnome.org/HTML/574645/index.html


#. (itstool) path: page/p
#: C/index.page:35
msgid ""
"3.36 has been named “Gresik” in recognition of the team behind href="
"\"https://2019.gnome.asia\;>GNOME.Asia 2019. GNOME.Asia is 
GNOME’s"
"official annual summit in Asia, which is only possible thanks to the 
hard"

"work of local volunteers. This year’s event was held in Gresik,
Indonesia, "
"and we’d like to thank everyone who contributed to its success. Thank
you, "
"Team Gresik!"
msgstr ""
"3.36 heeft de naam ‘Gresik’ gekregen als erkenning voor het team achter
https://2019.gnome.asia\;>GNOME.Asia 2019. GNOME.Asia is de"
"jaarlijkse officiële Gnome-bijeenkomst in Azië, die mogelijk gemaakt
wordt "
"dankzij het harde werk van de lokale vrijwilligers. Dit jaar vond het"
"evenement plaats in Gresik, Indonesië, en we willen graag iedereen die
aan "
"het succes ervan heeft bijgedragen bedanken. Bedankt, team Gresik!"

I made the mistake to commit the module anyway. Now, when I try to open
the last translation, I get the following message: 403 Forbidden (You
don't have permission to access this resource.)

I was not able to reproduce 403 forbidden. Can you be more specific on
the URL you are not being able to access?

Looks good to me:
https://l10n.gnome.org/vertimus/release-notes/gnome-3-36/help/nl/

Also looks good to me:
https://l10n.gnome.org/module/po/release-notes/gnome-3-36/help/nl.po


Can anyone help?

Hannie Dumoleyn
Gnome Dutch Translators


Regards,
Rafael Fontenelle



___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Build error

[Andre Klapper]

Hi,

On Sat, 2020-03-07 at 13:30 +0100, Hannie Dumoleyn wrote:
> The Dutch translation of
> https://l10n.gnome.org/vertimus/release-notes/gnome-3-36/help/nl/level1/
> is not accepted.

What is the error message, and where?

> I think the link in the following string may be the culprit:

Could you explain what makes you think so?

> #. (itstool) path: page/p
> #: C/index.page:35
> msgid ""
> "3.36 has been named “Gresik” in recognition of the team behind https://2019.gnome.asia\;>GNOME.Asia 2019. GNOME.Asia is GNOME’s "
> "official annual summit in Asia, which is only possible thanks to the hard "
> "work of local volunteers. This year’s event was held in Gresik,
> Indonesia, "
> "and we’d like to thank everyone who contributed to its success. Thank
> you, "
> "Team Gresik!"
> msgstr ""
> "3.36 heeft de naam ‘Gresik’ gekregen als erkenning voor het team achter 
>  " href="
> "\"https://2019.gnome.asia\;>GNOME.Asia 2019. GNOME.Asia is de "
> "jaarlijkse officiële Gnome-bijeenkomst in Azië, die mogelijk gemaakt wordt "
> "dankzij het harde werk van de lokale vrijwilligers. Dit jaar vond het "
> "evenement plaats in Gresik, Indonesië, en we willen graag iedereen die aan "
> "het succes ervan heeft bijgedragen bedanken. Bedankt, team Gresik!"
>
> I made the mistake to commit the module anyway. Now, when I try to open
> the last translation, I get the following message: 403 Forbidden (You
> don't have permission to access this resource.)
>
> Can anyone help?

The last action on
https://l10n.gnome.org/vertimus/release-notes/gnome-3-36/help/nl/level1/
is "Archive the actions".
I assume that removes the translation proposals, hence the 403 error.

Cheers,
andre
--
Andre Klapper  |  ak...@gmx.net
https://blogs.gnome.org/aklapper/


___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Build error

[Hannie Dumoleyn]

Hello,

The Dutch translation of 
https://l10n.gnome.org/vertimus/release-notes/gnome-3-36/help/nl/level1/
is not accepted. I think the link in the following string may be the 
culprit:


#. (itstool) path: page/p
#: C/index.page:35
msgid ""
"3.36 has been named “Gresik” in recognition of the team behind https://2019.gnome.asia\;>GNOME.Asia 2019. GNOME.Asia is GNOME’s "
"official annual summit in Asia, which is only possible thanks to the hard "
"work of local volunteers. This year’s event was held in Gresik, 
Indonesia, "
"and we’d like to thank everyone who contributed to its success. Thank 
you, "

"Team Gresik!"
msgstr ""
"3.36 heeft de naam ‘Gresik’ gekregen als erkenning voor het team achter 

" href="
"\"https://2019.gnome.asia\;>GNOME.Asia 2019. GNOME.Asia is de "
"jaarlijkse officiële Gnome-bijeenkomst in Azië, die mogelijk gemaakt 
wordt "

"dankzij het harde werk van de lokale vrijwilligers. Dit jaar vond het "
"evenement plaats in Gresik, Indonesië, en we willen graag iedereen die 
aan "

"het succes ervan heeft bijgedragen bedanken. Bedankt, team Gresik!"

I made the mistake to commit the module anyway. Now, when I try to open 
the last translation, I get the following message: 403 Forbidden (You 
don't have permission to access this resource.)


Can anyone help?

Hannie Dumoleyn
Gnome Dutch Translators

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Re: Translating tags [was: Re: Greek(el): build error gnome-devel-docs]

[Jiro Matsuzawa]

On Fri, May 3, 2013 at 4:40 PM, Daniel Mustieles García
daniel.mustie...@gmail.com wrote:
 There is a pending discussion about this here:
 https://mail.gnome.org/archives/gnome-i18n/2013-April/msg9.html

 Instead of using itstool, you can use gtxml to check errors in your
 documentation translations. I've not used itstool to check them, but maybe
 gtxml returns more user-friendly error messages.

It's good. Thank you!



 Cheers!

 2013/5/3 Jiro Matsuzawa jmatsuz...@gnome.org

 I think itstool is helpful. It reports some errors in translation.
 In the case of gnome-devel-docs:
 % itstool --strict -m el/el.mo -o el C/*.xml
 Error: Could not merge translations:
 'NoneType' object has no attribute 'node'

 Error messages may be obscure in some cases. But they let us know some
 errors exist in our translation. I make it a point to check my po with
 itstool before committing. It would be best if errors like this could
 be detected when po files are pushed...


 --
 Jiro Matsuzawa
 E-mail:
  jmatsuz...@gnome.org
  matsuzawa...@gmail.com
 GPG Key ID: 0xECC442E9
 GPG Key Fingerprint: E086 C14A 869F BB0E 3541 19EB E370 B08B ECC4 42E9
 ___
 gnome-i18n mailing list
 gnome-i18n@gnome.org
 https://mail.gnome.org/mailman/listinfo/gnome-i18n





--
Jiro Matsuzawa
E-mail:
 jmatsuz...@gnome.org
 matsuzawa...@gmail.com
GPG Key ID: 0xECC442E9
GPG Key Fingerprint: E086 C14A 869F BB0E 3541 19EB E370 B08B ECC4 42E9
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Re: Translating tags [was: Re: Greek(el): build error gnome-devel-docs]

[Daniel Mustieles García]

There is a pending discussion about this here:
https://mail.gnome.org/archives/gnome-i18n/2013-April/msg9.html

Instead of using itstool, you can use gtxml to check errors in your
documentation translations. I've not used itstool to check them, but maybe
gtxml returns more user-friendly error messages.

Cheers!

2013/5/3 Jiro Matsuzawa jmatsuz...@gnome.org

 I think itstool is helpful. It reports some errors in translation.
 In the case of gnome-devel-docs:
 % itstool --strict -m el/el.mo -o el C/*.xml
 Error: Could not merge translations:
 'NoneType' object has no attribute 'node'

 Error messages may be obscure in some cases. But they let us know some
 errors exist in our translation. I make it a point to check my po with
 itstool before committing. It would be best if errors like this could
 be detected when po files are pushed...


 --
 Jiro Matsuzawa
 E-mail:
  jmatsuz...@gnome.org
  matsuzawa...@gmail.com
 GPG Key ID: 0xECC442E9
 GPG Key Fingerprint: E086 C14A 869F BB0E 3541 19EB E370 B08B ECC4 42E9
 ___
 gnome-i18n mailing list
 gnome-i18n@gnome.org
 https://mail.gnome.org/mailman/listinfo/gnome-i18n

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Re: Translating tags [was: Re: Greek(el): build error gnome-devel-docs]

[Jiro Matsuzawa]

I think itstool is helpful. It reports some errors in translation.
In the case of gnome-devel-docs:
% itstool --strict -m el/el.mo -o el C/*.xml
Error: Could not merge translations:
'NoneType' object has no attribute 'node'

Error messages may be obscure in some cases. But they let us know some
errors exist in our translation. I make it a point to check my po with
itstool before committing. It would be best if errors like this could
be detected when po files are pushed...


--
Jiro Matsuzawa
E-mail:
 jmatsuz...@gnome.org
 matsuzawa...@gmail.com
GPG Key ID: 0xECC442E9
GPG Key Fingerprint: E086 C14A 869F BB0E 3541 19EB E370 B08B ECC4 42E9
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Greek(el): build error gnome-devel-docs

[Jiro Matsuzawa]

Hi Greek translators,

Building Greek gnome-devel-docs failed.
Would you please check it?
Here is a jhbuild log:
-
% jhbuild buildone -fc gnome-devel-docs
*** Checking out gnome-devel-docs *** [1/1]
git remote set-url origin git://git.gnome.org/gnome-devel-docs
(...snip...)
*** Building gnome-devel-docs *** [1/1]
(...snip...)
Making all in hig
make[1]: Entering directory `/opt/gnome/checkout/gnome-devel-docs/hig'
  GENde/de.mo
  GENde/
  GENel/el.mo
  GENel/
Error: Could not merge translations:
'NoneType' object has no attribute 'node'
make[1]: *** [el/el.stamp] Error 1
make[1]: Leaving directory `/opt/gnome/checkout/gnome-devel-docs/hig'
make: *** [all-recursive] Error 1
-

Thanks in advance for your help.

-- 
Jiro Matsuzawa
E-mail:
 jmatsuz...@gnome.org
 jmatsuz...@src.gnome.org
 matsuzawa...@gmail.com
GPG Key ID: 0xECC442E9
GPG Key Fingerprint: E086 C14A 869F BB0E 3541 19EB E370 B08B ECC4 42E9
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Re: Greek(el): build error gnome-devel-docs

[Jiro Matsuzawa]

I've debugged and fixed it. The patch has been already pushed [1].
If I have made any mistakes, please revert it.
[1] 
https://git.gnome.org/browse/gnome-devel-docs/commit/?id=d4881b6e0c165d99dd29eaae64d634f2b1db695b

diff --git a/hig/el/el.po b/hig/el/el.po
index a58e69c..e49dbc9 100644
--- a/hig/el/el.po
+++ b/hig/el/el.po
@@ -27568,7 +27568,7 @@ msgstr NY
 #: C/hig-ch-bibliography.xml:160(bibliomset/address)
 #: C/hig-ch-bibliography.xml:170(bibliomset/address)
 msgid _:city-1/, _:state-2/
-msgstr _:πόλη-1/, _:περιφέρεια-2/
+msgstr _:city-1/, _:state-2/

 #: C/hig-ch-bibliography.xml:12(bibliomset/publishername)
 msgid allworth press
@@ -27750,7 +27750,7 @@ msgstr Ηνωμένο Βασίλειο

 #: C/hig-ch-bibliography.xml:55(bibliomset/address)
 msgid _:city-1/, _:country-2/
-msgstr _:πόλη-1/, _:περιφέρεια-2/
+msgstr _:city-1/, _:country-2/

 #: C/hig-ch-bibliography.xml:56(bibliomset/publishername)
 msgid Thames amp; Hudson


On Mon, Mar 25, 2013 at 11:39 PM, Jiro Matsuzawa jmatsuz...@gnome.org wrote:
 Hi Greek translators,

 Building Greek gnome-devel-docs failed.
 Would you please check it?
 Here is a jhbuild log:
 -
 % jhbuild buildone -fc gnome-devel-docs
 *** Checking out gnome-devel-docs *** [1/1]
 git remote set-url origin git://git.gnome.org/gnome-devel-docs
 (...snip...)
 *** Building gnome-devel-docs *** [1/1]
 (...snip...)
 Making all in hig
 make[1]: Entering directory `/opt/gnome/checkout/gnome-devel-docs/hig'
   GENde/de.mo
   GENde/
   GENel/el.mo
   GENel/
 Error: Could not merge translations:
 'NoneType' object has no attribute 'node'
 make[1]: *** [el/el.stamp] Error 1
 make[1]: Leaving directory `/opt/gnome/checkout/gnome-devel-docs/hig'
 make: *** [all-recursive] Error 1
 -

 Thanks in advance for your help.

 --
 Jiro Matsuzawa
 E-mail:
  jmatsuz...@gnome.org
  jmatsuz...@src.gnome.org
  matsuzawa...@gmail.com
 GPG Key ID: 0xECC442E9
 GPG Key Fingerprint: E086 C14A 869F BB0E 3541 19EB E370 B08B ECC4 42E9



-- 
Jiro Matsuzawa
E-mail:
 jmatsuz...@gnome.org
 jmatsuz...@src.gnome.org
 matsuzawa...@gmail.com
GPG Key ID: 0xECC442E9
GPG Key Fingerprint: E086 C14A 869F BB0E 3541 19EB E370 B08B ECC4 42E9
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Translating tags [was: Re: Greek(el): build error gnome-devel-docs]

[Andre Klapper]

On Tue, 2013-03-26 at 02:32 +0900, Jiro Matsuzawa wrote:
  msgid _:city-1/, _:state-2/
 -msgstr _:πόλη-1/, _:περιφέρεια-2/ 

Anybody having ideas how can we avoid that translators translate tags?

andre
-- 
Andre Klapper  |  ak...@gmx.net
http://blogs.gnome.org/aklapper/

___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n

Fwd: Re: Translating tags [was: Re: Greek(el): build error gnome-devel-docs]

[Gabor Kelemen]

Wrong answer button, sorry. Also found the component to file the bug,
sysadmin/git: https://bugzilla.gnome.org/show_bug.cgi?id=696578

Even if gtxml currently lets this particular problem slip away, it
should work in general:

$ gtxml hig/el/el.po
$
$ grep -C2 city-1 hig/el/el.po
#: C/hig-ch-bibliography.xml:160(bibliomset/address)
#: C/hig-ch-bibliography.xml:170(bibliomset/address)
msgid _:city-1/, _:state-2/
msgstr _:πόλη-1/, _:περιφέρεια-2/

--

#: C/hig-ch-bibliography.xml:55(bibliomset/address)
msgid _:city-1/, _:country-2/
msgstr _:πόλη-1/, _:περιφέρεια-2/


Regards
Gabor Kelemen


 Eredeti üzenet 
Tárgy: Re: Translating tags [was: Re: Greek(el): build error
gnome-devel-docs]
Dátum: Mon, 25 Mar 2013 19:10:09 +0100
Feladó: Gabor Kelemen kelem...@gnome.hu
Címzett: Andre Klapper ak...@gmx.net

2013-03-25 18:35 keltezéssel, Andre Klapper írta:
 On Tue, 2013-03-26 at 02:32 +0900, Jiro Matsuzawa wrote:
  msgid _:city-1/, _:state-2/
 -msgstr _:πόλη-1/, _:περιφέρεια-2/ 
 
 Anybody having ideas how can we avoid that translators translate tags?
 

How about building gtxml checks into d-l and into git pre-commit hooks?
There is a bit of brainstorming about the former in
https://bugzilla.gnome.org/show_bug.cgi?id=667207

There is nothing about the latter AFAIK, but I'm willing to file a bug
if someone tells me the right component.

Regards
Gabor Kelemen









signature.asc
Description: OpenPGP digital signature
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n