From y Mon Jul 9 17:22:14 2012 From: y (y) Date: Mon, 9 Jul 2012 17:22:14 +0200 Subject: [Koha-docs] =?y?q?=5BPATCH=201/2=5D=20French=20translation=20update=20=28miscellaneous=29?= In-Reply-To: References: Message-ID: <1341847334-30873-1-git-send-email-y> From: Laurence Lefaucheur --- fr/manual.xml | 1181 ++++++++++++++++++++++++++++++++++++++++++++++++--------- 1 files changed, 1002 insertions(+), 179 deletions(-) diff --git a/fr/manual.xml b/fr/manual.xml index 231c427..0baf4ca 100644 --- a/fr/manual.xml +++ b/fr/manual.xml @@ -2,10 +2,10 @@ - + Manuel Koha 3.8 (fr) - + Nicole C. Engard @@ -63,14 +63,26 @@ Traduction fran??aise - + + Fran??ois + + Charbonnier + + + BibLibre + + + Traduction fran??aise + + + 2012 - Nicole C. Engard/ByWater Solutions / BibLibre/Laurence - Lefaucheur + Nicole C. Engard/ByWater Solutions / Laurence + Lefaucheur/BibLibre - + Ce manuel est publi?? sous licence GNU General Public License, version 3 ou ult??rieure @@ -79,7 +91,7 @@ Appendix - 2011 + 2012 @@ -202,26 +214,26 @@ -
+
AcqViewBaskets - Default: created by staff member + Valeur par d??faut: cr????s par le biblioth??caire - Asks: Show baskets ___ + Demande: Afficher les paniers ___ - Values: + Valeurs: - created by staff member + cr????s par le biblioth??caire - from staff member's branch + de la biblioth??que - in system, regardless of owner + du syst??me, peu importe le propri??taire @@ -229,17 +241,7 @@ - When in acquisitions this preference allows you to - control whose baskets you can see when looking at a vendor. - The default value of 'created by staff member' makes it so - that you only see the baskets you created. Choosing to see - baskets 'from staff member's branch' will show you the baskets - created by anyone at the branch you're logged in at. Finally, - you can choose to set this preference to show you all baskets - regardless of who created it ('in system, regardless of - owner). Regardless of which value you choose for this - preference, superlibrarians can see all baskets created in the - system. + Quand vous ??tes dans les acquisitions cette pr??f??rence vous permet de contr??ler quels sont les paniers que vous pouvez voir pour un fournisseur. La valeur par d??faut est 'cr????s par le biblioth??caire', ce qui fait que vous ne voyez que les paniers que vous avez cr????s. Choisir de voir les paniers 'de la biblioth??que' vous permet de voir les paniers cr????s par n'importe qui dans la biblioth??que ?? laquelle vous ??tes connect??. Enfin, vous pouvez choisir de positionner cette pr??f??rence pour afficher tous les paniers, ind??pendamment de qui les a cr????s ('du syst??me, peu importe le propri??taire'). Quelle que soit la valeur choisie pour cette pr??f??rence, les superlibrarians peuvent voir tous les paniers cr????s dans le syst??me.
@@ -318,6 +320,25 @@
+
+ UniqueItemFields + + Valeur par d??faut: barcode + + Demande:___ (liste de champs uniques pour les exemplaires, s??par??s par des espaces ; doivent ??tre des champs valides de la table SQL items + ) + + Description: + + + + Si cette pr??f??rence est laiss??e vide, ?? l'ajout d'exemplaires dans les acquisitions il n'y aura pas de v??rification d'unicit??. Ceci signifie qu'un doublon de code barre peut ??tre cr???? dans les acquisitions, ce qui provoquera des erreurs ult??rieurement lors des pr??ts et retours d'exemplaires. + + +
+ +
Impression @@ -791,7 +812,53 @@ Situ?? sous : Accueil > Administration > Pr??f??rences syst??me > Autorit??s -
+
+ General + +
+ AutoCreateAuthorities + + Default: do not generate + + Asks: When editing records, ___ authority records that are + missing. + + Values: + + + + do not generate + + + + generate + + + + + BiblioAddsAuthorities + must be set to "allow" for this to have any effect + + + Description: + + + + When this and BiblioAddsAuthorities + are both turned on, automatically create authority records for + headings that don't have any authority link when cataloging. + When BiblioAddsAuthorities is on and AutoCreateAuthorities is + turned off, do not automatically generate authority records, + but allow the user to enter headings that don't match an + existing authority. When BiblioAddsAuthorities is off, this + has no effect. + + +
+ +
BiblioAddsAuthorities Valeur par d??faut : cr??er @@ -830,7 +897,7 @@
-
+
dontmerge Valeur par d??faut : Ne pas mettre ?? jour automatiquement @@ -857,7 +924,7 @@
-
+
MARCAuthorityControlField008 Valeur par d??faut : || aca||aabn | a|a d @@ -881,7 +948,7 @@
-
+
UseAuthoritiesForTracings Valeur par d??faut : Ne pas utiliser @@ -934,6 +1001,214 @@
+
+ Linker + + Cette pr??f??rence contr??le comment Koha lie les notices bibliographiques aux notices autorit??s. Toutes les notices bibliographiques ajout??es ?? Koha une fois cette pr??f??rence param??tr??e seront li??es automatiquement aux notices autorit??s ; pour les notices ajout??es avant que la pr??f??rence soit param??tr??e, un script (misc/link_bibs_to_authorities.pl) peut ??tre ex??cut?? par votre administrateur syst??me pour activer les liens. + + + +
+ LinkerKeepStale + + Default: Do not + + Asks: ___ keep existing links to authority records for + headings where the linker is unable to find a match. + + Values: + + + + Do + + + + Do not + + + + Description: + + + + When set to 'Do', the linker will never remove a link to + an authority record, though, depending on the value of LinkerRelink, it may change the + link. + + +
+ +
+ LinkerModule + + Default: Default + + Asks: Use the ___ linker module for matching headings to + authority records. + + Values: + + + + Default + + + + Retains Koha's previous behavior of only creating + links when there is an exact match to one and only one + authority record; if the LinkerOptions preference is + set to 'broader_headings', it will try to link headings to + authority records for broader headings by removing + subfields from the end of the heading + + + + + + First match + + + + Creates a link to the first authority record that + matches a given heading, even if there is more than one + authority record that matches + + + + + + Last match + + + + Creates a link to the last authority record that + matches a given heading, even if there is more than one + record that matches + + + + + + Description: + + + + This preference tells Koha which match to use when + searching for authority matches when saving a record. + + +
+ +
+ LinkerOptions + + Asks: Set the following options for the authority linker + ___ + + Description: + + + + This is a pipe separated (|) list of options. At the + moment, the only option available is "broader_headings." With + this option set to "broader_headings", the linker will try to + match the following heading as follows: + + =600 10$aCamins-Esakov, Jared$xCoin + collections$vCatalogs$vEarly works to 1800. + + First: Camins-Esakov, Jared--Coin + collections--Catalogs--Early works to 1800 + + Next: Camins-Esakov, Jared--Coin + collections--Catalogs + + Next: Camins-Esakov, Jared--Coin collections + + Next: Camins-Esakov, Jared (matches! if a previous + attempt had matched, it would not have tried this) + + +
+ + +
+
+
Catalogage @@ -1371,7 +1646,7 @@
-
+
Linda @@ -2178,12 +2453,12 @@ Exemple : Dans votre biblioth??que la limite d??finie pour - les amendes est de 5 € (c'est ?? dire qu'un adh??rent ayant accumul?? + les amendes est de 5 € (c'est ?? dire qu'un adh??rent ayant accumul?? 5 euros d'amendes n'est plus autoris?? ?? emrunter de documents). Un adh??rent ayant d??j?? 4 euros d'amendes impay??es sur son compte se pr??sente ?? la banque de pr??t avec 5 documents (4 livres et une video). La video est un pr??t payant, avec un co??t d'un euro, ce - qui porterait la somme totale due par l'adh??rent ?? 5 €. Selon + qui porterait la somme totale due par l'adh??rent ?? 5 €. Selon la valuer de cette pr??f??rence, ce pr??t sera permit ou non.
@@ -3130,6 +3405,71 @@
+
+ SuspendHoldsIntranet + + Default: Allow + + Asks: ___ holds to be suspended from the intranet. + + Values: + + + + Allow + + + + Don't allow + + + + Description: + + + + The holds suspention feature can be turned on and off in + the staff client by altering this system preference. If this + is set to 'allow' you will want to set the AutoResumeSuspendedHolds + system preference. + + +
+ +
+ SuspendHoldsOpac + + Default: Allow + + Asks: ___ holds to be suspended from the OPAC. + + Values: + + + + Allow + + + + Don't allow + + + + Description: + + + + The holds suspention feature can be turned on and off in + the OPAC by altering this system preference. If this is set to + 'allow' you will want to set the AutoResumeSuspendedHolds + system preference. + + +
+
+
Interface @@ -5965,7 +6305,6 @@
-
International @@ -8446,7 +8785,7 @@ src="http://platform.twitter.com/widgets.js"></script></div></
-
+
OpacAllowPublicListCreation Default: Allow @@ -9147,6 +9486,36 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype
+
+ AutoEmailOpacUser + + Valeur par d??faut: Ne pas envoyer + + Demande: ___ un courriel aux nouveaux inscrits avec le d??tail de leur compte. + + Description: + + + + AutoEmailOpacUser permet aux adh??rents de la biblioth??que d'??tre notifi??s par courriel des d??tails de leur compte lorsqu'un nouveau compte est cr????, ?? l'adresse mail sp??cifi??e dans la pr??f??rence AutoEmailPrimaryAddress. Le courriel comporte le nom d'utilisateur et le mot de passe donn??s au ou choisis par l'adh??rent lorsqu'il s'est inscrit, et peut ??tre personnalis?? en modifiant le message ACCTDETAILS. + + + + Valeurs: + + + + Ne pas envoyer + + + + Envoyer + + +
+
AutoEmailOpacUser & AutoEmailPrimaryAddress @@ -10060,6 +10429,44 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype
+
+ UseICU + + Valeur par d??faut: Ne pas utiliser + + Demande: ___ L'indexation Zebra ICU. + + Valeurs: + + + + Ne pas utiliser + + + + Utiliser + + + + Description: + + + + ICU est un param??trage de biblioth??ques de code fournissant le support pour Unicode et la globalisation pour les applications logicielles.. Ceci signifie que l'indexation Zebra ICU est n??cessaire uniquement si vous utilisez des caract??res non-roman dans votre catalogage. Si vous utilisez l'indexation Zebra ICU vous n'utiliserez pas QueryFuzzy. + + + + + Ce param??trage n'affecte pas l'indexation Zbera, il doit seulement ??tre utilis?? pour dire ?? Koha que vous avez activ?? l'indexation ICU si vous l'avez vraiment fait, parce qu'il n'y a aucun moyen pour que Koha le sache sinon. + + + + Voir avec votre administrateur syst??me si vous changez cette pr??f??rence afin de vous assurer que votre syst??me soit bien param??tr?? correctement pour que ??a fonctionne. + +
+ +
Results Display @@ -14608,7 +15015,92 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype
OAI Sets Configuration - Manage OAI Sets. + On this page you can create, modify and delete OAI-PMH + sets + +
+ Create a set + + To creat a set: + + + + Click on the link 'Add a new set' + + + + Fill the mandatory fields 'setSpec' and 'setName' + + + + Then you can add descriptions for this set. To do this + click on 'Add description' and fill the newly created text box. + You can add as many descriptions as you want. + + + + Click on 'Save' button' + + +
+ +
+ Modify/Delete a set + + To modify a set, just click on the link 'Modify' on the same + line of the set you want to modify. A form similar to set creation + form will appear and allow you to modify the setSpec, setName and + descriptions. + + To delete a set, just click on the link 'Delete' on the same + line of the set you want to delete. +
+ +
+ Define mappings + + Here you can define how a set will be build (what records will + belong to this set) by defining mappings. Mappings are a list of + conditions on record content. A record only need to match one + condition to belong to the set. + + + + Fill the fields 'Field', 'Subfield' and 'Value'. For + example if you want to include in this set all records that have + a 999$9 equal to 'XXX'. Fill 'Field' with 999, 'Subfield' with 9 + and 'Value' with XXX. + + + + If you want to add another condition, click on 'OR' button + and repeat step 1. + + + + Click on 'Save' + + + + To delete a condition, just leave at least one of 'Field', + 'Subfield' or 'Value' empty and click on 'Save'. + Actually, a condition is true if value in the + corresponding subfield is strictly equal to what is defined if + 'Value'. A record having 999$9 = 'XXX YYY' will not belong to a + set where condition is 999$9 = 'XXX'. + + + And it is case sensitive : a record having 999$9 = 'xxx' will + not belong to a set where condition is 999$9 = 'XXX'. +
+ +
+ Build sets + + Once you have configured all your sets, you have to build the + sets. This is done by calling the script + misc/migration_tools/build_oai_sets.pl. +
@@ -15188,7 +15680,6 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype - @@ -20587,56 +21078,50 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype - Enter any part of their name, username, email address or - barcode + Entrer une partie du nom, du login, de l'adresse courriel ou du code-barres de la carte du lecteur. - Email: + Courriel: - Enter any part of their email address. + Entrer une partie de l'adresse courriel. - Borrower number: + Num??ro d'adh??rent: - Enter the Koha borrower number + Entrer l'identifiant Koha du lecteur. - Phone number: + Num??ro de t??l??phone: - Enter the phone number exactly as it is in the system or - by using spaces between each batch of numbers. + Entrer le num??ro de t??l??phone tel qu'il a ??t?? saisi dans le syst??me ou en utilisant des espaces entre chaque groupe de num??ros. - Example: To find (212) 555-1212 you can search for it - exactly as it was entered or by searching for 212 555 - 1212 + Exemple: Pour trouver (212) 555-1212, vous pouvez rechercher ce num??ro en utilisant exactement cette forme ou en saisissant 212 555 1212 - If you want to filter your results to a specific branch or - category, you can click the plus sign [+] to the right of the search - box. + Si vous souhaitez filtrer vos r??sultats de recherche sur une biblioth??que ou une cat??gorie d'adh??rent sp??cifique, vous pouvez cliquer le bouton plus [+] ?? la droite du champ de recherche. - Advanced Patron Search + Recherche adh??rent avanc??e @@ -22261,14 +22746,12 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype
- In Processing / Book Cart Locations + Localisation "En traitement" / "En rangement" - Koha allows for handling temporary locations like the processing - center and/or book carts throughout the library. For this feature to - work you must first make sure you have authorized values set in the LOC category for PROC (Processing Center) - and CART (Book Cart). + Koha permet d'utiliser des localisations temporaires pour indiquer d'une document est en cours de traitement ou de rangement dans la biblioth??que. Pour que cette fonctionnalit?? fonctionne, vous devez avoir param??tr?? dans le liste de valeurs autoris??es localisation LOC le code PROC (En traitement ou Processing Center en anglais) + et CART (En rangement ou Book Cart en anglais). CART & PROC values in LOC @@ -22280,59 +22763,42 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype - Next you need to set the NewItemsDefaultLocation system - preference to PROC. This will set the new items to the Processing Center - as their default location. + Ensuite vous devez param??trer la pr??f??rence syst??me NewItemsDefaultLocation en indiquant comme localisation par d??faut d'un nouvel exemplaire "PROC". Ce param??trage permettra de renseigner par defaut la localisation "En traitement" pour chaque nouvel exemplaire. - Create items with their desired final shelving location. + Exemplariser avec la localisation finale. - These newly cataloged items will be temporarily set to the - PROC location and will display with whatever description PROC has. - The original location code entered at item creation is stored in the - new items column 'permanent_location', for future use. Items will - stay in the PROC location until they are checked in. To have those - items then move to the shelving cart: + Ces nouveaux exemplaires cr????s auront temporairement la localisation PROC (En traitement) et seront affich?? avec la description choisie pour cette valeur autoris??e. Le code de la localisation originale est stock??e dans le champ 'permanent_location' de la table items pour sa future utilisation. Les exemplaires garderont la localisation PROC tant qu'ils n'auront pas ??t?? pass?? en retour. Pour que ces exemplaires prennent la localisation "En rangement" : - Turn on the Activez la pr??f??rence syst??me InProcessingToShelvingCart - system preference + - Check in those newly-created items and they will be moved - to the location code of CART and display with whatever - description CART has. + Une fois le retour effectu??, ces nouveaux exemplaires prendront la localisation CART. Ces exemplaires s'afficheront avec la localisation "En rangement" ou n'importe quelle description indiqu??e pour cette valeur autoris??e. - A cron job runs at - specified intervals to age items from CART to the permanent - shelving location. (For example, an hourly cron entry of - cart_to_shelf.pl --hours 3 where --hours is the amount of time - an item should spend on the cart before aging to its permanent - location.) + Une t??che r??guli??re sera lanc?? ?? des intervals sp??cifiques pour remplacer la localisation CART par sa localisation permanente. (Par exemple, une t??che r??guli??re peut ??tre lanc??e toutes les 3 heures ainsi : cart_to_shelf.pl --hours 3 o?? le param??tre --hours correspond ?? la dur??e de rangement d'un document en rayon.) + - If the Si la pr??f??rence syst??me ReturnToShelvingCart - system preference is turned on, any newly-checked-in item - is also automatically put into the shelving cart, to be - covered by the same script run. + est activ??e, la localisation de tous les exemplaires retourn??s passera automatiquement ?? CART (En rangement), pour ensuite retrouv?? sa localisation permanent quand la t??che r??guli??re aura ??t?? lanc??e. - Checkins with confirmed holds will not go into the - shelving cart. If items on the shelving cart are checked - out, the cart location will be cleared. + Lors des retours, les documents r??serv??s ne prendront pas la localication CART (En rangement). Si un exemplaire avec la localisation CART est emprunt??, celui ci perd sa localisation CART et retrouve sa localisation permanente. @@ -22443,28 +22909,426 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype
+ + + Fran??ois + + Charbonnier + + + + BibLibre + + + + Nicole C. + + Engard + + Changed content where necessary. + + + 2012 + Plugin Firefox - Il existe un plugin Firefox qui fait office de pr??t de secours : - https://addons.mozilla.org/en-US/firefox/addon/14399 + There is an offline circulation tool that you can add to your + Firefox browser as a plugin/addon. To do so, just go to https://addons.mozilla.org/en/firefox/addon/koct/ + page and click on the "install now" button. You may have to confirm + the installation, just click on "install now" and then restart Firefox + to complete the installation. + + Once you have installed the plugin and restarted Firefox, you + will see the Koha logo in the add-on bar at the bottom right of + Firefox. + + + Koha Icon on Add-on Bar + + + + + + + + + A click on the logo will open the tool in its own window. + + + Koha Offline Circ Tool + + + + + + + + + The plugin consists of four tabs: + + + + The Check Out tab is where you check out items + + + + The Check In tab is where you check in items + + + + The Log tab keeps track of every transaction done while in + offline mode + + + + The log will keep information until you empty it. Each + time you open the plugin and it contains data in the log it + will warn you + + + Koha Offline Circ Warning + + + + + + + + If you'd like to clear the log, check the 'I want to + delete rows' box before hitting the 'OK' button. Otherwise + clicking 'OK' will keep the items in the log and let you + continue working with the tool. + + + + + + The Param tab is to set up the plugin + + - Une fois install?? vous avez l'icone de Koha en bas ?? droite de - votre ??cran de Firefox. + The first thing you want to do then is to set up the plugin. Go + to the Param tab to set up the plugin - Koha Icon on the Status Bar in Firefox + Koha Offline CIrc Params - + - Vous trouverez plus d'informations au sujet de l'utilisation de - cet outil ?? cette adresse : http://wiki.koha-community.org/wiki/Offline_circulation_firefox_plugin + Answer the 4 questions presented: + + + + Server = the URL of the librarian interface + + + + Branch Code = the code for the branch where you are + located + + + + Username = your staff account login + + + + Password = your staff account password + + + + + To save the settings, you will have to close the plugin + window and re-open it by clicking again on the Koha logo in the + add-on bar. + + You can create a staff account dedicated to the offline + circulation. So that, no matter who is at the circulation desk, + they can all use the same login. Along those lines, you can use a + group login that you already have in place for circulation as + well. + Once you have everything set up you can start checking items + in and out. + + Checking out: + + + Koha Offline Circulation Check Out + + + + + + + + + + + Go to the Check Out tab + + + + Scan the patron barcode + + + + Scan the item barcode + + + + Click 'Save' + + + + Checking in: + + + Koha Offline Circulation Check In + + + + + + + + + + + Go to the Check In tab + + + + Scan the item barcode + + + + Click Save + + + + Each time, you check out or check in an item, a new transaction + is recorded in the local plugin database and you will see, at the + bottom of the plugin how many transactions has been made during the + offline circulation. For example, "10 Row(s) Added" means you did 10 + transactions. + + + Koha Offline Circulation Tool Count + + + + + + + + + Then, if you want an overview of every transaction, go to the + Log tab. This tab will show you the transactions in the plugin + database + + + Koha Offline Circulation Log + + + + + + + + + + The status will be "Local." as long as you are offline and + don't process the transactions into Koha. + When your Internet connection comes back up you will want to + get these transactions in to Koha. Before processing these + transactions you should be aware of a few issues. + + Because you are not connected to your Koha database when using + this plugin holds will need additional processing. If an item you + check in while offline has a hold, the hold is kept on the item. + Since, you can't confirm holds found during the processing of every + check in, the holds stay on the item and will need to be managed + later. If you only checked in a few items you can just keep a record + of them all. If you checked in a lot of items you can use the Holds + Queue once it rebuilds to see what holds made it to the shelf + erroneously. + + Similarly, if an patron card was expired, the offline + circulation tool won't know about it, so the checkout will be recorded + regardless of the patron's account being blocked normally. + + You have two options for adding this data to Koha + + + + Commit to Koha + + + + If you checked in/out on more than one computer at the + same time, what you want is to process every transaction + consistently. Let's say for instance that one patron checked a + book out on one computer and then checked the same book in on + another computer. To be consistent, you need to record the + check out first and then the check in. Not the opposite! To do + so, you need to group every transaction in one place, sort + them all and then, process everything. So, you need to use the + "Commit to Koha" option from every plugin/computer you worked + with. This way, the log will go to Koha and be accessible from + the Offline Circulation page. + + + Circulation Menu + + + + + + + + + + + Get there: Circulation > Offline + Circulation (Firefox add-on) + + + Offline Circulation + + + + + + + + + + + Once all of the logs from all of the circulation + computers are loaded you will be able to check them all or + select just those you want to process into Koha. + + + + Click on the Process button and Koha will record every + sorted transaction one by one. For each transaction, the + status will change to: + + + + "Success." if the transaction was processed + correctly + + + + "Borrower not found." if the borrower card number is + incorrect + + + + "Item not found." if the item barcode is + wrong + + + + "Item not issued." if you checked in an available + item + + + + + + Once finished you will have a summary of all of your + transactions + + + Offline Circulation Summary + + + + + + + + + + + + + Apply directly + + + + If you performed all of the circulation actions on one + computer then everything is sorted already so you can choose + to "Apply directly" + + + + The status column will be updated to let you know if the + transactions were applied + + + + + "Success." if the transaction was processed + correctly + + + + "Borrower not found." if the borrower card number is + incorrect + + + + "Item not found." if the item barcode is + wrong + + + + "Item not issued." if you checked in an available + item + + + + + + Once you're finished you can review all of the items + right in the Log tab + + + Koha Offlince Circulation Apply + Directly + + + + + + + + + + + + + Once you are done you can clear the log by clicking Clear. If + you don't you will be warned the next time you open the Offline + Circulation tool. + + + Koha Offlince Circulation Tool Warning + + + + + + +
@@ -29621,7 +30485,7 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype pour les index Biblio, Index exemplaire, champs fixes et autres indexes sp??cifiques Z39.50 Bib-1 profile est constitu?? de diff??rents types d'attributs: Use, Relation, Position, Structure, - Truncature, et exhaustivit??. L'attribut bib-1 'Use' est utilis?? sur le tableau les autres + Truncature, et exhaustivit??. L'attribut bib-1 'Use' est utilis?? sur le tableau, les autres attributs sont utilis??s par la recherche. Il y a plus de 150 attributs mais vous n'??tes pas oblig?? de tous les utiliser. Les attributs que vous choisissez d'utiliser sont ceux qui deviennent des r??gles d'indexation pour votre base de donn??es. @@ -29665,56 +30529,31 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype also possible to set other attributes, such as the structure attribute. - In the MARC tags indexed column, there are some conventions used - that have specific meanings. They are: + Dans la colonne 'Etiquette MARC index??e', des conventions d'??criture sont utilis??es et ont un sens pr??cis. Ces conventions sont : - A three digit tag (100) means that all subfields in the tag - can be used in a search query. So, if you enter a search for - 'Jackson' as an author, you will retrieve records where Jackson - could be the last name or the first name. + Une ??tiquette de 3 chiffres (100) signifie que tous les sous-champs de l'??tiquette peuvent ??tre utilis?? dans une requ??te de recherche. Ainsi, si vous recherchez 'Jackson' comme auteur, vous retrouverez les notices o?? Jackson est le nom ou le pr??nom de l'auteur. - A three digit tag that has a '$' followed by a letter - (600$a) means that a search query will only search the 'a' - subfield. + Une ??tiquette de 3 chiffres qui poss??de un '$' suivi par une lettre (600$a) signifie que la requ??te de recherche ne portera que sur le sous-champ 'a' de cette ??tiquette. - A three digit tag that is followed by a ':' and a letter - (240:w) means that a search query can be further qualified. The - letter following the ':' identifies how to conduct the search. The - most common values you'll see are 'w' (word), 'p' (phrase), 's' - (sort), and 'n' (numeric). + Une ??tiquette de 3 chiffres suivie par un ':' et une lettre (240:w) signifie que le type de recherche est indiqu??e en plus dans la requ??te de recherche elle m??me. La lettre qui suit les ':' identifie comment la recheche doit ??tre r??alis??e. Les valeurs les plus communes sont :'w' (word), 'p' (phrase), 's' (sort), and 'n' (numeric). - The contents of the MARC tags, subfields, and/or fixed field - elements that are listed in this chart are all indexed. You'll see - that every attribute line is not mapped to a specific qualifier - (index)-LC card number, line 9 is one example. However, every indexed - word (a string of characters preceded and succeeded by a space) can be - searched using a keyword (kw) search. So, although an LC card number - specific index doesn't exist, you can still search by the LCCN since - tag 010 is assigned to the LC-card-number attribute. To verify this, - enter 72180055 in the persistent search box. You should retrieve The - gods themselves, by Isaac Asimov. - - Examples of fixed field elements indexing can be seen on the - chart between Attribute 8822 and Attribute 8703. These attributes are - most commonly used for limiting. The fixed field attributes currently - represent the BK codes. Other format codes, if needed, could be - defined. + Le contenu des ??tiquettes, sous-champs MARC, et/ou des ??l??ments fixes des champs qui sont list??s dans cette charte sont tous index??s. Vous verez que chaque ligne correspondant ?? un attribut n'est pas toujours mapp?? ?? un qualificatif sp??cifique (index). LC card number, ligne 9 est un exemple. Cependant, tous les mots index??s (une chaine de caract??res pr??c??d??e ou suivie d'un espace) peuvent ??tre cherch??s en utilisant le mot cl?? 'kw'. Ainsi, bien que l'index 'LC card number' n'existe pas, vous pouvez toujours rechercher par le LCNN puisque l'??tiquette 010 est assign??e ?? l'attribut LC-card-number. Pour le v??rifier, vous pouvez entrer 72180055 dans le champ de recherche simple. Vous devriez retrouver 'The gods themselves' par Isaac Asimov. + + Exemples d'??l??ments de champs fixes ind??x??s qui peuvent ??tre vus dans la charte entre l'Attributs 8822 et l'Attribut 8703. Ces attributs sont utilis??es habituellement comme limitation. Les attibuts pour les champs fixes repr??sente aujourd'hui les codes BK. D'autres codes, si n??cessaires, peuvent ??tre d??finis.
- Basic Searching + Recherche simple - The search box that library staff and library patrons will see - most often is the persistent search box at the top of the page. Koha - interprets the searches as keyword searches. + Le champ de recherche que les biblioth??caires et les usager verront le plus souvent est le champ persistant de recherche simple en haut de la page. Koha interpr??te les recherches ?? partir de ce champ comme une recherche par mot-cl??s. Koha search box @@ -29726,22 +30565,11 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype - To start a search, you enter a word or multiple words in the - search box. When a single word is entered, a keyword search is - performed. You can check this out by typing one word into the form and - note the number of results located. Then, repeat the search with a - minor change. In front of the search word, type 'kw=' followed by the - same search term. The results will be identical. + Pour faire une recherche, entrez un ou plusieurs mots dans le champ de recherche simple. Quand un seul mot est entr??, une recherche par mot-cl??s est lanc??e. Vous pouvez le constater en lanceant une recherche sur un seul terme et noter le nombre de r??sultats trouv??s. Ensuite, r??p??tez la recherche mais cette fois avec un nouvel ??l??ment. Devant le terme de recherche, ajoutez 'kw=' suivi par le terme de recherche. Vous verrez que le nombre de r??sultat est identique. - When you have more than one word in the search box, Koha will - still do a keyword search, but a bit differently. Each word will be - searched on its own, then the Boolean connector 'and' will narrow your - search to those items with all words contained in matching - records. + Quand vous avez plus d'une terme de recherche, Koha effectue toujours une recherche par mot-cl??s, mais celle ci est l??g??rement diff??rente. Chaque terme est recherch?? ind??pendamment les uns des autres, et ensuite, l'op??rateur bool??en 'and' limite la recherche aux notices qui contiennent tous les termes recherch??s. - Suppose you want to find material about how libraries are using - mashups. You'll select the major words and enter them into the - persistent search box. + Supposons que vous souhaitez trouver de la documentation sur la fa??on dont les biblioth??ques utilisent des 'mashups'. Vous allez selectionner les termes importants et les saisir dans le champ de recherche simple. Keyword Search @@ -29753,7 +30581,7 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype - The response to this search is: + La r??ponse ?? cette recherche est: Results @@ -29765,9 +30593,7 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype - The order of the words does not affect the retrieval results, so - you could also enter the search as "mashups library". The response to - this search is results + L'ordre des termes de recherche n'affecte pas le tri des r??sultats, donc vous pouvez saisir la recherche suivante "mashups library". La r??ponse ?? cette recherche est : Results @@ -29779,8 +30605,7 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype - Too many words in the search box will find very few matches, as - the following example illustrates: + Trop de termes dans le champ de recherche am??ne peu de r??sultats, comme l'illustre l'exemple suivant : No results found @@ -29794,11 +30619,9 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype
- Advanced Searching + Recherche avanc??e - When you can't find the most appropriate material with a general - search, you can move to the Advanced Search page by clicking on the - Search option on the persistent toolbar. + Quand vous ne trouvez pas de r??sultats qui vous conviennent avec la recherche simple, vous pouvez utiliser le formulaire de recherche avanc??e en cliquant sur le lien 'recherche avanc??e' sous le champ de recherche simple. Koha Menu @@ -29810,22 +30633,14 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype - The Advanced Search page offers many ways to limit the results - of your search. You can search using the Boolean operators AND, OR, - and NOT; limit by item type; limit by year and language; limit by - subtypes audience, content, format, or additional content types; by - location and by availability. + Le formulaire de recherche avanc??e offre plusieurs limitations de recherche. Vous pouvez utiliser les op??rateurs bool??en ET, OU, SAUF; limiter par type de document, limiter par ann??e et langue, limiter par les donn??es cod??es : audience, contenu, format ou type de contenu; limiter par localisation et disponibilit??. - The first limiting section on the Advanced Search page provides - a quick and simple way to use the Boolean operators in your search. - Note that this display depends on a system preference setting. This - option can be found on the Administration > System Preferences > - Searching page. The option called expandedSearchOption must be set - to 'show' to see the following display. + La premi??re section de limitation dans le formulaire de recherche avanc??e permet une utilisation rapide et simple des op??rateurs bool??en dans la recherche. Notez que cette affichage d??pend d'un param??trage dans vos pr??f??rences syst??me.T Cette option peut ??tre trouv??e dans Administration > Pr??f??rences syst??me > + Formulaire de recherche. L'option appel??e expandedSearchOption doit ??tre configur?? ?? 'montrer' pour voir l'affichage suivant. - Advanced Search Options + Options de la recherche avanc??e @@ -29834,16 +30649,9 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype - In this section you can choose among the many indexes by - clicking on the arrow in the first box. The blank box that follows is - where you enter your first search term or terms. On the second line, - you can choose the Boolean operator you want to use in your search. - The options are 'and', 'or', and 'not'. Then, you would again choose - the index to search, followed by the second term or terms. If you have - more concepts you want to include in your search, you can click the - [+] to add another line for your search. + Dans cette section, vous pouvez choisir parmis plusieurs index en cliquant sur les fl??ches dans le premier menu d??roulant. Le champ qui suit ce menu correspond au champ dans lequel vous allez entrer votre recherche. Sur la ligne suivante, vous pouvez choisir l'op??rateur Bool??en que vous souhaitez utiliser dans votre recherche. Les options sont 'et', 'ou', 'sauf'. Ensuite, vous pouvez de nouveau choisir un index et saisir un ou plusieurs termes de recherche. Si vous avez plusieurs concepts ?? saisir dans votre recherche, vous pouvez cliquer sur les [+] pour ajouter une nouvelle ligne de recherche. - A sample search is shown next, followed by its results: + Ci dessous, un exemple de recherche, suivi par ses r??sultats: Advanced Search @@ -33885,6 +34693,21 @@ print theme('pages_catalog'); Frequency suggestion: daily
+
+ Unsuspend Holds + + Script path: + misc/cronjobs/holds/auto_unsuspend_holds.pl + + Does: This script checks to find holds that should no longer + be suspended and removes the suspension if the AutoResumeSuspendedHolds + preference is set to 'allow'. This puts the patron back in to the + queue where they were when the hold was suspended. + + Frequency suggestion: daily +
+
Fines -- 1.7.5.4 From y Mon Jul 9 17:22:54 2012 From: y (y) Date: Mon, 9 Jul 2012 17:22:54 +0200 Subject: [Koha-docs] =?y?q?=5BPATCH=202/2=5D=20xml=20errors?= Message-ID: <1341847374-30945-1-git-send-email-y> From: Laurence Lefaucheur --- fr/manual.xml | 3 --- 1 files changed, 0 insertions(+), 3 deletions(-) diff --git a/fr/manual.xml b/fr/manual.xml index 0baf4ca..b0479ed 100644 --- a/fr/manual.xml +++ b/fr/manual.xml @@ -2075,7 +2075,6 @@
-
Circulation @@ -4135,7 +4134,6 @@ linkend="selfcheckout">libre service de Koha.
-
Cr??ateurs @@ -10844,7 +10842,6 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype
-
Serials -- 1.7.5.4 From nengard at gmail.com Mon Jul 9 20:26:57 2012 From: nengard at gmail.com (Nicole Engard) Date: Mon, 9 Jul 2012 14:26:57 -0400 Subject: [Koha-docs] [PATCH 1/2] French translation update (miscellaneous) In-Reply-To: <4ffb081b.aa56b40a.1965.2911SMTPIN_ADDED@mx.google.com> References: <4ffb081b.aa56b40a.1965.2911SMTPIN_ADDED@mx.google.com> Message-ID: I'm a bit confused by this. I can't seem to apply it and the subject and email address are very wonky. Here's the error I get: new-host:manual nengard$ git am -3 -i -u fr1.txt fatal: cannot convert from y to UTF-8 Can you maybe email the patch as an attachment? Or does anyone have an idea of what to do to apply this patch? Nicole PS. Please remember to tell me what version of the manual your patch is for (this time I see the 3.8 part in the file, but I don't want to have to look for that everytime (and it's not always there) On Mon, Jul 9, 2012 at 11:22 AM, wrote: > From: Laurence Lefaucheur > > --- > fr/manual.xml | 1181 ++++++++++++++++++++++++++++++++++++++++++++++++--------- > 1 files changed, 1002 insertions(+), 179 deletions(-) > > diff --git a/fr/manual.xml b/fr/manual.xml > index 231c427..0baf4ca 100644 > --- a/fr/manual.xml > +++ b/fr/manual.xml > @@ -2,10 +2,10 @@ > "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"> > > - > + > Manuel Koha 3.8 (fr) > > - > + > Nicole C. > > Engard > @@ -63,14 +63,26 @@ > Traduction fran?aise > > > - > + > + Fran?ois > + > + Charbonnier > + > + > + BibLibre > + > + > + Traduction fran?aise > + > + > + > 2012 > > - Nicole C. Engard/ByWater Solutions / BibLibre/Laurence > - Lefaucheur > + Nicole C. Engard/ByWater Solutions / Laurence > + Lefaucheur/BibLibre > > > - > + > Ce manuel est publi? sous licence url="http://www.gnu.org/licenses/gpl.html">GNU General Public License, > version 3 ou ult?rieure > @@ -79,7 +91,7 @@ > Appendix > > > - 2011 > + 2012 > > > > @@ -202,26 +214,26 @@ > >
> > -
> +
> AcqViewBaskets > > - Default: created by staff member > + Valeur par d?faut: cr??s par le biblioth?caire > > - Asks: Show baskets ___ > + Demande: Afficher les paniers ___ > > - Values: > + Valeurs: > > > > - created by staff member > + cr??s par le biblioth?caire > > > > - from staff member's branch > + de la biblioth?que > > > > - in system, regardless of owner > + du syst?me, peu importe le propri?taire > > > > @@ -229,17 +241,7 @@ > > > > - When in acquisitions this preference allows you to > - control whose baskets you can see when looking at a vendor. > - The default value of 'created by staff member' makes it so > - that you only see the baskets you created. Choosing to see > - baskets 'from staff member's branch' will show you the baskets > - created by anyone at the branch you're logged in at. Finally, > - you can choose to set this preference to show you all baskets > - regardless of who created it ('in system, regardless of > - owner). Regardless of which value you choose for this > - preference, superlibrarians can see all baskets created in the > - system. > + Quand vous ?tes dans les acquisitions cette pr?f?rence vous permet de contr?ler quels sont les paniers que vous pouvez voir pour un fournisseur. La valeur par d?faut est 'cr??s par le biblioth?caire', ce qui fait que vous ne voyez que les paniers que vous avez cr??s. Choisir de voir les paniers 'de la biblioth?que' vous permet de voir les paniers cr??s par n'importe qui dans la biblioth?que ? laquelle vous ?tes connect?. Enfin, vous pouvez choisir de positionner cette pr?f?rence pour afficher tous les paniers, ind?pendamment de qui les a cr??s ('du syst?me, peu importe le propri?taire'). Quelle que soit la valeur choisie pour cette pr?f?rence, les superlibrarians peuvent voir tous les paniers cr??s dans le syst?me. > > >
> @@ -318,6 +320,25 @@ >
> > > +
> + UniqueItemFields > + > + Valeur par d?faut: barcode > + > + Demande:___ (liste de champs uniques pour les exemplaires, s?par?s par des espaces ; doivent ?tre des champs valides de la table SQL + url="http://schema.koha-community.org/tables/items.html">items > + ) > + > + Description: > + > + > + > + Si cette pr?f?rence est laiss?e vide, ? l'ajout d'exemplaires dans les acquisitions il n'y aura pas de v?rification d'unicit?. Ceci signifie qu'un doublon de code barre peut ?tre cr?? dans les acquisitions, ce qui provoquera des erreurs ult?rieurement lors des pr?ts et retours d'exemplaires. > + > + > +
> + > + >
> Impression > > @@ -791,7 +812,53 @@ > Situ? sous : Accueil > Administration > > Pr?f?rences syst?me > Autorit?s > > -
> +
> + General > + > +
> + AutoCreateAuthorities > + > + Default: do not generate > + > + Asks: When editing records, ___ authority records that are > + missing. > + > + Values: > + > + > + > + do not generate > + > + > + > + generate > + > + > + > + > + + linkend="BiblioAddsAuthorities">BiblioAddsAuthorities > + must be set to "allow" for this to have any effect > + > + > + Description: > + > + > + > + When this and + linkend="BiblioAddsAuthorities">BiblioAddsAuthorities > + are both turned on, automatically create authority records for > + headings that don't have any authority link when cataloging. > + When BiblioAddsAuthorities is on and AutoCreateAuthorities is > + turned off, do not automatically generate authority records, > + but allow the user to enter headings that don't match an > + existing authority. When BiblioAddsAuthorities is off, this > + has no effect. > + > + > +
> + > +
> BiblioAddsAuthorities > > Valeur par d?faut : cr?er > @@ -830,7 +897,7 @@ > >
> > -
> +
> dontmerge > > Valeur par d?faut : Ne pas mettre ? jour automatiquement > @@ -857,7 +924,7 @@ > >
> > -
> +
> MARCAuthorityControlField008 > > Valeur par d?faut : || aca||aabn | a|a d > @@ -881,7 +948,7 @@ > >
> > -
> +
> UseAuthoritiesForTracings > > Valeur par d?faut : Ne pas utiliser > @@ -934,6 +1001,214 @@ >
>
> > +
> + Linker > + > + Cette pr?f?rence contr?le comment Koha lie les notices bibliographiques aux notices autorit?s. Toutes les notices bibliographiques ajout?es ? Koha une fois cette pr?f?rence param?tr?e seront li?es automatiquement aux notices autorit?s ; pour les notices ajout?es avant que la pr?f?rence soit param?tr?e, un script (misc/link_bibs_to_authorities.pl) peut ?tre ex?cut? par votre administrateur syst?me pour activer les liens. > + > + > + > +
> + LinkerKeepStale > + > + Default: Do not > + > + Asks: ___ keep existing links to authority records for > + headings where the linker is unable to find a match. > + > + Values: > + > + > + > + Do > + > + > + > + Do not > + > + > + > + Description: > + > + > + > + When set to 'Do', the linker will never remove a link to > + an authority record, though, depending on the value of + linkend="LinkerRelink">LinkerRelink, it may change the > + link. > + > + > +
> + > +
> + LinkerModule > + > + Default: Default > + > + Asks: Use the ___ linker module for matching headings to > + authority records. > + > + Values: > + > + > + > + Default > + > + > + > + Retains Koha's previous behavior of only creating > + links when there is an exact match to one and only one > + authority record; if the + linkend="LinkerOptions">LinkerOptions preference is > + set to 'broader_headings', it will try to link headings to > + authority records for broader headings by removing > + subfields from the end of the heading > + > + > + > + > + > + First match > + > + > + > + Creates a link to the first authority record that > + matches a given heading, even if there is more than one > + authority record that matches > + > + > + > + > + > + Last match > + > + > + > + Creates a link to the last authority record that > + matches a given heading, even if there is more than one > + record that matches > + > + > + > + > + > + Description: > + > + > + > + This preference tells Koha which match to use when > + searching for authority matches when saving a record. > + > + > +
> + > +
> + LinkerOptions > + > + Asks: Set the following options for the authority linker > + ___ > + > + Description: > + > + > + > + This is a pipe separated (|) list of options. At the > + moment, the only option available is "broader_headings." With > + this option set to "broader_headings", the linker will try to > + match the following heading as follows: > + > + =600 10$aCamins-Esakov, Jared$xCoin > + collections$vCatalogs$vEarly works to 1800. > + > + First: Camins-Esakov, Jared--Coin > + collections--Catalogs--Early works to 1800 > + > + Next: Camins-Esakov, Jared--Coin > + collections--Catalogs > + > + Next: Camins-Esakov, Jared--Coin collections > + > + Next: Camins-Esakov, Jared (matches! if a previous > + attempt had matched, it would not have tried this) > + > + > +
> + > + > +
> +
> + >
> Catalogage > > @@ -1371,7 +1646,7 @@ >
>
> > -
> +
> > > Linda > @@ -2178,12 +2453,12 @@ > > > Exemple : Dans votre biblioth?que la limite d?finie pour > - les amendes est de 5 € (c'est ? dire qu'un adh?rent ayant accumul? > + les amendes est de 5 € (c'est ? dire qu'un adh?rent ayant accumul? > 5 euros d'amendes n'est plus autoris? ? emrunter de documents). > Un adh?rent ayant d?j? 4 euros d'amendes impay?es sur son compte > se pr?sente ? la banque de pr?t avec 5 documents (4 livres et une > video). La video est un pr?t payant, avec un co?t d'un euro, ce > - qui porterait la somme totale due par l'adh?rent ? 5 €. Selon > + qui porterait la somme totale due par l'adh?rent ? 5 €. Selon > la valuer de cette pr?f?rence, ce pr?t sera permit ou non. >
> > @@ -3130,6 +3405,71 @@ >
>
> > +
> + SuspendHoldsIntranet > + > + Default: Allow > + > + Asks: ___ holds to be suspended from the intranet. > + > + Values: > + > + > + > + Allow > + > + > + > + Don't allow > + > + > + > + Description: > + > + > + > + The holds suspention feature can be turned on and off in > + the staff client by altering this system preference. If this > + is set to 'allow' you will want to set the + linkend="AutoResumeSuspendedHolds">AutoResumeSuspendedHolds > + system preference. > + > + > +
> + > +
> + SuspendHoldsOpac > + > + Default: Allow > + > + Asks: ___ holds to be suspended from the OPAC. > + > + Values: > + > + > + > + Allow > + > + > + > + Don't allow > + > + > + > + Description: > + > + > + > + The holds suspention feature can be turned on and off in > + the OPAC by altering this system preference. If this is set to > + 'allow' you will want to set the + linkend="AutoResumeSuspendedHolds">AutoResumeSuspendedHolds > + system preference. > + > + > +
> +
> + >
> Interface > > @@ -5965,7 +6305,6 @@ > >
>
> - > >
> International > @@ -8446,7 +8785,7 @@ src="http://platform.twitter.com/widgets.js"></script></div></ > >
> > -
> +
> OpacAllowPublicListCreation > > Default: Allow > @@ -9147,6 +9486,36 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype > >
> > +
> + AutoEmailOpacUser > + > + Valeur par d?faut: Ne pas envoyer > + > + Demande: ___ un courriel aux nouveaux inscrits avec le d?tail de leur compte. > + > + Description: > + > + > + > + AutoEmailOpacUser permet aux adh?rents de la biblioth?que d'?tre notifi?s par courriel des d?tails de leur compte lorsqu'un nouveau compte est cr??, ? l'adresse mail sp?cifi?e dans la pr?f?rence + linkend="AutoEmailPrimaryAddress">AutoEmailPrimaryAddress. Le courriel comporte le nom d'utilisateur et le mot de passe donn?s au ou choisis par l'adh?rent lorsqu'il s'est inscrit, et peut ?tre personnalis? en modifiant le message + linkend="ACCTDETAILS">ACCTDETAILS. > + > + > + > + Valeurs: > + > + > + > + Ne pas envoyer > + > + > + > + Envoyer > + > + > +
> + >
> AutoEmailOpacUser & AutoEmailPrimaryAddress > > @@ -10060,6 +10429,44 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype >
>
> > +
> + UseICU > + > + Valeur par d?faut: Ne pas utiliser > + > + Demande: ___ L'indexation Zebra ICU. > + > + Valeurs: > + > + > + > + Ne pas utiliser > + > + > + > + Utiliser > + > + > + > + Description: > + > + > + > + ICU est un param?trage de biblioth?ques de code fournissant le support pour Unicode et la globalisation pour les applications logicielles.. Ceci signifie que l'indexation Zebra ICU est n?cessaire uniquement si vous utilisez des caract?res non-roman dans votre catalogage. Si vous utilisez l'indexation Zebra ICU vous n'utiliserez pas + linkend="QueryFuzzy">QueryFuzzy. > + > + > + > + > + Ce param?trage n'affecte pas l'indexation Zbera, il doit seulement ?tre utilis? pour dire ? Koha que vous avez activ? l'indexation ICU si vous l'avez vraiment fait, parce qu'il n'y a aucun moyen pour que Koha le sache sinon. > + > + > + > + Voir avec votre administrateur syst?me si vous changez cette pr?f?rence afin de vous assurer que votre syst?me soit bien param?tr? correctement pour que ?a fonctionne. > + > +
> + > + >
> Results Display > > @@ -14608,7 +15015,92 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype >
> OAI Sets Configuration > > - Manage OAI Sets. > + On this page you can create, modify and delete OAI-PMH > + sets > + > +
> + Create a set > + > + To creat a set: > + > + > + > + Click on the link 'Add a new set' > + > + > + > + Fill the mandatory fields 'setSpec' and 'setName' > + > + > + > + Then you can add descriptions for this set. To do this > + click on 'Add description' and fill the newly created text box. > + You can add as many descriptions as you want. > + > + > + > + Click on 'Save' button' > + > + > +
> + > +
> + Modify/Delete a set > + > + To modify a set, just click on the link 'Modify' on the same > + line of the set you want to modify. A form similar to set creation > + form will appear and allow you to modify the setSpec, setName and > + descriptions. > + > + To delete a set, just click on the link 'Delete' on the same > + line of the set you want to delete. > +
> + > +
> + Define mappings > + > + Here you can define how a set will be build (what records will > + belong to this set) by defining mappings. Mappings are a list of > + conditions on record content. A record only need to match one > + condition to belong to the set. > + > + > + > + Fill the fields 'Field', 'Subfield' and 'Value'. For > + example if you want to include in this set all records that have > + a 999$9 equal to 'XXX'. Fill 'Field' with 999, 'Subfield' with 9 > + and 'Value' with XXX. > + > + > + > + If you want to add another condition, click on 'OR' button > + and repeat step 1. > + > + > + > + Click on 'Save' > + > + > + > + To delete a condition, just leave at least one of 'Field', > + 'Subfield' or 'Value' empty and click on 'Save'. > + Actually, a condition is true if value in the > + corresponding subfield is strictly equal to what is defined if > + 'Value'. A record having 999$9 = 'XXX YYY' will not belong to a > + set where condition is 999$9 = 'XXX'. > + > + > + And it is case sensitive : a record having 999$9 = 'xxx' will > + not belong to a set where condition is 999$9 = 'XXX'. > +
> + > +
> + Build sets > + > + Once you have configured all your sets, you have to build the > + sets. This is done by calling the script > + misc/migration_tools/build_oai_sets.pl. > +
>
>
> > @@ -15188,7 +15680,6 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype > > > > - > > > > @@ -20587,56 +21078,50 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype > > > > - Enter any part of their name, username, email address or > - barcode > + Entrer une partie du nom, du login, de l'adresse courriel ou du code-barres de la carte du lecteur. > > > > > > - Email: > + Courriel: > > > > - Enter any part of their email address. > + Entrer une partie de l'adresse courriel. > > > > > > - Borrower number: > + Num?ro d'adh?rent: > > > > - Enter the Koha borrower number > + Entrer l'identifiant Koha du lecteur. > > > > > > - Phone number: > + Num?ro de t?l?phone: > > > > - Enter the phone number exactly as it is in the system or > - by using spaces between each batch of numbers. > + Entrer le num?ro de t?l?phone tel qu'il a ?t? saisi dans le syst?me ou en utilisant des espaces entre chaque groupe de num?ros. > > > > - Example: To find (212) 555-1212 you can search for it > - exactly as it was entered or by searching for 212 555 > - 1212 > + Exemple: Pour trouver (212) 555-1212, vous pouvez rechercher ce num?ro en utilisant exactement cette forme ou en saisissant 212 555 1212 > > > > > > - If you want to filter your results to a specific branch or > - category, you can click the plus sign [+] to the right of the search > - box. > + Si vous souhaitez filtrer vos r?sultats de recherche sur une biblioth?que ou une cat?gorie d'adh?rent sp?cifique, vous pouvez cliquer le bouton plus [+] ? la droite du champ de recherche. > > > - Advanced Patron Search > + Recherche adh?rent avanc?e > > > > @@ -22261,14 +22746,12 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype > > >
> - In Processing / Book Cart Locations > + Localisation "En traitement" / "En rangement" > > - Koha allows for handling temporary locations like the processing > - center and/or book carts throughout the library. For this feature to > - work you must first make sure you have - linkend="authorizedvalues">authorized values set in the - linkend="shelvelocvals">LOC category for PROC (Processing Center) > - and CART (Book Cart). > + Koha permet d'utiliser des localisations temporaires pour indiquer d'une document est en cours de traitement ou de rangement dans la biblioth?que. Pour que cette fonctionnalit? fonctionne, vous devez avoir param?tr? dans le liste de + linkend="authorizedvalues">valeurs autoris?es localisation + linkend="shelvelocvals">LOC le code PROC (En traitement ou Processing Center en anglais) > + et CART (En rangement ou Book Cart en anglais). > > > CART & PROC values in LOC > @@ -22280,59 +22763,42 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype > > > > - Next you need to set the - linkend="NewItemsDefaultLocation">NewItemsDefaultLocation system > - preference to PROC. This will set the new items to the Processing Center > - as their default location. > + Ensuite vous devez param?trer la pr?f?rence syst?me + linkend="NewItemsDefaultLocation">NewItemsDefaultLocation en indiquant comme localisation par d?faut d'un nouvel exemplaire "PROC". Ce param?trage permettra de renseigner par defaut la localisation "En traitement" pour chaque nouvel exemplaire. > > - Create items with their desired final shelving location. > + Exemplariser avec la localisation finale. > > > > - These newly cataloged items will be temporarily set to the > - PROC location and will display with whatever description PROC has. > - The original location code entered at item creation is stored in the > - new items column 'permanent_location', for future use. Items will > - stay in the PROC location until they are checked in. To have those > - items then move to the shelving cart: > + Ces nouveaux exemplaires cr??s auront temporairement la localisation PROC (En traitement) et seront affich? avec la description choisie pour cette valeur autoris?e. Le code de la localisation originale est stock?e dans le champ 'permanent_location' de la table items pour sa future utilisation. Les exemplaires garderont la localisation PROC tant qu'ils n'auront pas ?t? pass? en retour. Pour que ces exemplaires prennent la localisation "En rangement" : > > > > - Turn on the + Activez la pr?f?rence syst?me linkend="InProcessingToShelvingCart">InProcessingToShelvingCart > - system preference > + > > > > - Check in those newly-created items and they will be moved > - to the location code of CART and display with whatever > - description CART has. > + Une fois le retour effectu?, ces nouveaux exemplaires prendront la localisation CART. Ces exemplaires s'afficheront avec la localisation "En rangement" ou n'importe quelle description indiqu?e pour cette valeur autoris?e. > > > > - A cron job runs at > - specified intervals to age items from CART to the permanent > - shelving location. (For example, an hourly cron entry of > - cart_to_shelf.pl --hours 3 where --hours is the amount of time > - an item should spend on the cart before aging to its permanent > - location.) > + Une t?che r?guli?re sera lanc? ? des intervals sp?cifiques pour remplacer la localisation CART par sa localisation permanente. (Par exemple, une t?che r?guli?re peut ?tre lanc?e toutes les 3 heures ainsi : cart_to_shelf.pl --hours 3 o? le param?tre --hours correspond ? la dur?e de rangement d'un document en rayon.) > + > > > > > - If the + Si la pr?f?rence syst?me linkend="ReturnToShelvingCart">ReturnToShelvingCart > - system preference is turned on, any newly-checked-in item > - is also automatically put into the shelving cart, to be > - covered by the same script run. > + est activ?e, la localisation de tous les exemplaires retourn?s passera automatiquement ? CART (En rangement), pour ensuite retrouv? sa localisation permanent quand la t?che r?guli?re aura ?t? lanc?e. > > > > > > - Checkins with confirmed holds will not go into the > - shelving cart. If items on the shelving cart are checked > - out, the cart location will be cleared. > + Lors des retours, les documents r?serv?s ne prendront pas la localication CART (En rangement). Si un exemplaire avec la localisation CART est emprunt?, celui ci perd sa localisation CART et retrouve sa localisation permanente. > > > > @@ -22443,28 +22909,426 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype > > >
> + > + > + Fran?ois > + > + Charbonnier > + > + > + > + BibLibre > + > + > + > + Nicole C. > + > + Engard > + > + Changed content where necessary. > + > + > + 2012 > + > Plugin Firefox > > - Il existe un plugin Firefox qui fait office de pr?t de secours : > - - url="https://addons.mozilla.org/en-US/firefox/addon/14399">https://addons.mozilla.org/en-US/firefox/addon/14399 > + There is an offline circulation tool that you can add to your > + Firefox browser as a plugin/addon. To do so, just go to + url="https://addons.mozilla.org/en/firefox/addon/koct/">https://addons.mozilla.org/en/firefox/addon/koct/ > + page and click on the "install now" button. You may have to confirm > + the installation, just click on "install now" and then restart Firefox > + to complete the installation. > + > + Once you have installed the plugin and restarted Firefox, you > + will see the Koha logo in the add-on bar at the bottom right of > + Firefox. > + > + > + Koha Icon on Add-on Bar > + > + > + > + > + > + > + > + > + A click on the logo will open the tool in its own window. > + > + > + Koha Offline Circ Tool > + > + > + > + > + > + > + > + > + The plugin consists of four tabs: > + > + > + > + The Check Out tab is where you check out items > + > + > + > + The Check In tab is where you check in items > + > + > + > + The Log tab keeps track of every transaction done while in > + offline mode > + > + > + > + The log will keep information until you empty it. Each > + time you open the plugin and it contains data in the log it > + will warn you > + > + > + Koha Offline Circ Warning > + > + > + > + > + > + > + > + If you'd like to clear the log, check the 'I want to > + delete rows' box before hitting the 'OK' button. Otherwise > + clicking 'OK' will keep the items in the log and let you > + continue working with the tool. > + > + > + > + > + > + The Param tab is to set up the plugin > + > + > > - Une fois install? vous avez l'icone de Koha en bas ? droite de > - votre ?cran de Firefox. > + The first thing you want to do then is to set up the plugin. Go > + to the Param tab to set up the plugin > > > - Koha Icon on the Status Bar in Firefox > + Koha Offline CIrc Params > > > > - > + > > > > > - Vous trouverez plus d'informations au sujet de l'utilisation de > - cet outil ? cette adresse : - url="http://wiki.koha-community.org/wiki/Offline_circulation_firefox_plugin">http://wiki.koha-community.org/wiki/Offline_circulation_firefox_plugin > + Answer the 4 questions presented: > + > + > + > + Server = the URL of the librarian interface > + > + > + > + Branch Code = the code for the branch where you are > + located > + > + > + > + Username = your staff account login > + > + > + > + Password = your staff account password > + > + > + > + > + To save the settings, you will have to close the plugin > + window and re-open it by clicking again on the Koha logo in the > + add-on bar. > + > + You can create a staff account dedicated to the offline > + circulation. So that, no matter who is at the circulation desk, > + they can all use the same login. Along those lines, you can use a > + group login that you already have in place for circulation as > + well. > + Once you have everything set up you can start checking items > + in and out. > + > + Checking out: > + > + > + Koha Offline Circulation Check Out > + > + > + > + > + > + > + > + > + > + > + Go to the Check Out tab > + > + > + > + Scan the patron barcode > + > + > + > + Scan the item barcode > + > + > + > + Click 'Save' > + > + > + > + Checking in: > + > + > + Koha Offline Circulation Check In > + > + > + > + > + > + > + > + > + > + > + Go to the Check In tab > + > + > + > + Scan the item barcode > + > + > + > + Click Save > + > + > + > + Each time, you check out or check in an item, a new transaction > + is recorded in the local plugin database and you will see, at the > + bottom of the plugin how many transactions has been made during the > + offline circulation. For example, "10 Row(s) Added" means you did 10 > + transactions. > + > + > + Koha Offline Circulation Tool Count > + > + > + > + > + > + > + > + > + Then, if you want an overview of every transaction, go to the > + Log tab. This tab will show you the transactions in the plugin > + database > + > + > + Koha Offline Circulation Log > + > + > + > + > + > + > + > + > + > + The status will be "Local." as long as you are offline and > + don't process the transactions into Koha. > + When your Internet connection comes back up you will want to > + get these transactions in to Koha. Before processing these > + transactions you should be aware of a few issues. > + > + Because you are not connected to your Koha database when using > + this plugin holds will need additional processing. If an item you > + check in while offline has a hold, the hold is kept on the item. > + Since, you can't confirm holds found during the processing of every > + check in, the holds stay on the item and will need to be managed > + later. If you only checked in a few items you can just keep a record > + of them all. If you checked in a lot of items you can use the Holds > + Queue once it rebuilds to see what holds made it to the shelf > + erroneously. > + > + Similarly, if an patron card was expired, the offline > + circulation tool won't know about it, so the checkout will be recorded > + regardless of the patron's account being blocked normally. > + > + You have two options for adding this data to Koha > + > + > + > + Commit to Koha > + > + > + > + If you checked in/out on more than one computer at the > + same time, what you want is to process every transaction > + consistently. Let's say for instance that one patron checked a > + book out on one computer and then checked the same book in on > + another computer. To be consistent, you need to record the > + check out first and then the check in. Not the opposite! To do > + so, you need to group every transaction in one place, sort > + them all and then, process everything. So, you need to use the > + "Commit to Koha" option from every plugin/computer you worked > + with. This way, the log will go to Koha and be accessible from > + the Offline Circulation page. > + > + > + Circulation Menu > + > + > + > + > + > + > + > + > + > + > + Get there: Circulation > Offline > + Circulation (Firefox add-on) > + > + > + Offline Circulation > + > + > + > + > + > + > + > + > + > + > + Once all of the logs from all of the circulation > + computers are loaded you will be able to check them all or > + select just those you want to process into Koha. > + > + > + > + Click on the Process button and Koha will record every > + sorted transaction one by one. For each transaction, the > + status will change to: > + > + > + > + "Success." if the transaction was processed > + correctly > + > + > + > + "Borrower not found." if the borrower card number is > + incorrect > + > + > + > + "Item not found." if the item barcode is > + wrong > + > + > + > + "Item not issued." if you checked in an available > + item > + > + > + > + > + > + Once finished you will have a summary of all of your > + transactions > + > + > + Offline Circulation Summary > + > + > + > + > + > + > + > + > + > + > + > + > + Apply directly > + > + > + > + If you performed all of the circulation actions on one > + computer then everything is sorted already so you can choose > + to "Apply directly" > + > + > + > + The status column will be updated to let you know if the > + transactions were applied > + > + > + > + > + "Success." if the transaction was processed > + correctly > + > + > + > + "Borrower not found." if the borrower card number is > + incorrect > + > + > + > + "Item not found." if the item barcode is > + wrong > + > + > + > + "Item not issued." if you checked in an available > + item > + > + > + > + > + > + Once you're finished you can review all of the items > + right in the Log tab > + > + > + Koha Offlince Circulation Apply > + Directly > + > + > + > + > + > + > + > + > + > + > + > + > + Once you are done you can clear the log by clicking Clear. If > + you don't you will be warned the next time you open the Offline > + Circulation tool. > + > + > + Koha Offlince Circulation Tool Warning > + > + > + > + > + > + > + >
> >
> @@ -29621,7 +30485,7 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype > pour les index Biblio, Index exemplaire, champs fixes et autres > indexes sp?cifiques Z39.50 Bib-1 profile est constitu? de diff?rents > types d'attributs: Use, Relation, Position, Structure, > - Truncature, et exhaustivit?. L'attribut bib-1 'Use' est utilis? sur le tableau les autres > + Truncature, et exhaustivit?. L'attribut bib-1 'Use' est utilis? sur le tableau, les autres > attributs sont utilis?s par la recherche. Il y a plus de 150 attributs mais > vous n'?tes pas oblig? de tous les utiliser. Les attributs que vous choisissez d'utiliser > sont ceux qui deviennent des r?gles d'indexation pour votre base de donn?es. > @@ -29665,56 +30529,31 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype > also possible to set other attributes, such as the structure > attribute. > > - In the MARC tags indexed column, there are some conventions used > - that have specific meanings. They are: > + Dans la colonne 'Etiquette MARC index?e', des conventions d'?criture sont utilis?es et ont un sens pr?cis. Ces conventions sont : > > > > - A three digit tag (100) means that all subfields in the tag > - can be used in a search query. So, if you enter a search for > - 'Jackson' as an author, you will retrieve records where Jackson > - could be the last name or the first name. > + Une ?tiquette de 3 chiffres (100) signifie que tous les sous-champs de l'?tiquette peuvent ?tre utilis? dans une requ?te de recherche. Ainsi, si vous recherchez 'Jackson' comme auteur, vous retrouverez les notices o? Jackson est le nom ou le pr?nom de l'auteur. > > > > - A three digit tag that has a '$' followed by a letter > - (600$a) means that a search query will only search the 'a' > - subfield. > + Une ?tiquette de 3 chiffres qui poss?de un '$' suivi par une lettre (600$a) signifie que la requ?te de recherche ne portera que sur le sous-champ 'a' de cette ?tiquette. > > > > - A three digit tag that is followed by a ':' and a letter > - (240:w) means that a search query can be further qualified. The > - letter following the ':' identifies how to conduct the search. The > - most common values you'll see are 'w' (word), 'p' (phrase), 's' > - (sort), and 'n' (numeric). > + Une ?tiquette de 3 chiffres suivie par un ':' et une lettre (240:w) signifie que le type de recherche est indiqu?e en plus dans la requ?te de recherche elle m?me. La lettre qui suit les ':' identifie comment la recheche doit ?tre r?alis?e. Les valeurs les plus communes sont :'w' (word), 'p' (phrase), 's' (sort), and 'n' (numeric). > > > > - The contents of the MARC tags, subfields, and/or fixed field > - elements that are listed in this chart are all indexed. You'll see > - that every attribute line is not mapped to a specific qualifier > - (index)-LC card number, line 9 is one example. However, every indexed > - word (a string of characters preceded and succeeded by a space) can be > - searched using a keyword (kw) search. So, although an LC card number > - specific index doesn't exist, you can still search by the LCCN since > - tag 010 is assigned to the LC-card-number attribute. To verify this, > - enter 72180055 in the persistent search box. You should retrieve The > - gods themselves, by Isaac Asimov. > - > - Examples of fixed field elements indexing can be seen on the > - chart between Attribute 8822 and Attribute 8703. These attributes are > - most commonly used for limiting. The fixed field attributes currently > - represent the BK codes. Other format codes, if needed, could be > - defined. > + Le contenu des ?tiquettes, sous-champs MARC, et/ou des ?l?ments fixes des champs qui sont list?s dans cette charte sont tous index?s. Vous verez que chaque ligne correspondant ? un attribut n'est pas toujours mapp? ? un qualificatif sp?cifique (index). LC card number, ligne 9 est un exemple. Cependant, tous les mots index?s (une chaine de caract?res pr?c?d?e ou suivie d'un espace) peuvent ?tre cherch?s en utilisant le mot cl? 'kw'. Ainsi, bien que l'index 'LC card number' n'existe pas, vous pouvez toujours rechercher par le LCNN puisque l'?tiquette 010 est assign?e ? l'attribut LC-card-number. Pour le v?rifier, vous pouvez entrer 72180055 dans le champ de recherche simple. Vous devriez retrouver 'The gods themselves' par Isaac Asimov. > + > + Exemples d'?l?ments de champs fixes ind?x?s qui peuvent ?tre vus dans la charte entre l'Attributs 8822 et l'Attribut 8703. Ces attributs sont utilis?es habituellement comme limitation. Les attibuts pour les champs fixes repr?sente aujourd'hui les codes BK. D'autres codes, si n?cessaires, peuvent ?tre d?finis. >
> >
> - Basic Searching > + Recherche simple > > - The search box that library staff and library patrons will see > - most often is the persistent search box at the top of the page. Koha > - interprets the searches as keyword searches. > + Le champ de recherche que les biblioth?caires et les usager verront le plus souvent est le champ persistant de recherche simple en haut de la page. Koha interpr?te les recherches ? partir de ce champ comme une recherche par mot-cl?s. > > > Koha search box > @@ -29726,22 +30565,11 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype > > > > - To start a search, you enter a word or multiple words in the > - search box. When a single word is entered, a keyword search is > - performed. You can check this out by typing one word into the form and > - note the number of results located. Then, repeat the search with a > - minor change. In front of the search word, type 'kw=' followed by the > - same search term. The results will be identical. > + Pour faire une recherche, entrez un ou plusieurs mots dans le champ de recherche simple. Quand un seul mot est entr?, une recherche par mot-cl?s est lanc?e. Vous pouvez le constater en lanceant une recherche sur un seul terme et noter le nombre de r?sultats trouv?s. Ensuite, r?p?tez la recherche mais cette fois avec un nouvel ?l?ment. Devant le terme de recherche, ajoutez 'kw=' suivi par le terme de recherche. Vous verrez que le nombre de r?sultat est identique. > > - When you have more than one word in the search box, Koha will > - still do a keyword search, but a bit differently. Each word will be > - searched on its own, then the Boolean connector 'and' will narrow your > - search to those items with all words contained in matching > - records. > + Quand vous avez plus d'une terme de recherche, Koha effectue toujours une recherche par mot-cl?s, mais celle ci est l?g?rement diff?rente. Chaque terme est recherch? ind?pendamment les uns des autres, et ensuite, l'op?rateur bool?en 'and' limite la recherche aux notices qui contiennent tous les termes recherch?s. > > - Suppose you want to find material about how libraries are using > - mashups. You'll select the major words and enter them into the > - persistent search box. > + Supposons que vous souhaitez trouver de la documentation sur la fa?on dont les biblioth?ques utilisent des 'mashups'. Vous allez selectionner les termes importants et les saisir dans le champ de recherche simple. > > > Keyword Search > @@ -29753,7 +30581,7 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype > > > > - The response to this search is: > + La r?ponse ? cette recherche est: > > > Results > @@ -29765,9 +30593,7 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype > > > > - The order of the words does not affect the retrieval results, so > - you could also enter the search as "mashups library". The response to > - this search is results > + L'ordre des termes de recherche n'affecte pas le tri des r?sultats, donc vous pouvez saisir la recherche suivante "mashups library". La r?ponse ? cette recherche est : > > > Results > @@ -29779,8 +30605,7 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype > > > > - Too many words in the search box will find very few matches, as > - the following example illustrates: > + Trop de termes dans le champ de recherche am?ne peu de r?sultats, comme l'illustre l'exemple suivant : > > > No results found > @@ -29794,11 +30619,9 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype >
> >
> - Advanced Searching > + Recherche avanc?e > > - When you can't find the most appropriate material with a general > - search, you can move to the Advanced Search page by clicking on the > - Search option on the persistent toolbar. > + Quand vous ne trouvez pas de r?sultats qui vous conviennent avec la recherche simple, vous pouvez utiliser le formulaire de recherche avanc?e en cliquant sur le lien 'recherche avanc?e' sous le champ de recherche simple. > > > Koha Menu > @@ -29810,22 +30633,14 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype > > > > - The Advanced Search page offers many ways to limit the results > - of your search. You can search using the Boolean operators AND, OR, > - and NOT; limit by item type; limit by year and language; limit by > - subtypes audience, content, format, or additional content types; by > - location and by availability. > + Le formulaire de recherche avanc?e offre plusieurs limitations de recherche. Vous pouvez utiliser les op?rateurs bool?en ET, OU, SAUF; limiter par type de document, limiter par ann?e et langue, limiter par les donn?es cod?es : audience, contenu, format ou type de contenu; limiter par localisation et disponibilit?. > > - The first limiting section on the Advanced Search page provides > - a quick and simple way to use the Boolean operators in your search. > - Note that this display depends on a system preference setting. This > - option can be found on the Administration > System Preferences > > - Searching page. The option called - linkend="expandedSearchOption">expandedSearchOption must be set > - to 'show' to see the following display. > + La premi?re section de limitation dans le formulaire de recherche avanc?e permet une utilisation rapide et simple des op?rateurs bool?en dans la recherche. Notez que cette affichage d?pend d'un param?trage dans vos pr?f?rences syst?me.T Cette option peut ?tre trouv?e dans Administration > Pr?f?rences syst?me > > + Formulaire de recherche. L'option appel?e + linkend="expandedSearchOption">expandedSearchOption doit ?tre configur? ? 'montrer' pour voir l'affichage suivant. > > > - Advanced Search Options > + Options de la recherche avanc?e > > > > @@ -29834,16 +30649,9 @@ location: [STAFF, ISO]Bloquera les exemplaires avec un itype > > > > - In this section you can choose among the many indexes by > - clicking on the arrow in the first box. The blank box that follows is > - where you enter your first search term or terms. On the second line, > - you can choose the Boolean operator you want to use in your search. > - The options are 'and', 'or', and 'not'. Then, you would again choose > - the index to search, followed by the second term or terms. If you have > - more concepts you want to include in your search, you can click the > - [+] to add another line for your search. > + Dans cette section, vous pouvez choisir parmis plusieurs index en cliquant sur les fl?ches dans le premier menu d?roulant. Le champ qui suit ce menu correspond au champ dans lequel vous allez entrer votre recherche. Sur la ligne suivante, vous pouvez choisir l'op?rateur Bool?en que vous souhaitez utiliser dans votre recherche. Les options sont 'et', 'ou', 'sauf'. Ensuite, vous pouvez de nouveau choisir un index et saisir un ou plusieurs termes de recherche. Si vous avez plusieurs concepts ? saisir dans votre recherche, vous pouvez cliquer sur les [+] pour ajouter une nouvelle ligne de recherche. > > - A sample search is shown next, followed by its results: > + Ci dessous, un exemple de recherche, suivi par ses r?sultats: > > > Advanced Search > @@ -33885,6 +34693,21 @@ print theme('pages_catalog'); > Frequency suggestion: daily >
> > +
> + Unsuspend Holds > + > + Script path: > + misc/cronjobs/holds/auto_unsuspend_holds.pl > + > + Does: This script checks to find holds that should no longer > + be suspended and removes the suspension if the + linkend="AutoResumeSuspendedHolds">AutoResumeSuspendedHolds > + preference is set to 'allow'. This puts the patron back in to the > + queue where they were when the hold was suspended. > + > + Frequency suggestion: daily > +
> + >
> Fines > > -- > 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 karamqubsi at gmail.com Wed Jul 11 21:03:39 2012 From: karamqubsi at gmail.com (Karam Qubsi) Date: Wed, 11 Jul 2012 22:03:39 +0300 Subject: [Koha-docs] Arabic manual 38 Message-ID: Hi first I'm so sorry if I bother you with my questions. I have try to translate some parts in the manual of koha 3.8 , and I finish editing some section in the first chapter 1. Administration 1. Global System Preferences 1.1. Acquisitions 100% 1.2. Administration 20% with images from the English version ( I will later update images from the Arabic version ) so , I want to test my work in the web , and see if my work will look good in the manual web site and I don't have experience about if I have to do some thing with my xml file to make the html result goes from right to left , or this will be done automatically ? and I want to ask , If I have to start work in the koha 3.10 (better ) or working in koha 3.8 now (as what I'm doing) , and in the future we can update the changes and make it fit the koha 3.10 . I wish you will batch my file as soon ad you can to see it i'm sorry if i have to do something else to do batches so please guide me to the correct way I know that not every one can send batches using git , so I attach the file here :) and thanks for your helps :) Thank you for your patience -- Karam Qubsi Koha Arab Translating Team http://koha.wikibrary.org/ Wikibrary for Arab Librarians http://wikibrary.org -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: manual.xml Type: text/xml Size: 1364319 bytes Desc: not available URL: From nengard at gmail.com Wed Jul 11 21:52:08 2012 From: nengard at gmail.com (Nicole Engard) Date: Wed, 11 Jul 2012 15:52:08 -0400 Subject: [Koha-docs] Arabic manual 38 In-Reply-To: References: Message-ID: I need to check with someone about the script we use to convert XML to HTML ... I don't know the way it works or if it will work for your purposes. If anyone else on the list knows the answer I'd love to hear it. Nicole On Wed, Jul 11, 2012 at 3:03 PM, Karam Qubsi wrote: > Hi > first I'm so sorry if I bother you with my questions. > > I have try to translate some parts in the manual of koha 3.8 , and I finish > editing some section in the first chapter > > 1. Administration > 1. Global System Preferences > 1.1. Acquisitions 100% > 1.2. Administration 20% > > with images from the English version ( I will later update images from the > Arabic version ) > > so , I want to test my work in the web , and see if my work will look good > in the manual web site > > and I don't have experience about if I have to do some thing with my xml > file to make the html result goes from right to left , or this will be done > automatically ? > > and I want to ask , If I have to start work in the koha 3.10 (better ) or > working in koha 3.8 now (as what I'm doing) , and in the future we can > update the changes and make it fit the koha 3.10 . > > I wish you will batch my file as soon ad you can to see it > > i'm sorry if i have to do something else to do batches so please guide me to > the correct way > > I know that not every one can send batches using git , so I attach the file > here :) > > and thanks for your helps :) > Thank you for your patience > > > > -- > Karam Qubsi > Koha Arab Translating Team > http://koha.wikibrary.org/ > Wikibrary for Arab Librarians > http://wikibrary.org > From nengard at gmail.com Thu Jul 12 21:48:17 2012 From: nengard at gmail.com (Nicole Engard) Date: Thu, 12 Jul 2012 15:48:17 -0400 Subject: [Koha-docs] Arabic manual 38 In-Reply-To: References: Message-ID: Here's how it converted in 3.2 (http://manual.koha-community.org/3.2/ar/) does that look right? If so then your 3.8 manual should be A-OK. If you need to see the 3.2 manual it's in git. Nicole On Wed, Jul 11, 2012 at 3:52 PM, Nicole Engard wrote: > I need to check with someone about the script we use to convert XML to > HTML ... I don't know the way it works or if it will work for your > purposes. If anyone else on the list knows the answer I'd love to hear > it. > > Nicole > > On Wed, Jul 11, 2012 at 3:03 PM, Karam Qubsi wrote: >> Hi >> first I'm so sorry if I bother you with my questions. >> >> I have try to translate some parts in the manual of koha 3.8 , and I finish >> editing some section in the first chapter >> >> 1. Administration >> 1. Global System Preferences >> 1.1. Acquisitions 100% >> 1.2. Administration 20% >> >> with images from the English version ( I will later update images from the >> Arabic version ) >> >> so , I want to test my work in the web , and see if my work will look good >> in the manual web site >> >> and I don't have experience about if I have to do some thing with my xml >> file to make the html result goes from right to left , or this will be done >> automatically ? >> >> and I want to ask , If I have to start work in the koha 3.10 (better ) or >> working in koha 3.8 now (as what I'm doing) , and in the future we can >> update the changes and make it fit the koha 3.10 . >> >> I wish you will batch my file as soon ad you can to see it >> >> i'm sorry if i have to do something else to do batches so please guide me to >> the correct way >> >> I know that not every one can send batches using git , so I attach the file >> here :) >> >> and thanks for your helps :) >> Thank you for your patience >> >> >> >> -- >> Karam Qubsi >> Koha Arab Translating Team >> http://koha.wikibrary.org/ >> Wikibrary for Arab Librarians >> http://wikibrary.org >> From karamqubsi at gmail.com Fri Jul 13 06:16:08 2012 From: karamqubsi at gmail.com (Karam Qubsi) Date: Fri, 13 Jul 2012 07:16:08 +0300 Subject: [Koha-docs] Arabic manual 38 In-Reply-To: References: Message-ID: Hi all Thanks Nicole I test it locally and it looks good , and i found the way to convert it to html :) (and to po) but I'm puzzled a little where is the best to start ? in translating the 3.8 manual ( because it is maybe stable more than 3.10) or work in 3.10 to make the next koha version full in Arabic (manuals and system) so please advice . and one more point , I've found a tool that convert (docbook) format to po and we can translate it from there it is more easy to translate If there is flaws in this solution please let me know. *the attached file* is the po generated from the manaul.xml (for 3.10) and it could be re convert to xml after translation I used the gnome-doc-utils https://live.gnome.org/GnomeDocUtils/ "It includes xml2po tool which makes it easier to translate and keep up to date translations of documentation" Hi Fr?d?ric :) Can we use the Pootle Server to translate manuals ? as a new project (not just for arabic ) I think to make koha more translatable we need to provide easy way to translate the system and the manuals I think the translator who used to translate in Pootle will find this more easier to translate the documentation I wish you all happy times On Thu, Jul 12, 2012 at 10:48 PM, Nicole Engard wrote: > Here's how it converted in 3.2 > (http://manual.koha-community.org/3.2/ar/) does that look right? If so > then your 3.8 manual should be A-OK. If you need to see the 3.2 manual > it's in git. > > Nicole > > On Wed, Jul 11, 2012 at 3:52 PM, Nicole Engard wrote: > > I need to check with someone about the script we use to convert XML to > > HTML ... I don't know the way it works or if it will work for your > > purposes. If anyone else on the list knows the answer I'd love to hear > > it. > > > > Nicole > > > > On Wed, Jul 11, 2012 at 3:03 PM, Karam Qubsi > wrote: > >> Hi > >> first I'm so sorry if I bother you with my questions. > >> > >> I have try to translate some parts in the manual of koha 3.8 , and I > finish > >> editing some section in the first chapter > >> > >> 1. Administration > >> 1. Global System Preferences > >> 1.1. Acquisitions 100% > >> 1.2. Administration 20% > >> > >> with images from the English version ( I will later update images from > the > >> Arabic version ) > >> > >> so , I want to test my work in the web , and see if my work will look > good > >> in the manual web site > >> > >> and I don't have experience about if I have to do some thing with my xml > >> file to make the html result goes from right to left , or this will be > done > >> automatically ? > >> > >> and I want to ask , If I have to start work in the koha 3.10 (better ) > or > >> working in koha 3.8 now (as what I'm doing) , and in the future we can > >> update the changes and make it fit the koha 3.10 . > >> > >> I wish you will batch my file as soon ad you can to see it > >> > >> i'm sorry if i have to do something else to do batches so please guide > me to > >> the correct way > >> > >> I know that not every one can send batches using git , so I attach the > file > >> here :) > >> > >> and thanks for your helps :) > >> Thank you for your patience > >> > >> > >> > >> -- > >> Karam Qubsi > >> Koha Arab Translating Team > >> http://koha.wikibrary.org/ > >> Wikibrary for Arab Librarians > >> http://wikibrary.org > >> > -- Karam Qubsi Koha Arab Translating Team http://koha.wikibrary.org/ Wikibrary for Arab Librarians http://wikibrary.org -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: manual.po Type: application/octet-stream Size: 1177901 bytes Desc: not available URL: From nengard at gmail.com Fri Jul 13 16:21:04 2012 From: nengard at gmail.com (Nicole Engard) Date: Fri, 13 Jul 2012 10:21:04 -0400 Subject: [Koha-docs] Arabic manual 38 In-Reply-To: References: Message-ID: I don't know anything about po - all I know is that the manual is in Docbook and when I push changes to it those are converted to HTML with a script on the server for display. If another set up is necessary, we'll need to discuss hat that requires. For me the best place to start in the 3.8 manual and submit patches to the docbook file to me via this list. Then once you have the 3.8 manual translated you can use that as the base for the 3.10 manual (at least that's what I do). Nicole On Fri, Jul 13, 2012 at 12:16 AM, Karam Qubsi wrote: > Hi all > > Thanks Nicole > I test it locally and it looks good , and i found the way to convert it to > html :) (and to po) > > but I'm puzzled a little > > where is the best to start ? > in translating the 3.8 manual ( because it is maybe stable more than 3.10) > > or work in 3.10 to make the next koha version full in Arabic (manuals and > system) > > so please advice . > > and one more point , I've found a tool that convert (docbook) format to po > and we can translate it from there > > it is more easy to translate > > If there is flaws in this solution please let me know. > > the attached file is the po generated from the manaul.xml (for 3.10) > and it could be re convert to xml after translation > > I used the gnome-doc-utils > https://live.gnome.org/GnomeDocUtils/ > > "It includes xml2po tool which makes it easier to translate and keep up to > date translations of documentation" > > Hi Fr?d?ric :) > > Can we use the Pootle Server to translate manuals ? as a new project (not > just for arabic ) > > I think to make koha more translatable we need to provide easy way to > translate the system and the manuals > I think the translator who used to translate in Pootle will find this more > easier to translate the documentation > > I wish you all happy times > > > > > > > > > On Thu, Jul 12, 2012 at 10:48 PM, Nicole Engard wrote: >> >> Here's how it converted in 3.2 >> (http://manual.koha-community.org/3.2/ar/) does that look right? If so >> then your 3.8 manual should be A-OK. If you need to see the 3.2 manual >> it's in git. >> >> Nicole >> >> On Wed, Jul 11, 2012 at 3:52 PM, Nicole Engard wrote: >> > I need to check with someone about the script we use to convert XML to >> > HTML ... I don't know the way it works or if it will work for your >> > purposes. If anyone else on the list knows the answer I'd love to hear >> > it. >> > >> > Nicole >> > >> > On Wed, Jul 11, 2012 at 3:03 PM, Karam Qubsi >> > wrote: >> >> Hi >> >> first I'm so sorry if I bother you with my questions. >> >> >> >> I have try to translate some parts in the manual of koha 3.8 , and I >> >> finish >> >> editing some section in the first chapter >> >> >> >> 1. Administration >> >> 1. Global System Preferences >> >> 1.1. Acquisitions 100% >> >> 1.2. Administration 20% >> >> >> >> with images from the English version ( I will later update images from >> >> the >> >> Arabic version ) >> >> >> >> so , I want to test my work in the web , and see if my work will look >> >> good >> >> in the manual web site >> >> >> >> and I don't have experience about if I have to do some thing with my >> >> xml >> >> file to make the html result goes from right to left , or this will be >> >> done >> >> automatically ? >> >> >> >> and I want to ask , If I have to start work in the koha 3.10 (better ) >> >> or >> >> working in koha 3.8 now (as what I'm doing) , and in the future we can >> >> update the changes and make it fit the koha 3.10 . >> >> >> >> I wish you will batch my file as soon ad you can to see it >> >> >> >> i'm sorry if i have to do something else to do batches so please guide >> >> me to >> >> the correct way >> >> >> >> I know that not every one can send batches using git , so I attach the >> >> file >> >> here :) >> >> >> >> and thanks for your helps :) >> >> Thank you for your patience >> >> >> >> >> >> >> >> -- >> >> Karam Qubsi >> >> Koha Arab Translating Team >> >> http://koha.wikibrary.org/ >> >> Wikibrary for Arab Librarians >> >> http://wikibrary.org >> >> > > > > > -- > Karam Qubsi > Koha Arab Translating Team > http://koha.wikibrary.org/ > Wikibrary for Arab Librarians > http://wikibrary.org > From Katrin.Fischer at bsz-bw.de Fri Jul 13 16:36:52 2012 From: Katrin.Fischer at bsz-bw.de (Fischer, Katrin) Date: Fri, 13 Jul 2012 16:36:52 +0200 Subject: [Koha-docs] [Koha-translate] Arabic manual 38 In-Reply-To: References: Message-ID: <028B1A54D03E7B4482CDCA4EC8F06BFD0221E0E8@Bodensee.bsz-bw.de> I think the idea of having po files for translating the manual is an interesting idea - because it means that when Nicole updates the manual, not the whole manual will have to be retranslated, but only the changed parts of it. If we keep the image names the same for each language, we could also have "translated" screenshots for each language. Git allows to see what has changed in the English manual between versions, but those changes are not reflected in the translated manuals. If someone wants to do a 1:1 translation, using po files make a lot of sense and it would lower the barrier for translating the manuals. Katrin > -----Original Message----- > From: koha-translate-bounces at lists.koha-community.org [mailto:koha- > translate-bounces at lists.koha-community.org] On Behalf Of Nicole Engard > Sent: Friday, July 13, 2012 4:21 PM > To: Karam Qubsi > Cc: Larry Baerveldt; Fr?d?ric Demians; koha.ILS at groups.facebook.com; > koha-docs at lists.koha-community.org; koha-translate at lists.koha- > community.org > Subject: Re: [Koha-translate] Arabic manual 38 > > I don't know anything about po - all I know is that the manual is in > Docbook and when I push changes to it those are converted to HTML with a > script on the server for display. If another set up is necessary, we'll > need to discuss hat that requires. > > For me the best place to start in the 3.8 manual and submit patches to > the docbook file to me via this list. Then once you have the 3.8 manual > translated you can use that as the base for the 3.10 manual (at least > that's what I do). > > Nicole > > On Fri, Jul 13, 2012 at 12:16 AM, Karam Qubsi > wrote: > > Hi all > > > > Thanks Nicole > > I test it locally and it looks good , and i found the way to convert > > it to html :) (and to po) > > > > but I'm puzzled a little > > > > where is the best to start ? > > in translating the 3.8 manual ( because it is maybe stable more than > > 3.10) > > > > or work in 3.10 to make the next koha version full in Arabic (manuals > > and > > system) > > > > so please advice . > > > > and one more point , I've found a tool that convert (docbook) format > > to po and we can translate it from there > > > > it is more easy to translate > > > > If there is flaws in this solution please let me know. > > > > the attached file is the po generated from the manaul.xml (for 3.10) > > and it could be re convert to xml after translation > > > > I used the gnome-doc-utils > > https://live.gnome.org/GnomeDocUtils/ > > > > "It includes xml2po tool which makes it easier to translate and keep > > up to date translations of documentation" > > > > Hi Fr?d?ric :) > > > > Can we use the Pootle Server to translate manuals ? as a new project > > (not just for arabic ) > > > > I think to make koha more translatable we need to provide easy way to > > translate the system and the manuals I think the translator who used > > to translate in Pootle will find this more easier to translate the > > documentation > > > > I wish you all happy times > > > > > > > > > > > > > > > > > > On Thu, Jul 12, 2012 at 10:48 PM, Nicole Engard > wrote: > >> > >> Here's how it converted in 3.2 > >> (http://manual.koha-community.org/3.2/ar/) does that look right? If > >> so then your 3.8 manual should be A-OK. If you need to see the 3.2 > >> manual it's in git. > >> > >> Nicole > >> > >> On Wed, Jul 11, 2012 at 3:52 PM, Nicole Engard > wrote: > >> > I need to check with someone about the script we use to convert XML > >> > to HTML ... I don't know the way it works or if it will work for > >> > your purposes. If anyone else on the list knows the answer I'd love > >> > to hear it. > >> > > >> > Nicole > >> > > >> > On Wed, Jul 11, 2012 at 3:03 PM, Karam Qubsi > >> > wrote: > >> >> Hi > >> >> first I'm so sorry if I bother you with my questions. > >> >> > >> >> I have try to translate some parts in the manual of koha 3.8 , and > >> >> I finish editing some section in the first chapter > >> >> > >> >> 1. Administration > >> >> 1. Global System Preferences > >> >> 1.1. Acquisitions 100% > >> >> 1.2. Administration 20% > >> >> > >> >> with images from the English version ( I will later update images > >> >> from the Arabic version ) > >> >> > >> >> so , I want to test my work in the web , and see if my work will > >> >> look good in the manual web site > >> >> > >> >> and I don't have experience about if I have to do some thing with > >> >> my xml file to make the html result goes from right to left , or > >> >> this will be done automatically ? > >> >> > >> >> and I want to ask , If I have to start work in the koha 3.10 > >> >> (better ) or working in koha 3.8 now (as what I'm doing) , and in > >> >> the future we can update the changes and make it fit the koha 3.10 > >> >> . > >> >> > >> >> I wish you will batch my file as soon ad you can to see it > >> >> > >> >> i'm sorry if i have to do something else to do batches so please > >> >> guide me to the correct way > >> >> > >> >> I know that not every one can send batches using git , so I attach > >> >> the file here :) > >> >> > >> >> and thanks for your helps :) > >> >> Thank you for your patience > >> >> > >> >> > >> >> > >> >> -- > >> >> Karam Qubsi > >> >> Koha Arab Translating Team > >> >> http://koha.wikibrary.org/ > >> >> Wikibrary for Arab Librarians > >> >> http://wikibrary.org > >> >> > > > > > > > > > > -- > > Karam Qubsi > > Koha Arab Translating Team > > http://koha.wikibrary.org/ > > Wikibrary for Arab Librarians > > http://wikibrary.org > > > _______________________________________________ > Koha-translate mailing list > Koha-translate at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate > website: www.koha-community.org > git: git.koha-community.org > bugs: bugs.koha-community.org From jcamins at cpbibliography.com Sat Jul 14 18:20:49 2012 From: jcamins at cpbibliography.com (Jared Camins-Esakov) Date: Sat, 14 Jul 2012 12:20:49 -0400 Subject: [Koha-docs] [Koha-translate] Arabic manual 38 In-Reply-To: <028B1A54D03E7B4482CDCA4EC8F06BFD0221E0E8@Bodensee.bsz-bw.de> References: <028B1A54D03E7B4482CDCA4EC8F06BFD0221E0E8@Bodensee.bsz-bw.de> Message-ID: > > I think the idea of having po files for translating the manual is an > interesting idea - because it means that when Nicole updates the manual, > not the whole manual will have to be retranslated, but only the changed > parts of it. If we keep the image names the same for each language, we > could also have "translated" screenshots for each language. > > Git allows to see what has changed in the English manual between versions, > but those changes are not reflected in the translated manuals. > > If someone wants to do a 1:1 translation, using po files make a lot of > sense and it would lower the barrier for translating the manuals. > Agreed. This is a fantastic idea. Generating a po file from Docbook (and vice versa) is easy, and for 1:1 translations would be a great help. I think it would be much better to merge the translated Docbook into the git repository prior to releases, the way we do with Koha, rather than asking the translation teams to rewrite the manual every time something is pushed to the English. Regards, Jared -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins at cpbibliography.com (web) http://www.cpbibliography.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From dear.shari at gmail.com Sat Jul 14 22:40:12 2012 From: dear.shari at gmail.com (Shari Perkins) Date: Sat, 14 Jul 2012 16:40:12 -0400 Subject: [Koha-docs] Copyedits to Acquisition Section Message-ID: Hello! I've started incorporating the changes I made to the help files into the manual. Please find the first patch attached to this email. Shari Perkins -- Shari Perkins Dramaturg (cell) 917-880-9146 (email) dear.shari at gmail.com (web) http://www.shariperkins.com -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Copyedited-Acquisitions.patch Type: application/octet-stream Size: 1883900 bytes Desc: not available URL: From nengard at gmail.com Sat Jul 14 23:06:10 2012 From: nengard at gmail.com (Nicole Engard) Date: Sat, 14 Jul 2012 17:06:10 -0400 Subject: [Koha-docs] Copyedits to Acquisition Section In-Reply-To: References: Message-ID: I need to know what version of the manual to apply this patch to. 3.6? 3.8? 3.10? Nicole On Sat, Jul 14, 2012 at 4:40 PM, Shari Perkins wrote: > Hello! > > I've started incorporating the changes I made to the help files into > the manual. Please find the first patch attached to this email. > > Shari Perkins > > -- > Shari Perkins > Dramaturg > (cell) 917-880-9146 > (email) dear.shari at gmail.com > (web) http://www.shariperkins.com > > _______________________________________________ > Koha-docs mailing list > Koha-docs at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-docs > From dear.shari at gmail.com Sat Jul 14 23:07:12 2012 From: dear.shari at gmail.com (Shari Perkins) Date: Sat, 14 Jul 2012 17:07:12 -0400 Subject: [Koha-docs] Copyedits to Acquisition Section In-Reply-To: References: Message-ID: I wrote the patch against master. On Sat, Jul 14, 2012 at 5:06 PM, Nicole Engard wrote: > I need to know what version of the manual to apply this patch to. > 3.6? 3.8? 3.10? > > Nicole > > On Sat, Jul 14, 2012 at 4:40 PM, Shari Perkins wrote: >> Hello! >> >> I've started incorporating the changes I made to the help files into >> the manual. Please find the first patch attached to this email. >> >> Shari Perkins >> >> -- >> Shari Perkins >> Dramaturg >> (cell) 917-880-9146 >> (email) dear.shari at gmail.com >> (web) http://www.shariperkins.com >> >> _______________________________________________ >> Koha-docs mailing list >> Koha-docs at lists.koha-community.org >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-docs >> -- Shari Perkins Dramaturg (cell) 917-880-9146 (email) dear.shari at gmail.com (web) http://www.shariperkins.com From nengard at gmail.com Sun Jul 15 02:03:53 2012 From: nengard at gmail.com (Nicole Engard) Date: Sat, 14 Jul 2012 20:03:53 -0400 Subject: [Koha-docs] Copyedits to Acquisition Section In-Reply-To: References: Message-ID: Okay, patch applied, but next time try not to mess too much with the line spacing, that causes problems when other patches are applied. Which I've learned the hard way :) Nicole On Sat, Jul 14, 2012 at 5:07 PM, Shari Perkins wrote: > I wrote the patch against master. > > On Sat, Jul 14, 2012 at 5:06 PM, Nicole Engard wrote: >> I need to know what version of the manual to apply this patch to. >> 3.6? 3.8? 3.10? >> >> Nicole >> >> On Sat, Jul 14, 2012 at 4:40 PM, Shari Perkins wrote: >>> Hello! >>> >>> I've started incorporating the changes I made to the help files into >>> the manual. Please find the first patch attached to this email. >>> >>> Shari Perkins >>> >>> -- >>> Shari Perkins >>> Dramaturg >>> (cell) 917-880-9146 >>> (email) dear.shari at gmail.com >>> (web) http://www.shariperkins.com >>> >>> _______________________________________________ >>> Koha-docs mailing list >>> Koha-docs at lists.koha-community.org >>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-docs >>> > > > > -- > Shari Perkins > Dramaturg > (cell) 917-880-9146 > (email) dear.shari at gmail.com > (web) http://www.shariperkins.com From karamqubsi at gmail.com Sun Jul 15 09:17:30 2012 From: karamqubsi at gmail.com (Karam Qubsi) Date: Sun, 15 Jul 2012 10:17:30 +0300 Subject: [Koha-docs] [Koha-translate] Arabic manual 38 In-Reply-To: References: <028B1A54D03E7B4482CDCA4EC8F06BFD0221E0E8@Bodensee.bsz-bw.de> Message-ID: Hi all :) thanks for your response I wish we can apply this as soon as possible and we can try this for the Arabic language my group is ready to work :) but the Question is , where we will work ? in the same Pootle Server , or that is not available ? if that is available , I wish you upload the pot and po files to the server If you want some guidelines you can use this guide it's very useful , and very easy : http://pwet.fr/man/linux/commandes/xml2po and I wish to start work with the the 3.8 manual as Nicole advice :) Thanks ^_^ Karam On Sat, Jul 14, 2012 at 7:20 PM, Jared Camins-Esakov < jcamins at cpbibliography.com> wrote: > I think the idea of having po files for translating the manual is an >> interesting idea - because it means that when Nicole updates the manual, >> not the whole manual will have to be retranslated, but only the changed >> parts of it. If we keep the image names the same for each language, we >> could also have "translated" screenshots for each language. >> >> Git allows to see what has changed in the English manual between >> versions, but those changes are not reflected in the translated manuals. >> >> If someone wants to do a 1:1 translation, using po files make a lot of >> sense and it would lower the barrier for translating the manuals. >> > > Agreed. This is a fantastic idea. Generating a po file from Docbook (and > vice versa) is easy, and for 1:1 translations would be a great help. I > think it would be much better to merge the translated Docbook into the git > repository prior to releases, the way we do with Koha, rather than asking > the translation teams to rewrite the manual every time something is pushed > to the English. > > Regards, > Jared > > -- > Jared Camins-Esakov > Bibliographer, C & P Bibliography Services, LLC > (phone) +1 (917) 727-3445 > (e-mail) jcamins at cpbibliography.com > (web) http://www.cpbibliography.com/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From frederic at tamil.fr Sun Jul 15 12:07:33 2012 From: frederic at tamil.fr (=?ISO-8859-1?Q?Fr=E9d=E9ric_Demians?=) Date: Sun, 15 Jul 2012 12:07:33 +0200 Subject: [Koha-docs] [Koha-translate] Arabic manual 38 In-Reply-To: References: <028B1A54D03E7B4482CDCA4EC8F06BFD0221E0E8@Bodensee.bsz-bw.de> Message-ID: <50029665.1060403@tamil.fr> Hi Karam, > but the Question is , where we will work ? in the same Pootle Server , > or that is not available ? Very possible. > if that is available , I wish you upload the pot and po files to the > server If you want some guidelines you can use this guide it's very > useful , and very easy : > http://pwet.fr/man/linux/commandes/xml2po Nothing hasn't been done yet in this direction. We have to validate that this workflow just works for us, test it, and document it. Things to do (at least): - A .pot file must be generated from DocBook XML file - One, or several, .po files must be generated from .pot file - After translation, a translated XML DocBook file must be generated from .po file, and original English DocBook - After original DocBook updates, a merging mechanism must allow to update .pot file, and .po files Who will do that job? You? the documentation manager? the translation manager? From my perspective, you are the best suited to start this project since you will be the first to benefit from its results. If this workflow proves to work for you, I'm sure the community will embrace it with enthusiasm and gratitude. Kind regards, -- Fr?d?ric DEMIANS http://www.tamil.fr/u/fdemians.html From bgkriegel at gmail.com Sun Jul 15 17:47:52 2012 From: bgkriegel at gmail.com (Bernardo Gonzalez Kriegel) Date: Sun, 15 Jul 2012 12:47:52 -0300 Subject: [Koha-docs] [Koha-translate] Arabic manual 38 In-Reply-To: References: <028B1A54D03E7B4482CDCA4EC8F06BFD0221E0E8@Bodensee.bsz-bw.de> Message-ID: > > I think the idea of having po files for translating the manual is an >> interesting idea - because it means that when Nicole updates the manual, >> not the whole manual will have to be retranslated, but only the changed >> parts of it. If we keep the image names the same for each language, we >> could also have "translated" screenshots for each language. >> >> Git allows to see what has changed in the English manual between >> versions, but those changes are not reflected in the translated manuals. >> >> If someone wants to do a 1:1 translation, using po files make a lot of >> sense and it would lower the barrier for translating the manuals. >> > > Agreed. This is a fantastic idea. Generating a po file from Docbook (and > vice versa) is easy, and for 1:1 translations would be a great help. I > think it would be much better to merge the translated Docbook into the git > repository prior to releases, the way we do with Koha, rather than asking > the translation teams to rewrite the manual every time something is pushed > to the English. > I wrote a while ago (26-3-2010) on the same topic to Chris Cormak (he was translation manager, I think) ... I've been working on the translation of the 3.2 manual from some time, not too much lately because we are finishing the migration of almost all of the libraries of our university (hope we will finish in a month), but we plan to complete the translation eventually. Thanks to Nicole, the manual is a living thing and she does a great job, but every time she makes a change or adds something we are out of sync, then we need to search were in the english version she has made a change, and do the translation. The question is: Is it possible to apply to the manual the same procedure we have with the koha code? I mean, some procedure to generate a PO file from the manual, translate it and then generate the corresponding translated manual. Every time the English manual changes, then the PO file will have new, changed or deprecated strings, easier to found using pootle or poedit. ... It would be wonderful if this could be implemented. Bernardo -------------- next part -------------- An HTML attachment was scrubbed... URL: From karamqubsi at gmail.com Mon Jul 16 08:36:32 2012 From: karamqubsi at gmail.com (Karam Qubsi) Date: Mon, 16 Jul 2012 09:36:32 +0300 Subject: [Koha-docs] [Koha-translate] Arabic manual 38 In-Reply-To: <50029665.1060403@tamil.fr> References: <028B1A54D03E7B4482CDCA4EC8F06BFD0221E0E8@Bodensee.bsz-bw.de> <50029665.1060403@tamil.fr> Message-ID: Hi Fr?d?ric , OK I will start with this by generating the 3.8 .pot file and the .po (for Arabic right now to test ) and will give you feedback about this :) Karam On Sun, Jul 15, 2012 at 1:07 PM, Fr?d?ric Demians wrote: > Hi Karam, > > > > but the Question is , where we will work ? in the same Pootle Server , > > or that is not available ? > > Very possible. > > > > if that is available , I wish you upload the pot and po files to the > > server If you want some guidelines you can use this guide it's very > > useful , and very easy : > > > http://pwet.fr/man/linux/**commandes/xml2po > > Nothing hasn't been done yet in this direction. We have to validate that > this workflow just works for us, test it, and document it. Things to do > (at least): > > - A .pot file must be generated from DocBook XML file > - One, or several, .po files must be generated from .pot file > - After translation, a translated XML DocBook file must be generated > from .po file, and original English DocBook > - After original DocBook updates, a merging mechanism must allow to > update .pot file, and .po files > > Who will do that job? You? the documentation manager? the translation > manager? From my perspective, you are the best suited to start this > project since you will be the first to benefit from its results. If this > workflow proves to work for you, I'm sure the community will embrace it > with enthusiasm and gratitude. > > Kind regards, > -- > Fr?d?ric DEMIANS > http://www.tamil.fr/u/**fdemians.html > -- Karam Qubsi Koha Arab Translating Team http://koha.wikibrary.org/ Wikibrary for Arab Librarians http://wikibrary.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From Katrin.Fischer at bsz-bw.de Mon Jul 16 08:55:58 2012 From: Katrin.Fischer at bsz-bw.de (Fischer, Katrin) Date: Mon, 16 Jul 2012 08:55:58 +0200 Subject: [Koha-docs] [Koha-translate] Arabic manual 38 In-Reply-To: References: <028B1A54D03E7B4482CDCA4EC8F06BFD0221E0E8@Bodensee.bsz-bw.de><50029665.1060403@tamil.fr> Message-ID: <028B1A54D03E7B4482CDCA4EC8F06BFD0221E124@Bodensee.bsz-bw.de> Hi Karam, thank you for your work on this. I hope it works out and we can make this available for other languages soon too :) Katrin From: Karam Qubsi [mailto:karamqubsi at gmail.com] Sent: Monday, July 16, 2012 8:37 AM To: Fr?d?ric Demians Cc: Jared Camins-Esakov; Fischer, Katrin; koha-docs at lists.koha-community.org; koha-translate at lists.koha-community.org; Nicole Engard Subject: Re: [Koha-translate] Arabic manual 38 Hi Fr?d?ric , OK I will start with this by generating the 3.8 .pot file and the .po (for Arabic right now to test ) and will give you feedback about this :) Karam On Sun, Jul 15, 2012 at 1:07 PM, Fr?d?ric Demians wrote: Hi Karam, > but the Question is , where we will work ? in the same Pootle Server , > or that is not available ? Very possible. > if that is available , I wish you upload the pot and po files to the > server If you want some guidelines you can use this guide it's very > useful , and very easy : > http://pwet.fr/man/linux/commandes/xml2po Nothing hasn't been done yet in this direction. We have to validate that this workflow just works for us, test it, and document it. Things to do (at least): - A .pot file must be generated from DocBook XML file - One, or several, .po files must be generated from .pot file - After translation, a translated XML DocBook file must be generated ? from .po file, and original English DocBook - After original DocBook updates, a merging mechanism must allow to ? update .pot file, and .po files Who will do that job? You? the documentation manager? the translation manager? ?From my perspective, you are the best suited to start this project since you will be the first to benefit from its results. If this workflow proves to work for you, I'm sure the community will embrace it with enthusiasm and gratitude. Kind regards, -- Fr?d?ric DEMIANS http://www.tamil.fr/u/fdemians.html -- Karam Qubsi Koha Arab Translating Team http://koha.wikibrary.org/ Wikibrary for Arab Librarians http://wikibrary.org From gaetan.boisson at biblibre.com Mon Jul 16 09:17:32 2012 From: gaetan.boisson at biblibre.com (Gaetan Boisson) Date: Mon, 16 Jul 2012 09:17:32 +0200 Subject: [Koha-docs] [Koha-translate] Arabic manual 38 In-Reply-To: References: <028B1A54D03E7B4482CDCA4EC8F06BFD0221E0E8@Bodensee.bsz-bw.de> <50029665.1060403@tamil.fr> Message-ID: <1342423052.2480.5.camel@Asmara> As many have said already, this really is a great idea, and i'm looking forward to seeing this live ! I know quite a few librarians who will be more than happy to contribute to the manual translation... On question : will this handle bold and emphasized sections differently than for the koha interface ? It is quite often a problem for translators when a single word is bold in a sentence in the interface, because the translation system then splits the sentence around the bold part. For the translator these 3 bits will appear separated from each other, and sometimes it will cause bad translations as we are translating single words out of their context. Anyway, truly this sounds like a great plan. Thanks Karam ! Gaetan Le lundi 16 juillet 2012 ? 09:36 +0300, Karam Qubsi a ?crit : > Hi Fr?d?ric , > > OK > I will start with this > > by generating the 3.8 .pot file and the .po (for Arabic right now to > test ) > > and will give you feedback about this :) > > Karam > > On Sun, Jul 15, 2012 at 1:07 PM, Fr?d?ric Demians > wrote: > Hi Karam, > > > > but the Question is , where we will work ? in the same > Pootle Server , > > or that is not available ? > > > Very possible. > > > > if that is available , I wish you upload the pot and po > files to the > > server If you want some guidelines you can use this guide > it's very > > useful , and very easy : > > > http://pwet.fr/man/linux/commandes/xml2po > > > Nothing hasn't been done yet in this direction. We have to > validate that > this workflow just works for us, test it, and document it. > Things to do > (at least): > > - A .pot file must be generated from DocBook XML file > - One, or several, .po files must be generated from .pot file > - After translation, a translated XML DocBook file must be > generated > from .po file, and original English DocBook > - After original DocBook updates, a merging mechanism must > allow to > update .pot file, and .po files > > Who will do that job? You? the documentation manager? the > translation > manager? From my perspective, you are the best suited to > start this > project since you will be the first to benefit from its > results. If this > workflow proves to work for you, I'm sure the community will > embrace it > with enthusiasm and gratitude. > > Kind regards, > _______________________________________________ > Koha-docs mailing list > Koha-docs at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-docs > > -- Gaetan Boisson Chef de projet biblioth?caire BibLibre 06 52 42 51 29 108 avenue Breteuil 13006 Marseille gaetan.boisson at biblibre.com From karamqubsi at gmail.com Wed Jul 25 22:09:08 2012 From: karamqubsi at gmail.com (Karam Qubsi) Date: Wed, 25 Jul 2012 23:09:08 +0300 Subject: [Koha-docs] [Koha-translate] Arabic manual 38 In-Reply-To: <50029665.1060403@tamil.fr> References: <028B1A54D03E7B4482CDCA4EC8F06BFD0221E0E8@Bodensee.bsz-bw.de> <50029665.1060403@tamil.fr> Message-ID: Hi all Using "itstool" http://itstool.org we can do the following points that Fr?d?ric talked about : - A .pot file can be generated from DocBook XML file by running : itstool -o manual.pot manual.xml - One, or several, .po files can be generated from .pot file I think by saving it as po files ar.po , fr.po , de.po .... - After translation, a translated XML DocBook file can be generated from .po file, and original English DocBook For this we have first to use *msgfmt* to generate mo file by running : msgfmt fr.po then a messages.mo will be generated using this mo file we can generate the xml file by running : itstool -m messages.mo -o fr/ manual.xml Then the translated docbook will be generated in the sub-folder /fr ( using msgmerge ) TO UPDATE - After original DocBook updates, a merging mechanism must allow to update .pot file, and .po files I think this will be similar to the process in the koha translation project I don't know how you do that exactly ( right now) but I think we have to generate a new pot file ( for the new version of the xml) and update the po files from the new POT file using : msgmerge -U fr.po manual.pot where : manual.pot is the new generated POT file and the fr.po is the translated po file in the previous version I hope you provide me with your assistance from your experience and thank you all Karam On Sun, Jul 15, 2012 at 1:07 PM, Fr?d?ric Demians wrote: > Hi Karam, > > > > but the Question is , where we will work ? in the same Pootle Server , > > or that is not available ? > > Very possible. > > > > if that is available , I wish you upload the pot and po files to the > > server If you want some guidelines you can use this guide it's very > > useful , and very easy : > > > http://pwet.fr/man/linux/**commandes/xml2po > > Nothing hasn't been done yet in this direction. We have to validate that > this workflow just works for us, test it, and document it. Things to do > (at least): > > - A .pot file must be generated from DocBook XML file > - One, or several, .po files must be generated from .pot file > - After translation, a translated XML DocBook file must be generated > from .po file, and original English DocBook > - After original DocBook updates, a merging mechanism must allow to > update .pot file, and .po files > > Who will do that job? You? the documentation manager? the translation > manager? From my perspective, you are the best suited to start this > project since you will be the first to benefit from its results. If this > workflow proves to work for you, I'm sure the community will embrace it > with enthusiasm and gratitude. > > Kind regards, > -- > Fr?d?ric DEMIANS > http://www.tamil.fr/u/**fdemians.html > -------------- next part -------------- An HTML attachment was scrubbed... URL: From karamqubsi at gmail.com Thu Jul 26 02:37:00 2012 From: karamqubsi at gmail.com (Karam Qubsi) Date: Thu, 26 Jul 2012 03:37:00 +0300 Subject: [Koha-docs] Translate KOHA Manual Message-ID: Hi All , Hi Fr?d?ric Attached with this Email a Zip file contain the pot file for the manual 3.8 with the last version that Nicole submitted and in the folder ( lang) you will find ar , fr and de po files to start with we can add other languages as you know I wish this will be added to the Pootle Server ( as a new project ) , and start translating there :) Kind regards Karam ---------- Forwarded message ---------- From: Karam Qubsi Date: Wed, Jul 25, 2012 at 11:09 PM Subject: Re: [Koha-translate] Arabic manual 38 To: Fr?d?ric Demians Cc: Jared Camins-Esakov , "Fischer, Katrin" < Katrin.Fischer at bsz-bw.de>, koha-docs at lists.koha-community.org, koha-translate at lists.koha-community.org, Nicole Engard Hi all Using "itstool" http://itstool.org we can do the following points that Fr?d?ric talked about : - A .pot file can be generated from DocBook XML file by running : itstool -o manual.pot manual.xml - One, or several, .po files can be generated from .pot file I think by saving it as po files ar.po , fr.po , de.po .... - After translation, a translated XML DocBook file can be generated from .po file, and original English DocBook For this we have first to use *msgfmt* to generate mo file by running : msgfmt fr.po then a messages.mo will be generated using this mo file we can generate the xml file by running : itstool -m messages.mo -o fr/ manual.xml Then the translated docbook will be generated in the sub-folder /fr ( using msgmerge ) TO UPDATE - After original DocBook updates, a merging mechanism must allow to update .pot file, and .po files I think this will be similar to the process in the koha translation project I don't know how you do that exactly ( right now) but I think we have to generate a new pot file ( for the new version of the xml) and update the po files from the new POT file using : msgmerge -U fr.po manual.pot where : manual.pot is the new generated POT file and the fr.po is the translated po file in the previous version I hope you provide me with your assistance from your experience and thank you all Karam On Sun, Jul 15, 2012 at 1:07 PM, Fr?d?ric Demians wrote: > Hi Karam, > > > > but the Question is , where we will work ? in the same Pootle Server , > > or that is not available ? > > Very possible. > > > > if that is available , I wish you upload the pot and po files to the > > server If you want some guidelines you can use this guide it's very > > useful , and very easy : > > > http://pwet.fr/man/linux/**commandes/xml2po > > Nothing hasn't been done yet in this direction. We have to validate that > this workflow just works for us, test it, and document it. Things to do > (at least): > > - A .pot file must be generated from DocBook XML file > - One, or several, .po files must be generated from .pot file > - After translation, a translated XML DocBook file must be generated > from .po file, and original English DocBook > - After original DocBook updates, a merging mechanism must allow to > update .pot file, and .po files > > Who will do that job? You? the documentation manager? the translation > manager? From my perspective, you are the best suited to start this > project since you will be the first to benefit from its results. If this > workflow proves to work for you, I'm sure the community will embrace it > with enthusiasm and gratitude. > > Kind regards, > -- > Fr?d?ric DEMIANS > http://www.tamil.fr/u/**fdemians.html > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: po.zip Type: application/zip Size: 1137001 bytes Desc: not available URL: From bgkriegel at gmail.com Thu Jul 26 04:09:11 2012 From: bgkriegel at gmail.com (Bernardo Gonzalez Kriegel) Date: Wed, 25 Jul 2012 23:09:11 -0300 Subject: [Koha-docs] Translate KOHA Manual In-Reply-To: References: Message-ID: On Wed, Jul 25, 2012 at 9:37 PM, Karam Qubsi wrote: > Hi All , > Hi Fr?d?ric > > Attached with this Email a Zip file contain the pot file for the manual > 3.8 with the last version that Nicole submitted > and in the folder ( lang) > you will find ar , fr and de po files to start with > > we can add other languages as you know > > I wish this will be added to the Pootle Server ( as a new project ) , and > start translating there :) > > Kind regards > > Karam > > > Karam, great job! I have already started the translation into Spanish (offline). I think this could be integrated as another file within the project for each version, starting with 3.8, but this is up to the Translation Managers of course. Regards Bernardo -- Bernardo Gonzalez Kriegel bgkriegel at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From frederic at tamil.fr Thu Jul 26 08:30:58 2012 From: frederic at tamil.fr (=?ISO-8859-1?Q?Fr=E9d=E9ric_Demians?=) Date: Thu, 26 Jul 2012 08:30:58 +0200 Subject: [Koha-docs] Translate KOHA Manual In-Reply-To: References: Message-ID: <5010E422.30805@tamil.fr> Thanks Karam! We need documentation on the whole process. We have now this page: http://wiki.koha-community.org/wiki/Editing_the_Koha_Manual This page is incomplete. We have to describe the process followed to generate the Koha Manual from DocBook XML file. And then, the process to localize the manual. I propose to work collaboratively on a new page gathering all information on the subject: http://wiki.koha-community.org/wiki/Koha_Manual Karam, you could document in Localization section the steps you followed. Few remarks: - .po file names shouldn't contains Koha version number. At the end of the day, those files will be stored in a Git repository whith branches identifying Koha version. .po files for Koha interfaces show us that embedding version number in the file name is a bad idea. - How will we deal with image files? There are a lot of screenshot. Good idea or bad idea? - We will need to write few scripts to generate the translation files. There are already somewhere (but where?) scripts to generated .pdf/.html versions of the manual. We could gather all those script in one place, directly in the Koha Manual git repository. Kind regards, -- Fr?d?ric DEMIANS http://www.tamil.fr/u/fdemians.html From nengard at gmail.com Thu Jul 26 14:24:31 2012 From: nengard at gmail.com (Nicole Engard) Date: Thu, 26 Jul 2012 08:24:31 -0400 Subject: [Koha-docs] Translate KOHA Manual In-Reply-To: <5010E422.30805@tamil.fr> References: <5010E422.30805@tamil.fr> Message-ID: On Thu, Jul 26, 2012 at 2:30 AM, Fr?d?ric Demians wrote: > I propose to work collaboratively on a new page gathering all > information on the subject: > > http://wiki.koha-community.org/wiki/Koha_Manual Why create a new page - you could just edit the existing page. Anyway, I'll add a link to the page I wrote on the new one. Nicole From laurence.lefaucheur at biblibre.com Fri Jul 27 17:43:49 2012 From: laurence.lefaucheur at biblibre.com (Laurence Lefaucheur) Date: Fri, 27 Jul 2012 17:43:49 +0200 Subject: [Koha-docs] [Koha-translate] Arabic manual 38 In-Reply-To: References: <028B1A54D03E7B4482CDCA4EC8F06BFD0221E0E8@Bodensee.bsz-bw.de> <50029665.1060403@tamil.fr> Message-ID: <5012B735.6010401@biblibre.com> 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 Le 25/07/2012 22:09, Karam Qubsi a ?crit : > Hi all > Using "itstool" > http://itstool.org > > we can do the following points that Fr?d?ric talked about : > > - A .pot file can be generated from DocBook XML file > by running : > itstool -o manual.pot manual.xml > - One, or several, .po files can be generated from .pot file > I think by saving it as po files > ar.po , fr.po , de.po .... > - After translation, a translated XML DocBook file can be generated > from .po file, and original English DocBook > > For this we have first to use *msgfmt* to generate mo file by > running : > msgfmt fr.po > then a messages.mo will be generated > using this mo file we can generate the xml file by running : > itstool -m messages.mo -o fr/ manual.xml > > Then the translated docbook will be generated in the sub-folder /fr > > > ( using msgmerge ) TO UPDATE > - After original DocBook updates, a merging mechanism must allow > to update .pot file, and .po files > > I think this will be similar to the process in the koha translation project > I don't know how you do that exactly ( right now) but I think > > we have to generate a new pot file ( for the new version of the xml) > and update the po files from the new POT file using : > msgmerge -U fr.po manual.pot > > where : > manual.pot is the new generated POT file > and the fr.po is the translated po file in the previous version > > > I hope you provide me with your assistance from your experience > > > and thank you all > > Karam > > > On Sun, Jul 15, 2012 at 1:07 PM, Fr?d?ric Demians > wrote: > > Hi Karam, > > > > but the Question is , where we will work ? in the same Pootle > Server , > > or that is not available ? > > Very possible. > > > > if that is available , I wish you upload the pot and po files to the > > server If you want some guidelines you can use this guide it's very > > useful , and very easy : > > > http://pwet.fr/man/linux/__commandes/xml2po > > > Nothing hasn't been done yet in this direction. We have to validate that > this workflow just works for us, test it, and document it. Things to do > (at least): > > - A .pot file must be generated from DocBook XML file > - One, or several, .po files must be generated from .pot file > - After translation, a translated XML DocBook file must be generated > from .po file, and original English DocBook > - After original DocBook updates, a merging mechanism must allow to > update .pot file, and .po files > > Who will do that job? You? the documentation manager? the translation > manager? From my perspective, you are the best suited to start this > project since you will be the first to benefit from its results. If this > workflow proves to work for you, I'm sure the community will embrace it > with enthusiasm and gratitude. > > Kind regards, > -- > Fr?d?ric DEMIANS > http://www.tamil.fr/u/__fdemians.html > > > > > > > > _______________________________________________ > Koha-docs mailing list > Koha-docs at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-docs -- ------------------------ 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 karamqubsi at gmail.com Fri Jul 27 20:56:28 2012 From: karamqubsi at gmail.com (Karam Qubsi) Date: Fri, 27 Jul 2012 21:56:28 +0300 Subject: [Koha-docs] [Koha-translate] Arabic manual 38 In-Reply-To: <5012B735.6010401@biblibre.com> References: <028B1A54D03E7B4482CDCA4EC8F06BFD0221E0E8@Bodensee.bsz-bw.de> <50029665.1060403@tamil.fr> <5012B735.6010401@biblibre.com> Message-ID: 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 < laurence.lefaucheur at biblibre.com> 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 > > Le 25/07/2012 22:09, Karam Qubsi a ?crit : > >> Hi all >> Using "itstool" >> http://itstool.org >> >> >> we can do the following points that Fr?d?ric talked about : >> >> - A .pot file can be generated from DocBook XML file >> by running : >> itstool -o manual.pot manual.xml >> - One, or several, .po files can be generated from .pot file >> I think by saving it as po files >> ar.po , fr.po , de.po .... >> - After translation, a translated XML DocBook file can be generated >> from .po file, and original English DocBook >> >> For this we have first to use *msgfmt* to generate mo file by >> >> running : >> msgfmt fr.po >> then a messages.mo will be generated >> using this mo file we can generate the xml file by running : >> itstool -m messages.mo -o fr/ manual.xml >> >> Then the translated docbook will be generated in the sub-folder >> /fr >> >> >> ( using msgmerge ) TO UPDATE >> - After original DocBook updates, a merging mechanism must allow >> to update .pot file, and .po files >> >> I think this will be similar to the process in the koha translation >> project >> I don't know how you do that exactly ( right now) but I think >> >> we have to generate a new pot file ( for the new version of the xml) >> and update the po files from the new POT file using : >> msgmerge -U fr.po manual.pot >> >> where : >> manual.pot is the new generated POT file >> and the fr.po is the translated po file in the previous version >> >> >> I hope you provide me with your assistance from your experience >> >> >> and thank you all >> >> Karam >> >> >> On Sun, Jul 15, 2012 at 1:07 PM, Fr?d?ric Demians > > wrote: >> >> Hi Karam, >> >> >> > but the Question is , where we will work ? in the same Pootle >> Server , >> > or that is not available ? >> >> Very possible. >> >> >> > if that is available , I wish you upload the pot and po files to >> the >> > server If you want some guidelines you can use this guide it's very >> > useful , and very easy : >> >> > http://pwet.fr/man/linux/__**commandes/xml2po >> >> >> > >> >> Nothing hasn't been done yet in this direction. We have to validate >> that >> this workflow just works for us, test it, and document it. Things to >> do >> (at least): >> >> - A .pot file must be generated from DocBook XML file >> - One, or several, .po files must be generated from .pot file >> - After translation, a translated XML DocBook file must be generated >> from .po file, and original English DocBook >> - After original DocBook updates, a merging mechanism must allow to >> update .pot file, and .po files >> >> Who will do that job? You? the documentation manager? the translation >> manager? From my perspective, you are the best suited to start this >> project since you will be the first to benefit from its results. If >> this >> workflow proves to work for you, I'm sure the community will embrace >> it >> with enthusiasm and gratitude. >> >> Kind regards, >> -- >> Fr?d?ric DEMIANS >> http://www.tamil.fr/u/__**fdemians.html >> >> > >> >> >> >> >> >> >> >> ______________________________**_________________ >> Koha-docs mailing list >> Koha-docs at lists.koha-**community.org >> https://lists.koha-community.**org/cgi-bin/mailman/listinfo/**koha-docs >> > > > -- > ------------------------ > Laurence Lefaucheur > BibLibre > solutions libres pour les biblioth?ques > http://www.biblibre.com > laurence.lefaucheur at biblibre.**com > p. 06 27 85 46 49 > > > ______________________________**_________________ > Koha-docs mailing list > Koha-docs at lists.koha-**community.org > https://lists.koha-community.**org/cgi-bin/mailman/listinfo/**koha-docs > -- Karam Qubsi Koha Arab Translating Team http://koha.wikibrary.org/ Wikibrary for Arab Librarians http://wikibrary.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From karamqubsi at gmail.com Fri Jul 27 23:23:37 2012 From: karamqubsi at gmail.com (Karam Qubsi) Date: Sat, 28 Jul 2012 00:23:37 +0300 Subject: [Koha-docs] Translate KOHA Manual In-Reply-To: <5010E422.30805@tamil.fr> References: <5010E422.30805@tamil.fr> Message-ID: Hi Fr?d?ric, I document the process that I have information about ( localization ) please review and edit this :) http://wiki.koha-community.org/wiki/Koha_Manual And I will review it again later *about images* , Hi Nicole, I think the translation team (for each lang) have to take screenshot of the Koha interface in their languages and put it in the /images folder and sup folder in in the same name and target . I think we will translate the examples that Nicole used in the documentation so we have to use the same cases and examples that she used maybe we have to take the same database that she work on . Thank you Fr?d?ric Thank you Nicole Karam On Thu, Jul 26, 2012 at 9:30 AM, Fr?d?ric Demians wrote: > Thanks Karam! > > We need documentation on the whole process. We have now this page: > > http://wiki.koha-community.**org/wiki/Editing_the_Koha_**Manual > > This page is incomplete. We have to describe the process followed to > generate the Koha Manual from DocBook XML file. And then, the process > to localize the manual. > > I propose to work collaboratively on a new page gathering all > information on the subject: > > http://wiki.koha-community.**org/wiki/Koha_Manual > > Karam, you could document in Localization section the steps you followed. > > Few remarks: > > - .po file names shouldn't contains Koha version number. At the end of > the day, those files will be stored in a Git repository whith branches > identifying Koha version. .po files for Koha interfaces show us that > embedding version number in the file name is a bad idea. > > - How will we deal with image files? There are a lot of screenshot. Good > idea or bad idea? > > - We will need to write few scripts to generate the translation files. > There are already somewhere (but where?) scripts to generated > .pdf/.html versions of the manual. We could gather all those script in > one place, directly in the Koha Manual git repository. > > > Kind regards, > -- > Fr?d?ric DEMIANS > http://www.tamil.fr/u/**fdemians.html > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bgkriegel at gmail.com Sun Jul 29 01:02:16 2012 From: bgkriegel at gmail.com (Bernardo Gonzalez Kriegel) Date: Sat, 28 Jul 2012 20:02:16 -0300 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: 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 < > laurence.lefaucheur at biblibre.com> 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 >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From nengard at gmail.com Sun Jul 29 04:45:01 2012 From: nengard at gmail.com (Nicole Engard) Date: Sat, 28 Jul 2012 22:45:01 -0400 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: On Sat, Jul 28, 2012 at 7:02 PM, Bernardo Gonzalez Kriegel wrote: > 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"). I can't do that. I did that a while back and it broke then XML to HTML converter ... or at least didn't convert anymore. So if someone wants to improve upon the script being used to generate the HTML (and maybe get it to work for PDF as well while they're at it) then maybe I can switch the encoding, but right now it has to stay the way it is if the XML is going to generate proper HTML on a nightly basis. Nicole From chrisc at catalyst.net.nz Sun Jul 29 05:49:57 2012 From: chrisc at catalyst.net.nz (Chris Cormack) Date: Sun, 29 Jul 2012 15:49:57 +1200 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: <20120729034957.GB29738@rorohiko.wgtn.cat-it.co.nz> * Nicole Engard (nengard at gmail.com) wrote: > On Sat, Jul 28, 2012 at 7:02 PM, Bernardo Gonzalez Kriegel > wrote: > > 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"). > > I can't do that. I did that a while back and it broke then XML to HTML > converter ... or at least didn't convert anymore. So if someone wants > to improve upon the script being used to generate the HTML (and maybe > get it to work for PDF as well while they're at it) then maybe I can > switch the encoding, but right now it has to stay the way it is if the > XML is going to generate proper HTML on a nightly basis. > Hmm, the master branch already is UTF-8 Nicole > _______________________________________________ > Koha-docs mailing list > Koha-docs at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-docs -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From chrisc at catalyst.net.nz Sun Jul 29 06:43:46 2012 From: chrisc at catalyst.net.nz (Chris Cormack) Date: Sun, 29 Jul 2012 16:43:46 +1200 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: <20120729044346.GC29738@rorohiko.wgtn.cat-it.co.nz> * Nicole Engard (nengard at gmail.com) wrote: > On Sat, Jul 28, 2012 at 7:02 PM, Bernardo Gonzalez Kriegel > wrote: > > 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"). > > I can't do that. I did that a while back and it broke then XML to HTML > converter ... or at least didn't convert anymore. So if someone wants > to improve upon the script being used to generate the HTML (and maybe > get it to work for PDF as well while they're at it) then maybe I can > switch the encoding, but right now it has to stay the way it is if the > XML is going to generate proper HTML on a nightly basis. > Heres xhtml I generated with xmlto http://stats.workbuffer.org/manualtest/manual.html <-- as one file Here with one file per chapter http://stats.workbuffer.org/manualtest/manual_chapters/ You can generate pdf as well % xmlto pdf --with-fop -m config.xsl en/manual.xml But as before the problem is only have web quality not print quality images, and they get stretch in the pdf. Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From nengard at gmail.com Sun Jul 29 08:28:48 2012 From: nengard at gmail.com (Nicole Engard) Date: Sun, 29 Jul 2012 02:28:48 -0400 Subject: [Koha-docs] [Koha-translate] Arabic manual 38 In-Reply-To: <20120729034957.GB29738@rorohiko.wgtn.cat-it.co.nz> References: <028B1A54D03E7B4482CDCA4EC8F06BFD0221E0E8@Bodensee.bsz-bw.de> <50029665.1060403@tamil.fr> <5012B735.6010401@biblibre.com> <20120729034957.GB29738@rorohiko.wgtn.cat-it.co.nz> Message-ID: Then I'm confused. Master is 3.8 plus more.. Encoding should be the same. Thank you, Nicole C. Engard Sent from my Android. Please excuse my brevity and typos. On Jul 28, 2012 11:50 PM, "Chris Cormack" wrote: > * Nicole Engard (nengard at gmail.com) wrote: > > On Sat, Jul 28, 2012 at 7:02 PM, Bernardo Gonzalez Kriegel > > wrote: > > > 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"). > > > > I can't do that. I did that a while back and it broke then XML to HTML > > converter ... or at least didn't convert anymore. So if someone wants > > to improve upon the script being used to generate the HTML (and maybe > > get it to work for PDF as well while they're at it) then maybe I can > > switch the encoding, but right now it has to stay the way it is if the > > XML is going to generate proper HTML on a nightly basis. > > > Hmm, the master branch already is UTF-8 > > > > > And seems to be generating ok > http://manual.koha-community.org/3.10/en/ > > Chris > > > > Nicole > > _______________________________________________ > > Koha-docs mailing list > > Koha-docs at lists.koha-community.org > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-docs > > -- > Chris Cormack > Catalyst IT Ltd. > +64 4 803 2238 > PO Box 11-053, Manners St, Wellington 6142, New Zealand > -------------- next part -------------- An HTML attachment was scrubbed... URL: From karamqubsi at gmail.com Mon Jul 30 23:47:50 2012 From: karamqubsi at gmail.com (Karam Qubsi) Date: Tue, 31 Jul 2012 00:47:50 +0300 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: Hi Bernardo and all ... about the xml2po tool I test it and as you said its more better in generating the pot po files I edited the Procedure in : http://wiki.koha-community.org/wiki/Koha_Manual I try to translate some section in the po file and it go after the Procedure translated xml and look very good Hi Fr?d?ric So what next ? Karam On Sun, Jul 29, 2012 at 2:02 AM, Bernardo Gonzalez Kriegel < bgkriegel at gmail.com> wrote: > 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 < >> laurence.lefaucheur at biblibre.com> 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 >>> >>> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From frederic at tamil.fr Tue Jul 31 09:36:57 2012 From: frederic at tamil.fr (=?ISO-8859-1?Q?Fr=E9d=E9ric_Demians?=) Date: Tue, 31 Jul 2012 09:36:57 +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: <50178B19.6000805@tamil.fr> > Hi Fr?d?ric > So what next ? Someone else than Bernardo or yourself has to validate the whole process to confirm that it works as expected. What next: 1) Translation process validation 2) You, and others, send me their .po files that have been generated with 1). 3) .po files from 2) are pushed on translate.koha-community.org. As soon as 1) is done, you can work on translating your .po file with the guaranty not to loose your work. We then have to design a synchronization mechanism: 1) What happen when Nicole Engard (Koha Documentation Manager) updates the English master DocBook file? 2) How to publish/package the localized documentation (not the .po files, the HTML/PDF files)? At which frequency? We still have to think about several things: - Will translators work online (on Pootle) or offline (in a local .po files editor)? This will impact the synchronization mechanism. - What release frequency is wishable? - How to deal exactly with screenshots? Shouldn't it better to have as less screenshots as possible? I will personally not be able to work on that stuff before the end of August. But but you're welcome pursuing experimentations and thinking. Kind regards,