From laurence.lefaucheur at biblibre.com Thu Aug 2 17:50:09 2012 From: laurence.lefaucheur at biblibre.com (Laurence Lefaucheur) Date: Thu, 2 Aug 2012 17:50:09 +0200 Subject: [Koha-docs] =?utf-8?q?=5BPATCH=5D_manual_3=2E8_french_translation?= =?utf-8?q?=2C_system_preferences?= Message-ID: <1343922609-2660-1-git-send-email-laurence.lefaucheur@biblibre.com> --- fr/manual.xml | 146 +++++++++++++++++++++------------------------------------ 1 files changed, 54 insertions(+), 92 deletions(-) diff --git a/fr/manual.xml b/fr/manual.xml index b0479ed..1a44858 100644 --- a/fr/manual.xml +++ b/fr/manual.xml @@ -1,4 +1,4 @@ -? + @@ -249,19 +249,19 @@
BasketConfirmations - Default: always ask for confirmation + Valeur par d?faut: toujours demander confirmation - Asks: When closing or reopening a basket, ___. + Demande: Pour fermer ou r?ouvrir un panier, ___. - Values: + Valeurs: - always ask for confirmation + toujours demander confirmation - do not ask for confirmation + ne pas demander confirmation @@ -269,9 +269,7 @@ - This preference adds the option to skip confirmations on - closing and reopening a basket. If you skip the confirmation, - you do not create a new basket group. + Cette pr?f?rence ajoute la possibilit? de ne pas avoir d'?tape de confirmation ? la fermeture et ? la r?ouverture d'un panier. Si vous d?sactivez l'?tape de confirmation, vous ne cr?ez pas un nouveau bordereau.
@@ -370,24 +368,23 @@
AllowPKIAuth - Default: no + Valeur par d?faut: aucun - Asks: Use ___ field for SSL client certificate - authentication + Demande: Utiliser ___ champ pour le certificat d'authentification client SSL - Values: + Valeurs: - no + aucun - the common name + le nom de famille - the email address + l'adresse email
@@ -1516,11 +1513,8 @@ - Unless you are going in and manually changing 773$w to - match your rigorously-defined bibliographic relationships, you - should set this preference to "Don't use" and instead set EasyAnalyticalRecords to - "Display" + A moins que vous ne poursuiviez et changiez manuellement le 773$w pour correspondre aux relations bibliographiques rigoureuses, vous devriez positionner cette pr?f?rence sur "Ne pas utiliser" et param?trer ? la place EasyAnalyticalRecords sur + "Afficher" Description : @@ -1672,45 +1666,35 @@ EasyAnalyticalRecords - Asks: ___ easy ways to create analytical record - relationships + Demande: ___ les fa?ons simples de cr?er des relations entre notices (notice analytique) + - Default: Don't Display + Valeur par d?faut: Ne pas afficher - Values: + Valeurs: - Display + Afficher - Don't Display + Ne pas afficher - If you decide to use this feature you'll want to make sure - that your UseControlNumber preference is - set to "Don't use" or else the "Show analytics" links in the - staff client and the OPAC will be broken. + Si vous d?cidez d'utiliser cette fonctionnalit? assurez vous que votre pr?f?rence UseControlNumber est positionn?e sur "Ne pas utiliser", sinon le lien "Afficher les notices analytiques" dans l'interface professionnelle et ? l'OPAC sera bris?. + Description: - An analytic entry in a catalog is one that describes a - part of a larger work that is also described in the catalog. - In bibliographic cataloging, analytic entries may be made for - chapters in books or special issues of articles in - periodicals. In archival cataloging, analytic entries may be - made for series or items within a collection. This feature in - Koha allows for an easy way of linking analytic entries to the - host records, and this system preference adds several new menu - options to the staff cataloging detail pages to allow that to - happen. + Une notice analytique dans le catalogue est une notice qui d?crit une partie d'un travail plus large ?galement d?crit dans le catalogue. Dans le catalogage bibliographique, les notices analytiques peuvent ?tre faites pour les chapitres de livres ou des articles de num?ros de p?riodiques. Dans le catalogage d'archive, les notices analytiques peuvent ?tre faites pour des s?ries de documents ? l'int?rieur d'une collection. Cette fonctionnalit? dans Koha fournit un moyen facile de lier des notices analytiques au document h?te, et cette pr?f?rence syst?me ajoute plusieurs options sur les pages de d?tail de catalogage de l'interface professionnelle permettant d'utiliser la fonctionnalit?. + @@ -2156,39 +2140,32 @@
AllowItemsOnHoldCheckout - Default: Don't allow + Valeur par d?faut: Ne pas permettre - Asks: ___ checkouts of items items reserved to someone else. - If allowed do not generate RESERVE_WAITING and RESERVED warning. - This allows self checkouts for those items. + Demande: ___ le pr?t d'exemplaires r?serv?s pour quelqu'un d'autre. Si c'est autoris? ne pas g?n?rer les alertes R?servation mise de c?t? RESERVE_WAITING et R?serv? RESERVED. Ceci autorise le pr?t libre service de ces exemplaires. + - Values: + Valeurs: - Allow + Permettre - Don't allow + Ne pas permettre - This system preference relates only to SIP based self - checkout, not Koha's web based self checkout. + Cette pr?f?rence syst?me fait r?f?rence uniquement au pr?t libre service par automate SIP, pas au pr?t libre service de Koha. Description: - When this preference is set to 'Allow' patrons will be - able to use your external self check machine to check out a - book to themselves even if it's on hold for someone else. If - you would like Koha to prevent people from checking out books - that are on hold for someone else set this preference to - "Don't allow." + Quand cette pr?f?rence est positionn?e sur 'Permettre' les adh?rents pourront utiliser l'automate de pr?t pour emprunter un document m?me s'il est r?serv? pour quelqu'un d'autre. Si vous voulez emp?cher les personnes d'emprunter des livres qui sont r?serv?s pour quelqu'un d'autre, positionnez cette pr?f?rence sur "Ne pas permettre".
@@ -3005,20 +2982,19 @@
AutoResumeSuspendedHolds - Default: Allow + Valeur par d?faut: Permettre - Asks: ___ suspended holds to be automatically resumed by a - set date. + Demande: ___ de r?activer automatiquement les r?servations suspendues en saisissant une date. - Values: + Valeurs: - Allow + Permettre - Don't allow + Ne pas permettre @@ -3026,12 +3002,8 @@ - If this preference is set to 'Allow' then all suspended - holds will be able to have a date at which they automatically - become unsuspended. If you have this preference set to 'Allow' - you will also need the Unsuspend Holds cron job - running. + Si cette pr?f?rence est positionn?e sur 'Permettre' alors toutes les r?servations suspendues pourront recevoir une date ? laquelle la suspension sera lev?e automatiquement. Si vous positionnez cette pr?f?rence sur 'Permettre' vous aurez aussi besoin d'ex?cuter le cron job Lever les suspensions de r?servation .
@@ -3143,21 +3115,20 @@
ExpireReservesMaxPickUpDelay - Default: Don't allow + Valeur par d?faut: Ne pas permettre - Asks: ___ holds to expire automatically if they have not - been picked by within the time period specified in Demande: ___ que les r?servations expirent automatiquement si elles n'ont pas ?t? mises de c?t? durant l'intervalle de temps sp?cifi? dans ReservesMaxPickUpDelay - Values: + Valeurs: - Allow + Permettre - Don't allow + Ne pas permettre @@ -3165,13 +3136,9 @@ - If set to 'allow' this will cancel holds that have been - waiting for longer than the number of days specified in the - Si c'est positionn? sur 'Permettre',ceci annulera les r?servations qui attendent depuis plus longtemps que le nombre de jours sp?cifi? dans la pr?f?rence syst?me ReservesMaxPickUpDelay - system preference. Holds will only be cancelled if the Expire Holds cron job is - runnning. + . Les r?servations seront annul?es uniquement si le cron job Cron job d'expiration des r?servations est mis en place.
@@ -3179,24 +3146,19 @@
ExpireReservesMaxPickUpDelayCharge - Default: 0 + Valeur par d?faut: 0 - Asks: If using Demande: Si ExpireReservesMaxPickUpDelay, - charge a borrower who allows his or her waiting hold to expire a - fee of ___ USD + est utilis?, imputer au lecteur qui a laiss? son d?lai de r?servation expirer une amende de ___ Description: - If you are expiring holds that have been waiting too - long you can use this preference to charge the patron for not - picking up their hold. If you don't charge patrons for items - that aren't picked up you can leave this set to the default - which is 0. Holds will only be cancelled and charged if the - Expire Holds cron job - is runnning. + Si vous voyez des r?servations expir?es depuis longtemps vous pouvez utiliser cette pr?f?rence pour mettre une amende aux adh?rents pour ne pas avoir retir? leurs r?servations. Si vous ne mettez pas d'amende aux adh?rents pour les documents non retir?s vous pouvez laisser la valeur par d?faut qui est 0. Les r?servations seront annul?es et l'amende imput?e uniquement si le script + Expiration des r?servatios + est mis en place.
-- 1.7.5.4 From nengard at gmail.com Thu Aug 2 19:53:25 2012 From: nengard at gmail.com (Nicole Engard) Date: Thu, 2 Aug 2012 13:53:25 -0400 Subject: [Koha-docs] [PATCH] manual 3.8 french translation, system preferences In-Reply-To: <1343922609-2660-1-git-send-email-laurence.lefaucheur@biblibre.com> References: <1343922609-2660-1-git-send-email-laurence.lefaucheur@biblibre.com> Message-ID: Patch pushed. Thanks! 2012/8/2 Laurence Lefaucheur : > --- > fr/manual.xml | 146 +++++++++++++++++++++------------------------------------ > 1 files changed, 54 insertions(+), 92 deletions(-) > > diff --git a/fr/manual.xml b/fr/manual.xml > index b0479ed..1a44858 100644 > --- a/fr/manual.xml > +++ b/fr/manual.xml > @@ -1,4 +1,4 @@ > -? > + > "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> > > @@ -249,19 +249,19 @@ >
> BasketConfirmations > > - Default: always ask for confirmation > + Valeur par d?faut: toujours demander confirmation > > - Asks: When closing or reopening a basket, ___. > + Demande: Pour fermer ou r?ouvrir un panier, ___. > > - Values: > + Valeurs: > > > > - always ask for confirmation > + toujours demander confirmation > > > > - do not ask for confirmation > + ne pas demander confirmation > > > > @@ -269,9 +269,7 @@ > > > > - This preference adds the option to skip confirmations on > - closing and reopening a basket. If you skip the confirmation, > - you do not create a new basket group. > + Cette pr?f?rence ajoute la possibilit? de ne pas avoir d'?tape de confirmation ? la fermeture et ? la r?ouverture d'un panier. Si vous d?sactivez l'?tape de confirmation, vous ne cr?ez pas un nouveau bordereau. > > >
> @@ -370,24 +368,23 @@ >
> AllowPKIAuth > > - Default: no > + Valeur par d?faut: aucun > > - Asks: Use ___ field for SSL client certificate > - authentication > + Demande: Utiliser ___ champ pour le certificat d'authentification client SSL > > - Values: > + Valeurs: > > > > - no > + aucun > > > > - the common name > + le nom de famille > > > > - the email address > + l'adresse email > > >
> @@ -1516,11 +1513,8 @@ > > > > - Unless you are going in and manually changing 773$w to > - match your rigorously-defined bibliographic relationships, you > - should set this preference to "Don't use" and instead set - linkend="EasyAnalyticalRecords">EasyAnalyticalRecords to > - "Display" > + A moins que vous ne poursuiviez et changiez manuellement le 773$w pour correspondre aux relations bibliographiques rigoureuses, vous devriez positionner cette pr?f?rence sur "Ne pas utiliser" et param?trer ? la place EasyAnalyticalRecords sur > + "Afficher" > > > Description : > @@ -1672,45 +1666,35 @@ > > EasyAnalyticalRecords > > - Asks: ___ easy ways to create analytical record > - relationships > + Demande: ___ les fa?ons simples de cr?er des relations entre notices (notice analytique) > + > > - Default: Don't Display > + Valeur par d?faut: Ne pas afficher > > - Values: > + Valeurs: > > > > - Display > + Afficher > > > > - Don't Display > + Ne pas afficher > > > > > - If you decide to use this feature you'll want to make sure > - that your - linkend="UseControlNumber">UseControlNumber preference is > - set to "Don't use" or else the "Show analytics" links in the > - staff client and the OPAC will be broken. > + Si vous d?cidez d'utiliser cette fonctionnalit? assurez vous que votre pr?f?rence + linkend="UseControlNumber">UseControlNumber est positionn?e sur "Ne pas utiliser", sinon le lien "Afficher les notices analytiques" dans l'interface professionnelle et ? l'OPAC sera bris?. > + > > > Description: > > > > - An analytic entry in a catalog is one that describes a > - part of a larger work that is also described in the catalog. > - In bibliographic cataloging, analytic entries may be made for > - chapters in books or special issues of articles in > - periodicals. In archival cataloging, analytic entries may be > - made for series or items within a collection. This feature in > - Koha allows for an easy way of linking analytic entries to the > - host records, and this system preference adds several new menu > - options to the staff cataloging detail pages to allow that to > - happen. > + Une notice analytique dans le catalogue est une notice qui d?crit une partie d'un travail plus large ?galement d?crit dans le catalogue. Dans le catalogage bibliographique, les notices analytiques peuvent ?tre faites pour les chapitres de livres ou des articles de num?ros de p?riodiques. Dans le catalogage d'archive, les notices analytiques peuvent ?tre faites pour des s?ries de documents ? l'int?rieur d'une collection. Cette fonctionnalit? dans Koha fournit un moyen facile de lier des notices analytiques au document h?te, et cette pr?f?rence syst?me ajoute plusieurs options sur les pages de d?tail de catalogage de l'interface professionnelle permettant d'utiliser la fonctionnalit?. > + > > > > @@ -2156,39 +2140,32 @@ >
> AllowItemsOnHoldCheckout > > - Default: Don't allow > + Valeur par d?faut: Ne pas permettre > > - Asks: ___ checkouts of items items reserved to someone else. > - If allowed do not generate RESERVE_WAITING and RESERVED warning. > - This allows self checkouts for those items. > + Demande: ___ le pr?t d'exemplaires r?serv?s pour quelqu'un d'autre. Si c'est autoris? ne pas g?n?rer les alertes R?servation mise de c?t? RESERVE_WAITING et R?serv? RESERVED. Ceci autorise le pr?t libre service de ces exemplaires. > + > > - Values: > + Valeurs: > > > > - Allow > + Permettre > > > > - Don't allow > + Ne pas permettre > > > > > - This system preference relates only to SIP based self > - checkout, not Koha's web based self checkout. > + Cette pr?f?rence syst?me fait r?f?rence uniquement au pr?t libre service par automate SIP, pas au pr?t libre service de Koha. > > > Description: > > > > - When this preference is set to 'Allow' patrons will be > - able to use your external self check machine to check out a > - book to themselves even if it's on hold for someone else. If > - you would like Koha to prevent people from checking out books > - that are on hold for someone else set this preference to > - "Don't allow." > + Quand cette pr?f?rence est positionn?e sur 'Permettre' les adh?rents pourront utiliser l'automate de pr?t pour emprunter un document m?me s'il est r?serv? pour quelqu'un d'autre. Si vous voulez emp?cher les personnes d'emprunter des livres qui sont r?serv?s pour quelqu'un d'autre, positionnez cette pr?f?rence sur "Ne pas permettre". > > >
> @@ -3005,20 +2982,19 @@ >
> AutoResumeSuspendedHolds > > - Default: Allow > + Valeur par d?faut: Permettre > > - Asks: ___ suspended holds to be automatically resumed by a > - set date. > + Demande: ___ de r?activer automatiquement les r?servations suspendues en saisissant une date. > > - Values: > + Valeurs: > > > > - Allow > + Permettre > > > > - Don't allow > + Ne pas permettre > > > > @@ -3026,12 +3002,8 @@ > > > > - If this preference is set to 'Allow' then all suspended > - holds will be able to have a date at which they automatically > - become unsuspended. If you have this preference set to 'Allow' > - you will also need the - linkend="unsuspendholdcron">Unsuspend Holds cron job > - running. > + Si cette pr?f?rence est positionn?e sur 'Permettre' alors toutes les r?servations suspendues pourront recevoir une date ? laquelle la suspension sera lev?e automatiquement. Si vous positionnez cette pr?f?rence sur 'Permettre' vous aurez aussi besoin d'ex?cuter le cron job + linkend="unsuspendholdcron">Lever les suspensions de r?servation . > > >
> @@ -3143,21 +3115,20 @@ >
> ExpireReservesMaxPickUpDelay > > - Default: Don't allow > + Valeur par d?faut: Ne pas permettre > > - Asks: ___ holds to expire automatically if they have not > - been picked by within the time period specified in + Demande: ___ que les r?servations expirent automatiquement si elles n'ont pas ?t? mises de c?t? durant l'intervalle de temps sp?cifi? dans linkend="ReservesMaxPickUpDelay">ReservesMaxPickUpDelay > > - Values: > + Valeurs: > > > > - Allow > + Permettre > > > > - Don't allow > + Ne pas permettre > > > > @@ -3165,13 +3136,9 @@ > > > > - If set to 'allow' this will cancel holds that have been > - waiting for longer than the number of days specified in the > - + Si c'est positionn? sur 'Permettre',ceci annulera les r?servations qui attendent depuis plus longtemps que le nombre de jours sp?cifi? dans la pr?f?rence syst?me linkend="ReservesMaxPickUpDelay">ReservesMaxPickUpDelay > - system preference. Holds will only be cancelled if the - linkend="expiredholdscron">Expire Holds cron job is > - runnning. > + . Les r?servations seront annul?es uniquement si le cron job Cron job d'expiration des r?servations est mis en place. > > >
> @@ -3179,24 +3146,19 @@ >
> ExpireReservesMaxPickUpDelayCharge > > - Default: 0 > + Valeur par d?faut: 0 > > - Asks: If using + Demande: Si linkend="ExpireReservesMaxPickUpDelay">ExpireReservesMaxPickUpDelay, > - charge a borrower who allows his or her waiting hold to expire a > - fee of ___ USD > + est utilis?, imputer au lecteur qui a laiss? son d?lai de r?servation expirer une amende de ___ > > Description: > > > > - If you are expiring holds that have been waiting too > - long you can use this preference to charge the patron for not > - picking up their hold. If you don't charge patrons for items > - that aren't picked up you can leave this set to the default > - which is 0. Holds will only be cancelled and charged if the > - Expire Holds cron job > - is runnning. > + Si vous voyez des r?servations expir?es depuis longtemps vous pouvez utiliser cette pr?f?rence pour mettre une amende aux adh?rents pour ne pas avoir retir? leurs r?servations. Si vous ne mettez pas d'amende aux adh?rents pour les documents non retir?s vous pouvez laisser la valeur par d?faut qui est 0. Les r?servations seront annul?es et l'amende imput?e uniquement si le script > + Expiration des r?servatios > + est mis en place. > > >
> -- > 1.7.5.4 > > _______________________________________________ > Koha-docs mailing list > Koha-docs at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-docs From laurence.lefaucheur at biblibre.com Fri Aug 3 17:31:16 2012 From: laurence.lefaucheur at biblibre.com (Laurence Lefaucheur) Date: Fri, 03 Aug 2012 17:31:16 +0200 Subject: [Koha-docs] [Koha-translate] Arabic manual 38 In-Reply-To: References: <028B1A54D03E7B4482CDCA4EC8F06BFD0221E0E8@Bodensee.bsz-bw.de> <50029665.1060403@tamil.fr> <5012B735.6010401@biblibre.com> Message-ID: <501BEEC4.5090903@biblibre.com> Hi, what you propose with xml2pot is great ! Thanks. I now have to solve the next step : when the english manual is updated, how can the po file be updated without being overwritten ? When I execute all commands after having updated manual.xml, translations in the po file are lost I'll look a it after my holidays... Regards, Laurence Le 29/07/2012 01:02, Bernardo Gonzalez Kriegel a ?crit : > Hi Karam, Laurence and all interested. > > While watching the Olympics, I was working in the process of translating > the manual, > following the procedure suggested by Karam. > > I did use the git version of the manual for Koha 3.8.x > (git clone git://git.koha-community.org/kohadocs.git > ; cd kohadocs; git branch > --track 3.8.x origin/manual3.8.x; git checkout 3.8.x) > and found the following: > > 1) Using itstool from repository (itstool 1.1.0, Min12/Ubuntu 11.0) on > english version of the manual, > (itstool -l es_ES -o manual.pot manual.xml 2> err.log), was able to > create manual.pot. > I found the same error messages as Laurence, and no editing (XMLEditor, > vi) could get rid of them. > > The offending words (for itstool) where '©', 'é', > 'è', '∞', '“', '‘', '—', ' ', > '£', '”' and '’'. > > 2) Most of them can be replaced. > In fact, I suggest (Nicole) to switch the encoding of the manual to > UTF-8 (current encoding="US-ASCII"). > Then, for consistency > eacute and egrave should be replaced by ? and ? (ej. Caf?, Babelth?que) > ldquo and rdquor by " > lsquo and rsquor by ' > nbsp could be deleted or replaced by space. (only five occurrences) > mdash appears only once in the GNU license, and they use "--" in that > position in their website. > (I coud send a patch for all these) > > There is no logic replacement for 'infin' (once) and 'pound' (twice), > they are valid symbols. > But 'infin' appears in an example URL, perhaps is a mistake. > And 'pound' appears in an example of costs, could be replaced by $ > > Anyway the 'pot' file is created with those symbols/words and can be > translated, but... > > 3) There is another tool, xml2pot (from package poxml), that generates > a MUCH MUCH MUCH better PO file. > itstool produces 3 lines for each string (msgctxt, msgid and msgstr), > and produces an irrelevant entry for each image (827 lines) > > xml2pot produces a cleaner POT file, and without warnings/errors > (usage: xml2pot manual.xml > manual.pot) > > There is a tool for the reverse task, po2xml (same package), but do not > recommend using it (because it mangles the output file) > > 4) Then I suggest a change in the procedure: > > Fix manual.xml, at least the encoding > xml2pot manual.xml > manual.pot > msginit -i manual.pot -o manual.po --locale=xx_YY --no-translator > do some translation on manual.po > msgfmt -o manual.mo manual.po > itstool -m manual.mo -o manual.xx.xml manual.xml (this gives warnigs if > manual.xml is not fixed) > > Then open and read your (partially) translated manual. > > I hope that you could try this steps and comment your results. > > Regards > > Bernardo > -- > Bernardo Gonzalez Kriegel > bgkriegel at gmail.com > > > > On Fri, Jul 27, 2012 at 3:56 PM, Karam Qubsi > wrote: > > Hi Laurence , > I don't know what is the problem exactly , but I solve this problem > by open the manual.xml via (XMLEditor > ) and add (space) and delete it > (then save it ) and try again and it will work :) > > maybe this is about the (UTF-8) encoding > > > > On Fri, Jul 27, 2012 at 6:43 PM, Laurence Lefaucheur > > wrote: > > Hi, > > In installed itstool-1.2.0, and when I run : > > itstool -o manual.pot manual.xml > > I have many errors like : > > manual.xml:40231: parser error : Entity 'lsquo' not defined > ‘show c' should show the appropriate > parts of the > > Did you have the same ? > How can I solve the problem ? > > Thanks, > > Laurence > > -- ------------------------ Laurence Lefaucheur BibLibre solutions libres pour les biblioth?ques http://www.biblibre.com laurence.lefaucheur at biblibre.com p. 06 27 85 46 49 From bgkriegel at gmail.com Fri Aug 3 21:19:32 2012 From: bgkriegel at gmail.com (Bernardo Gonzalez Kriegel) Date: Fri, 3 Aug 2012 16:19:32 -0300 Subject: [Koha-docs] [Koha-translate] Arabic manual 38 In-Reply-To: <501BEEC4.5090903@biblibre.com> References: <028B1A54D03E7B4482CDCA4EC8F06BFD0221E0E8@Bodensee.bsz-bw.de> <50029665.1060403@tamil.fr> <5012B735.6010401@biblibre.com> <501BEEC4.5090903@biblibre.com> Message-ID: Hi Laurence, On Fri, Aug 3, 2012 at 12:31 PM, Laurence Lefaucheur < laurence.lefaucheur at biblibre.com> wrote: > Hi, > > what you propose with xml2pot is great ! Thanks. > > I now have to solve the next step : > when the english manual is updated, how can the po file be updated without > being overwritten ? > When I execute all commands after having updated manual.xml, translations > in the po file are lost > > To update the po file you can try the following (equivalent to what previously said Karam): Update the original file (ej. git pull) xml2pot manual.xml > manual.up,pot (create updated pot) msginit -i manual.up.pot -o manual.up.po --no-wrap --no-translator (create updated po) msgmerge -U manual.po manual.up.po (update strings, preserve translations) rm *.up* > I'll look a it after my holidays... > > Happy holidays! Bernardo > Regards, > > Laurence > > > Le 29/07/2012 01:02, Bernardo Gonzalez Kriegel a ?crit : > >> Hi Karam, Laurence and all interested. >> >> While watching the Olympics, I was working in the process of translating >> the manual, >> following the procedure suggested by Karam. >> >> I did use the git version of the manual for Koha 3.8.x >> (git clone git://git.koha-community.org/**kohadocs.git >> >; >> cd kohadocs; git branch >> >> --track 3.8.x origin/manual3.8.x; git checkout 3.8.x) >> and found the following: >> >> 1) Using itstool from repository (itstool 1.1.0, Min12/Ubuntu 11.0) on >> english version of the manual, >> (itstool -l es_ES -o manual.pot manual.xml 2> err.log), was able to >> create manual.pot. >> I found the same error messages as Laurence, and no editing (XMLEditor, >> vi) could get rid of them. >> >> The offending words (for itstool) where '©', 'é', >> 'è', '∞', '“', '‘', '—', ' ', >> '£', '”' and '’'. >> >> 2) Most of them can be replaced. >> In fact, I suggest (Nicole) to switch the encoding of the manual to >> UTF-8 (current encoding="US-ASCII"). >> Then, for consistency >> eacute and egrave should be replaced by ? and ? (ej. Caf?, Babelth?que) >> ldquo and rdquor by " >> lsquo and rsquor by ' >> nbsp could be deleted or replaced by space. (only five occurrences) >> mdash appears only once in the GNU license, and they use "--" in that >> position in their website. >> (I coud send a patch for all these) >> >> There is no logic replacement for 'infin' (once) and 'pound' (twice), >> they are valid symbols. >> But 'infin' appears in an example URL, perhaps is a mistake. >> And 'pound' appears in an example of costs, could be replaced by $ >> >> Anyway the 'pot' file is created with those symbols/words and can be >> translated, but... >> >> 3) There is another tool, xml2pot (from package poxml), that generates >> a MUCH MUCH MUCH better PO file. >> itstool produces 3 lines for each string (msgctxt, msgid and msgstr), >> and produces an irrelevant entry for each image (827 lines) >> >> xml2pot produces a cleaner POT file, and without warnings/errors >> (usage: xml2pot manual.xml > manual.pot) >> >> There is a tool for the reverse task, po2xml (same package), but do not >> recommend using it (because it mangles the output file) >> >> 4) Then I suggest a change in the procedure: >> >> Fix manual.xml, at least the encoding >> xml2pot manual.xml > manual.pot >> msginit -i manual.pot -o manual.po --locale=xx_YY --no-translator >> do some translation on manual.po >> msgfmt -o manual.mo manual.po >> itstool -m manual.mo -o manual.xx.xml manual.xml (this gives warnigs if >> manual.xml is not fixed) >> >> Then open and read your (partially) translated manual. >> >> I hope that you could try this steps and comment your results. >> >> Regards >> >> Bernardo >> -- >> Bernardo Gonzalez Kriegel >> bgkriegel at gmail.com >> >> >> >> >> On Fri, Jul 27, 2012 at 3:56 PM, Karam Qubsi > > wrote: >> >> Hi Laurence , >> I don't know what is the problem exactly , but I solve this problem >> by open the manual.xml via (XMLEditor >> > >> ) and add (space) and delete it >> >> (then save it ) and try again and it will work :) >> >> maybe this is about the (UTF-8) encoding >> >> >> >> On Fri, Jul 27, 2012 at 6:43 PM, Laurence Lefaucheur >> >> >> >> wrote: >> >> Hi, >> >> In installed itstool-1.2.0, and when I run : >> >> itstool -o manual.pot manual.xml >> >> I have many errors like : >> >> manual.xml:40231: parser error : Entity 'lsquo' not defined >> ‘show c' should show the appropriate >> parts of the >> >> Did you have the same ? >> How can I solve the problem ? >> >> Thanks, >> >> Laurence >> >> >> > > -- > ------------------------ > Laurence Lefaucheur > BibLibre > solutions libres pour les biblioth?ques > http://www.biblibre.com > laurence.lefaucheur at biblibre.**com > p. 06 27 85 46 49 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bgkriegel at gmail.com Tue Aug 28 19:03:43 2012 From: bgkriegel at gmail.com (Bernardo Gonzalez Kriegel) Date: Tue, 28 Aug 2012 14:03:43 -0300 Subject: [Koha-docs] Translation of manual using pootle Message-ID: Hi all, August is ending, so I guess it's time to revisit the issue of the translation of the manual. Some of us prefer to use the same infrastructure in translate.k-c. To that end we need a procedure to generate and update PO files from the XML version, translate, and finally produce a translated XML file (and then HTML, PDF, etc.). There are tools to do this: xml2pot: to create a POT file from XML gettext package to manipulate POT/PO/MO files itstool: to recreate XML from MO Now, one of this tools (itstool) complains that the current version of the manual (git, 3.8.x) is not a valid XML file. The problem seems to be due to the use of ISO (HTML) named character entities, such as ©   &ldquo, which are invalid in a XML document. One solution is to replace these entities by their UTF-8 counterparts (i.e. author in UTF-8), or by numeric character entities (© -> ©) So, to begin we need that the English version of the manual changes accordingly. (I could send a patch to this) Sincerely Bernardo -- Bernardo Gonzalez Kriegel bgkriegel at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From nengard at gmail.com Tue Aug 28 20:31:53 2012 From: nengard at gmail.com (Nicole Engard) Date: Tue, 28 Aug 2012 14:31:53 -0400 Subject: [Koha-docs] Translation of manual using pootle In-Reply-To: References: Message-ID: Bernardo, There were issues way back when we started with changing the encoding. The editor I'm using is entering those codes and if you change them once I open the editor again it will put them back in. So what needs to be done, is not necessarily a patch to the English version, but a check on the script that's generating the HTML to see if those codes can be removed and still display the manual properly. If they can then I can alter the encoding on the application and it should update those symbols .. if it doesn't then yes, we have to do it manually with a patch. I have to admit that I don't remember what the problem was, just that we went back and forth and eventually found a method that worked and I don't want to go and change the manual coding to find that we're back at square one with things not appearing properly on the web. Nicole On Tue, Aug 28, 2012 at 1:03 PM, Bernardo Gonzalez Kriegel wrote: > Hi all, > August is ending, so I guess it's time to revisit the issue of the > translation of the manual. > Some of us prefer to use the same infrastructure in translate.k-c. > > To that end we need a procedure to generate and update PO files from the XML > version, > translate, and finally produce a translated XML file (and then HTML, PDF, > etc.). > > There are tools to do this: > xml2pot: to create a POT file from XML > gettext package to manipulate POT/PO/MO files > itstool: to recreate XML from MO > > Now, one of this tools (itstool) complains that the current version of the > manual (git, 3.8.x) > is not a valid XML file. > > The problem seems to be due to the use of ISO (HTML) named character > entities, > such as ©   &ldquo, which are invalid in a XML document. > > One solution is to replace these entities by their UTF-8 counterparts (i.e. > author in UTF-8), or > by numeric character entities (© -> ©) > > So, to begin we need that the English version of the manual changes > accordingly. > (I could send a patch to this) > > Sincerely > Bernardo > > -- > Bernardo Gonzalez Kriegel > bgkriegel at gmail.com > From nengard at gmail.com Tue Aug 28 23:13:16 2012 From: nengard at gmail.com (Nicole Engard) Date: Tue, 28 Aug 2012 17:13:16 -0400 Subject: [Koha-docs] Translation of manual using pootle In-Reply-To: <33775AA9-10BD-4571-BB93-61811ECE3EC2@kohaaloha.com> References: <33775AA9-10BD-4571-BB93-61811ECE3EC2@kohaaloha.com> Message-ID: On Tue, Aug 28, 2012 at 4:08 PM, Mason James wrote: > whats the editor? > > can we use a better editor? The editor is http://www.xmlmind.com/xmleditor/ -- it's the one we ended up picking in the beginning after a lot of testing. Criteria - it has to work on Mac (and other OSes for others), it has to be a visual editor, and frankly since I do most of the writing, I have to like it :) hehe Like I said, I don't remember the problems with the encoding and the HTML conversion - it might all be irrelevant now, I'm willing to try whatever - but I do have the encoding set to UTF-8 (according to Chris) so I'm a bit clueless as to why those ASCII codes are showing. Nicole From mtj at kohaaloha.com Tue Aug 28 22:08:40 2012 From: mtj at kohaaloha.com (Mason James) Date: Wed, 29 Aug 2012 08:08:40 +1200 Subject: [Koha-docs] Translation of manual using pootle In-Reply-To: References: Message-ID: <33775AA9-10BD-4571-BB93-61811ECE3EC2@kohaaloha.com> On 2012-08-29, at 6:31 AM, Nicole Engard wrote: > Bernardo, > > There were issues way back when we started with changing the encoding. > The editor I'm using is entering those codes and if you change them > once I open the editor again it will put them back in. whats the editor? can we use a better editor? > So what needs > to be done, is not necessarily a patch to the English version, but a > check on the script that's generating the HTML to see if those codes > can be removed and still display the manual properly. If they can > then I can alter the encoding on the application and it should update > those symbols .. if it doesn't then yes, we have to do it manually > with a patch. > > I have to admit that I don't remember what the problem was, just that > we went back and forth and eventually found a method that worked and I > don't want to go and change the manual coding to find that we're back > at square one with things not appearing properly on the web. > > Nicole From gmcharlt at gmail.com Tue Aug 28 23:34:31 2012 From: gmcharlt at gmail.com (Galen Charlton) Date: Tue, 28 Aug 2012 17:34:31 -0400 Subject: [Koha-docs] Translation of manual using pootle In-Reply-To: References: Message-ID: Hi, On Tue, Aug 28, 2012 at 1:03 PM, Bernardo Gonzalez Kriegel wrote: > Now, one of this tools (itstool) complains that the current version of the > manual (git, 3.8.x) > is not a valid XML file. > > The problem seems to be due to the use of ISO (HTML) named character > entities, > such as ©   &ldquo, which are invalid in a XML document. I'm not sure whether to call it a bug or not, but the problem actually lies in itstool, not the document. Specifically, itstool currently has no way to load external DTDs. It uses the libxml2 Python module, so compare running xmllint --noout manual.xml vs. xmllint --noout --loaddtd manual.xml to see another example of an libxml2-based tool applied to the manual. As you can see, it works only if external DTDs are loaded. I've put up a _very_ quick-and-dirty patch to itstool in the load-dtds-quick-and-dirty branch at https://gitorious.org/~gmcharlt/itstool/gmcharlts-itstool, and I'll work on submitting a better patch to the maintainer of itstool. Regards, Galen -- Galen Charlton gmcharlt at gmail.com From bgkriegel at gmail.com Wed Aug 29 00:42:26 2012 From: bgkriegel at gmail.com (Bernardo Gonzalez Kriegel) Date: Tue, 28 Aug 2012 19:42:26 -0300 Subject: [Koha-docs] Translation of manual using pootle In-Reply-To: References: Message-ID: Galen, > I'm not sure whether to call it a bug or not, but the problem actually > lies in itstool, not the document. Specifically, itstool currently > has no way to load external DTDs. It uses the libxml2 Python module, > so compare running > > xmllint --noout manual.xml > > vs. > > xmllint --noout --loaddtd manual.xml > > to see another example of an libxml2-based tool applied to the manual. > As you can see, it works only if external DTDs are loaded. > > I've put up a _very_ quick-and-dirty patch to itstool in the > load-dtds-quick-and-dirty branch at > https://gitorious.org/~gmcharlt/itstool/gmcharlts-itstool, and I'll > work on submitting a better patch to the maintainer of itstool. > > you are right. In fact, an earlier version of itstool (1.1.0) complains, but not abort (and does its job), from 1.1.1 onward exit with error. My thought was to adapt the manual so we can work with the current version. Yours is a better solution, but we must wait for an updated version, or maybe not because it only has to work on the server that generates the XML from PO files, and the server can run a patched version, but I do not know if server administrators support this type of solution. Regards, Bernardo -------------- next part -------------- An HTML attachment was scrubbed... URL: From gmcharlt at gmail.com Wed Aug 29 15:28:57 2012 From: gmcharlt at gmail.com (Galen Charlton) Date: Wed, 29 Aug 2012 09:28:57 -0400 Subject: [Koha-docs] Translation of manual using pootle In-Reply-To: References: Message-ID: Hi, On Tue, Aug 28, 2012 at 6:42 PM, Bernardo Gonzalez Kriegel wrote: > My thought was to adapt the manual so we can work with the current version. > Yours is a better solution, but we must wait for an updated version, or > maybe > not because it only has to work on the server that generates the XML from PO > files, > and the server can run a patched version, but I do not know if server > administrators > support this type of solution. Depends on who the administrator is. :) For what it's worth, that kind of small change is one that I'd personally have no problem supporting. Regards, Galen -- Galen Charlton gmcharlt at gmail.com From gmcharlt at gmail.com Wed Aug 29 16:30:57 2012 From: gmcharlt at gmail.com (Galen Charlton) Date: Wed, 29 Aug 2012 10:30:57 -0400 Subject: [Koha-docs] Translation of manual using pootle In-Reply-To: References: Message-ID: Hi, On Tue, Aug 28, 2012 at 5:34 PM, Galen Charlton wrote: > I've put up a _very_ quick-and-dirty patch to itstool in the > load-dtds-quick-and-dirty branch at > https://gitorious.org/~gmcharlt/itstool/gmcharlts-itstool, and I'll > work on submitting a better patch to the maintainer of itstool. The better version of my patch is now available in the load-dtd branch and I've submitted a merge request to the maintainer. Regards, Galen -- Galen Charlton gmcharlt at gmail.com From bgkriegel at gmail.com Thu Aug 30 13:45:53 2012 From: bgkriegel at gmail.com (Bernardo Gonzalez Kriegel) Date: Thu, 30 Aug 2012 08:45:53 -0300 Subject: [Koha-docs] Translation of manual using pootle In-Reply-To: References: Message-ID: On Wed, Aug 29, 2012 at 11:30 AM, Galen Charlton wrote: > The better version of my patch is now available in the load-dtd branch > and I've submitted a merge request to the maintainer. > > Well, with a fixed itstool, then I would like suggest following procedure Prerequisites: working copy of kohadocs.git with 3.8.x branch, translate-toolkit and Galen's fixed "itstools" (Galen points that itstool do a better job to create PO files, expanding character entities) 1) To create initial PO file (I use some variables as example) DOCGITDIR=(where kohadocs.git lives, 3.8.x branch) DSTDIR=(pootle, etc., where translation takes place) LANG="xx" LOCALE="xx_YY" VER="38" cd $DOCGITDIR/en/ itstool -d --lang=$LANG -o /tmp/$LANG-$VER-manual.pot manual.xml msginit -i /tmp/$LANG-$VER-manual.pot -o $DSTDIR/$LANG-$VER-manual.po --locale=$LOCALE --no-translator rm /tmp/$LANG-$VER-manual.pot Next do some translation on PO file. 2) To update PO files from updated manual (same variables, updated repository) cd $DOCGITDIR/en/ itstool -d --lang=$LANG -o /tmp/$LANG-$VER-manual.pot manual.xml msginit -i /tmp/$LANG-$VER-manual.pot -o /tmp/$LANG-$VER-manual.po --locale=$LOCALE --no-translator msgmerge -U $DSTDIR/$LANG-$VER-manual.po /tmp/$LANG-$VER-manual.po rm /tmp/$LANG-$VER-manual.po* 3) To create translated version of the manual (same variables, updated repository) cd $DOCGITDIR/ msgfmt -o /tmp/$LANG-$VER-manual.mo $DSTDIR/$LANG-$VER-manual.po itstool -d --lang=$LANG -m /tmp/$LANG-$VER-manual.mo -o $LANG/manual.xml en/manual.xml rm /tmp/$LANG-$VERSION-manual.mo And eventually commit... All this should be done on the translation server, (1) once, (2) periodically or when Nicole commits, (3) periodically or with a new release... but Fr?d?ric want someone else to try if the procedure works. So, if someone wants to try ... Regards, Bernardo -- Bernardo Gonzalez Kriegel bgkriegel at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: