January 2008 - Koha-translate - lists.koha-community.org

2 questions and a comment
by Selma Aslan 24 Jan '08

24 Jan '08

Hi 1. A request for clarification please: referring to item 98: #. %1$s: TMPL_VAR name=import_errors #: ../../koha-tmpl/intranet-tmpl/prog/en/modules/tools/stage-marc-import.tmpl:39 #, c-format msgid "%s records not staged because of MARC error" msgstr "" a. Does "stage" above mean starting the import process, and b. %s imply that a number is to be inserted there ? c. If yes, and if the structure of the language requires this number to be stated in the middle, rather than at the beginning can we move it? eg. if "%s records not staged because of MARC error" means "The process of importing could not be started for x number of records because of MARC error". I have to translate it into Turkish as follows: " MARC hatasi nedeniyle x kaydın işlemleri başlatılamamıştır" which requires %s to be placed in the middle: "MARC hatasi nedeniyle %s kaydın işlemi başlatilamamiştir" is that OK? 2. If bibs stands for bibliographic records, what does "biblios" stand for? Are they the same? 3. I understand most prefer web interface as I do myself. However I would like to point out that it is very useful to use the files to put terms to be translated into context. For instance in the case of item 123, which reads "© %s" , it did not mean anything to me until I found the following in the file: #. For the first occurrence,#. %1$s: TMPL_VAR name=copyrightdate#: ../../koha-tmpl/intranet-tmpl/prog/en/modules/suggestion/acceptorreject.tmpl:100#: ../../koha-tmpl/intranet-tmpl/prog/en/modules/suggestion/acceptorreject.tmpl:140#, c-formatmsgid "© %s"msgstr "" Thanks Selma Aslan ----- Original Message ---- From: "koha-translate-request(a)nongnu.org" <koha-translate-request(a)nongnu.org> To: koha-translate(a)nongnu.org Sent: Thursday, 17 January, 2008 7:00:43 PM Subject: Koha-translate Digest, Vol 19, Issue 8 Send Koha-translate mailing list submissions to koha-translate(a)nongnu.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.nongnu.org/mailman/listinfo/koha-translate or, via email, send a message with subject or body 'help' to koha-translate-request(a)nongnu.org You can reach the person managing the list at koha-translate-owner(a)nongnu.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha-translate digest..." Today's Topics: 1. (no subject) (Karen Myers) 2. Tetun translation for Koha 3 (Karen Myers) 3. Re: Translate Koha 3.0 to Spanish (Joshua Ferraro) 4. Re: Tetun translation for Koha 3 (Joshua Ferraro) 5. Accepting translations made on the Hungarian versions (Agnes Imecs) 6. Status of Koha 3 Translations (two weeks remaining) (Joshua Ferraro) 7. translation (Ignacio Javier) ---------------------------------------------------------------------- Message: 1 Date: Wed, 16 Jan 2008 20:29:08 +0000 From: Karen Myers <karenmyers1(a)hotmail.com> Subject: [Koha-translate] (no subject) To: <koha-translate(a)nongnu.org> Message-ID: <BAY142-W113ADFF1F442FCCF5A2675FD400(a)phx.gbl> Content-Type: text/plain; charset="iso-8859-1" Hi I'd like to do the Tetun translation for Koha 3. Could I request a file to be setup on the translation site please? thanks Karen Myers _________________________________________________________________ New music from the Rogue Traders - listen now! http://ninemsn.com.au/share/redir/adTrack.asp?mode=click&clientID=832&refer… ------------------------------ Message: 2 Date: Wed, 16 Jan 2008 20:29:37 +0000 From: Karen Myers <karenmyers1(a)hotmail.com> Subject: [Koha-translate] Tetun translation for Koha 3 To: <koha-translate(a)nongnu.org> Message-ID: <BAY142-W15B10A20D652EC38CDEEF5FD400(a)phx.gbl> Content-Type: text/plain; charset="iso-8859-1" Hi I'd like to do the Tetun translation for Koha 3. Could I request a file to be setup on the translation site please? thanks Karen Myers _________________________________________________________________ New music from the Rogue Traders - listen now! http://ninemsn.com.au/share/redir/adTrack.asp?mode=click&clientID=832&refer… ------------------------------ Message: 3 Date: Wed, 16 Jan 2008 18:37:30 -0500 From: "Joshua Ferraro" <jmf(a)liblime.com> Subject: Re: [Koha-translate] Translate Koha 3.0 to Spanish To: "Santiago Hermira Anchuelo" <santiago.hermira(a)gmail.com> Cc: koha-translate(a)nongnu.org Message-ID: <2dfa91e40801161537u5a84d492obfe279c6cf562c05(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hi Santiago, Thank you for your submission. I've uploaded the Staff interface to translate.koha.org, it looks like it's about 55% completed, so congrats!. Cheers, Joshua On 1/15/08, Santiago Hermira Anchuelo <santiago.hermira(a)gmail.com> wrote: > Hi all, > > The OPAC translation for Spanish is finished in the web (I need the > approbation for the proposals). > > I translated some items of Intranet in a .po file. > Language: es > Region: ES > Country: Spain > > I use the web interface (http://translate.koha.org) > > thanks, > Santiago Hermira. > > > > > _______________________________________________ > Koha-translate mailing list > Koha-translate(a)nongnu.org > http://lists.nongnu.org/mailman/listinfo/koha-translate > > > -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS ------------------------------ Message: 4 Date: Wed, 16 Jan 2008 18:42:01 -0500 From: "Joshua Ferraro" <jmf(a)liblime.com> Subject: Re: [Koha-translate] Tetun translation for Koha 3 To: "Karen Myers" <karenmyers1(a)hotmail.com> Cc: koha-translate(a)nongnu.org Message-ID: <2dfa91e40801161542x10381371heefa537b2736a4c2(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hi Karen, I've added Tetum/Tetun to translate.koha.org. Happy Translating! Sincerely, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS On 1/16/08, Karen Myers <karenmyers1(a)hotmail.com> wrote: > > > Hi > > I'd like to do the Tetun translation for Koha 3. Could I request a file to be setup on the translation site please? > > thanks > Karen Myers > _________________________________________________________________ > New music from the Rogue Traders - listen now! > http://ninemsn.com.au/share/redir/adTrack.asp?mode=click&clientID=832&refer… > > _______________________________________________ > Koha-translate mailing list > Koha-translate(a)nongnu.org > http://lists.nongnu.org/mailman/listinfo/koha-translate > ------------------------------ Message: 5 Date: Wed, 16 Jan 2008 15:58:33 -0800 (PST) From: Agnes Imecs <eloise212(a)yahoo.com> Subject: [Koha-translate] Accepting translations made on the Hungarian versions To: Kohalista <koha-translate(a)nongnu.org> Message-ID: <640066.79520.qm(a)web50401.mail.re2.yahoo.com> Content-Type: text/plain; charset="us-ascii" Hello Joshua, You mentioned to contact you if we have a representative quantity of translations. I did worked on both files. Can you accept the translations, that someone can check them? Thanks! Agnes ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

5 7

Re: [Koha-devel] A complete translation
by Galen Charlton 23 Jan '08

23 Jan '08

Hi, On 1/23/08, Zeno Tajoli <tajoli(a)cilea.it> wrote: > > I image that the final result of translation of Koha framework is to > create new > dir under ../koha-3.00.00-alpha/installer/data/mysql/ > > An example could be ./koha-3.00.00-alpha/installer/data/mysql/it/ > Correct, the translated MARC framework would end up in a subdirectory under installer/data/mysql/it, typically something like: installer/data/mysql/it/marcflavour/unimarc or installer/data/mysql/it/marcflavour/marc21 or installer/data/mysql/it/marcflavour/itmarc depending the MARC format you use. If you were to also create sample settings and data for Italian libraries, the SQL scripts to load that data would also go under subdirectories of installer/data/mysql/it. Regards, Galen -- Galen Charlton Koha Application Developer LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709

1 0

A complete translation
by Zeno Tajoli 23 Jan '08

23 Jan '08

Hi to all, Reading the documentation about the translation I have understood the the result of two *.po files is to create the correct templates in dir with the code of the language. So for italian (it) dirs like: ../koha-3.00.00-alpha/koha-tmpl/intranet-tmpl/prog/it ../koha-3.00.00-alpha/koha-tmpl/opac-tmpl/prog/it But reading this mail http://lists.gnu.org/archive/html/koha-translate/2007-11/msg00002.html I undestood that there is also the Koha framework to translate. I image that the final result of translation of Koha framework is to create new dir under ../koha-3.00.00-alpha/installer/data/mysql/ An example could be ./koha-3.00.00-alpha/installer/data/mysql/it/ Is it correct ? Thank you for everything. Cheers Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

1 0

Some more questions concerning translation strings
by Axel Bojer 20 Jan '08

20 Jan '08

Hello again, and thank for your good answers! 1) Just to be sure; what is inside the <b>-tag should be left in English because it is a command, I guess? <b>marcflavour --</b> Your MARC flavor (MARC21 or UNIMARC). This choice tells Koha how to interpret your MARC records. 2) In example below, I suppose the -- should replace a — and thus be a perfectly normal sentence (and not any kind of strange graphic replacement to divide sentences on the screen, right)? But what is, then with the - right after the number? And why not use —? (A proper long dash might get lost in some characters encodings I guess, and would therefore not be advisable ...) 15- Heading use--subject added entry (There are more such strings.) 3) What does the exclamation marks mean in strings like this: 7 => !OPAC Intranet !Editor Collapsed Of course I could just leave them all before the corresponding words, but I think the best translation might be to join Opac Intranet into "Publikumskatalogen" in Norwegian, and then two of the, in English, unique strings would then be just the same in Norwegian. So, what are they for? 4) I do not understand these strings: Aitoff (found it in Wikipedia as Aitoff projection, is that the right meaning: http://en.wikipedia.org/wiki/Aitoff_projection ?) Albers (does also this mean a projection type: http://en.wikipedia.org/wiki/Albers_projection ?) Aluminographie = ? 625 PAL and 625 SECAM, is this about televisions? http://en.wikipedia.org/wiki/Pal http://en.wikipedia.org/wiki/SECAM ATS -- Wikipedia lists many possible explanations, which is it? http://en.wikipedia.org/wiki/ATS CCF -- Which one? :-) http://en.wikipedia.org/wiki/CCF Caseine (french) -- About cheese too? Or am I wrong? (confused) http://en.wikipedia.org/wiki/Casein Chorochromatique = ? (something about colours apparently ...) Choroplethe = Choropleth map, perhaps? http://en.wikipedia.org/wiki/Choropleth_map Comtd = ? (fransk?) Best regards Axel Bojer

2 1

Tetun translation for Koha 3
by Karen Myers 20 Jan '08

20 Jan '08

Hi I'd like to do the Tetun translation for Koha 3. Could I request a file to be setup on the translation site please? thanks Karen Myers _________________________________________________________________ New music from the Rogue Traders - listen now! http://ninemsn.com.au/share/redir/adTrack.asp?mode=click&clientID=832&refer…

2 2

Language, Script, Country, Encoding - an Explanation
by Dorian Meid 20 Jan '08

20 Jan '08

I recognize slight uncertainties when submitting the metadata for your translations. So I wanted to explain the basics a little. Koha uses RFC4646 http://rfc.net/rfc4646.html for language identification. It states, that a language is identified by several tags, separated by a hyphen: Language tag - Script tag - Region/Country tag The language tag is written in lowercase, the script tag is written in lowercase with the first letter in uppercase and the region or country tag is written in uppercase. Example: zh-Hans-CN zh is Chinese, Hans is the simplified Chinese script and CN is China. The language is how you speak or what word you use to name a thing. The language tags are standardised in ISO 639-1 or ISO 639-2 http:// www.loc.gov/standards/iso639-2/php/code_list.php As we are in a library environment it may be useful to mention the difference between ISO 639-2/T and ISO 639-2/B. T refers the terminology code and B refers the bibliographic code, e.g. german has the tag "deu" in ISO 639-2/T and "ger" in ISO 639-2/B. The reason for this inconvenience is that some libraries assigned some tags for languages (the B-tags) before the ISO (T) standardisation was made. The T and B differences are only in the three-letter tags of ISO 639-2. So far we use the two-letter tags of ISO 639-1, but RFC4646 allows also 639-2. The script is how your characters look like or what you paint to produce a specific sound. The script tags are standardised in ISO 15942 http://www.unicode.org/ iso15924/codelists.html You have to add the script tag if your language can be written in more than one script, e.g. Hans for simplified Chinese or Hant for traditional chinese, or if the specified language is not written in the normal script e.g. de-Latf-DE for German in Fraktur. You should, but don't have to omit the script tag if there is only one commonly used script for your language. The region or country is where the language is spoken, this is important because there often are differences between countries, which basically share the same language, e.g. British English and American English. The region/country tag is either a two letter Country code as sandardised in ISO 3166-1 http://www.iso.org/iso/country_codes/ iso_3166_code_lists.htm or a three digit Region code as standardised in UN M.49 http://unstats.un.org/unsd/methods/m49/m49.htm Normally we use the ISO letter code, but the UN region code can be handy when specifying a language spoken in more than one country, e.g. es-005 (Spanish as spoken in South America). When given a script tag we know how your script should look like, but computers are dumb. They don't know written characters, the just know bytes. The assignment of written (visual) characters to byte values is called character encoding. There are many different character encodings and to make it even worse there are some scripts, which can be successfully encoded in different ways. Normal character encodings are capable of assigning 128 or 256 characters. Unicode is capable of several billions of characters and can encode all used scripts, so it is the preffered choice for Koha themes and translations. So please use UTF-8 for your document character encoding http:// www.unicode.org/standard/WhatIsUnicode.html If you can't use UTF-8 or don't know how to use it please ask the list or at least specifiy the encoding you are using, so we can transcode your document. Hope that helps. Maybe this should be added to the readme on translate or the wiki. Dorian Meid

1 0

Ukrainian translation of Koha 3.0
by Serhij Dubyk Сергі й Дубик 20 Jan '08

20 Jan '08

Hi all I want to add Ukrainian translation: Language: українська Language in English: Ukrainian Country: Ukraine Cyrillic script code: Cyrl At this time I am main ukrainian translator: Serhij Dubyk (Сергій Дубик) Translation is maked localy with poEdit and posted on our translation service Pootle: http://www.library.lviv.ua:8080/uk/koha_3_0/ (to Ukrainians - please make suggestions and join to translation process) Some info in ukrainian will be collected on Wiki: http://wiki.koha.org/doku.php?id=ukrainian With best regards Serhij Dubyk, L'viv Scientific Library -- View this message in context: http://www.nabble.com/Ukrainian-translation-of-Koha-3.0-tp14980194p14980194… Sent from the Koha - Translate mailing list archive at Nabble.com.

2 2

Start Russian translation of Koha 3.0
by Serhij Dubyk Сергі й Дубик 20 Jan '08

20 Jan '08

Hi all I want to announce Russian translation for Koha 3.0: Language: русский Language in English: Russian Country: Russian Federation, Ukraine, ... Cyrillic script code: Cyrl Translators: Victor Titarchuk and Serhij Dubyk Translation maked on our on-line translation service Pootle: http://www.library.lviv.ua:8080/ru/koha_3_0/ To Russian-speaking people - please help with Russian translation, make suggestions, and look/work on Wiki: http://wiki.koha.org/doku.php?id=russian With best regards Serhij Dubyk -- View this message in context: http://www.nabble.com/Start-Russian-translation-of-Koha-3.0-tp14980243p1498… Sent from the Koha - Translate mailing list archive at Nabble.com.

1 0

Some questions
by Axel Bojer 20 Jan '08

20 Jan '08

Hello! I have some comments and questions concerning the Koha-translation, and hope there is someone out there that could help me :-) As you see for instance here: http://translate.koha.org/editpot.php?lg=en&db_table=fr__FR__i__opac__t__pr… there are strings like: $  But I suppose those are not to be localized at all, but just left as is? Something like: $  (translated to Norwegian) would supposedly not work, would it? But since it is there I assume something has to be configurable, so I am a little bit confused about those (there are more of them, some with some text in between, some without). Other than that, it would be nice if strings occurring twice could be eliminated, I am thinking of strings like this: In the staff file: ------------------ Catalogue by Item Type Catalogue by itemtype (strings 1447 and 1448) Other than inconsistent spelling, those are perfectly the same. Sometimes I see the same strings twice, but one of them misspelled, like this: Combinaisons de techiques diverses de detection thermique par infrarouge Combinaisons de techiques en faible emission Combinaisons de techniques diverses de detection thermique par infrarouge Combinaisons de techniques en faible emission (1683--86) Two of those obviously would have to be removed. String 1403 is also misspelled: Cannot Delete Currencey I also don't quite follow the necessity of string pairs like these: Couleur Couleur: (1179 and 1780) -- sometimes even more of them, just with * or extra an extra space before : added also, which makes up to four practically identical strings. with just a small effort in scripting these copies could be erased. I suppose some hundred, if not more, of the strings could be omitted by correcting such mistakes. I know I can search and replace (Kbabel and Kaider), copy and paste -- or even just use the translation database (Kbabel), but for the poor people using the web interface this is not easy to do. So if someone could take a look at this we could ease the translation job for everyone :-) Then for some mystic strings that I don't quite understand the meaning of: Bibs -- Is this a Unique Name and therefore not translatable? I could not find it on Google or Wikipedia. mc:v or mc-rtype:o and more of the same sort, are those really to be translated, and what do they mean? No added comment there, that could have helped :-) moon script -- What is this? I know what Braille is, but moon script? road type -- We are not talking about cars, are we, so what is it? http://en.wikipedia.org/wiki/Types_of_road reconcillation -- What is this according to Koha? If someone could clear this up, we would be happy :-) BTW: How do we give credits to the translators? I see some names in the staff-file, but no string like: Translator or similar, like KDE has. Do you add this, and do we then have to submit all the names of our translators to you to get it in? We are a group of four, maybe five translators, mainly because we have two writing languages :-P http://en.wikipedia.org/wiki/Norwegian Best regards Axel Bojer Norwegian translator of Koha

5 7

Re: Koha-translate Digest, Vol 19, Issue 10
by Selma Aslan 19 Jan '08

19 Jan '08

Hello Everyone I would like to make a comment on "Reconciliation": In one of the institutions I worked in the past we used to reconcile revenue records kept in the library and the accounts to make sure that they match. So, I don't know if this is relevant in the context of Koha, but I would expect it to be a kind of cross checking. Does that make sense? Selma Aslan ----- Original Message ---- From: "koha-translate-request(a)nongnu.org" <koha-translate-request(a)nongnu.org> To: koha-translate(a)nongnu.org Sent: Saturday, 19 January, 2008 7:00:45 PM Subject: Koha-translate Digest, Vol 19, Issue 10 Send Koha-translate mailing list submissions to koha-translate(a)nongnu.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.nongnu.org/mailman/listinfo/koha-translate or, via email, send a message with subject or body 'help' to koha-translate-request(a)nongnu.org You can reach the person managing the list at koha-translate-owner(a)nongnu.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha-translate digest..." Today's Topics: 1. Re: Some questions (Joshua Ferraro) 2. Re: Some questions (Axel Bojer) 3. Re: Some questions (Dorian Meid) 4. Re: Some questions (Joshua Ferraro) ---------------------------------------------------------------------- Message: 1 Date: Fri, 18 Jan 2008 18:59:59 -0500 From: "Joshua Ferraro" <jmf(a)liblime.com> Subject: Re: [Koha-translate] Some questions To: "Axel Bojer" <axelb(a)skolelinux.no> Cc: koha-translate(a)nongnu.org Message-ID: <2dfa91e40801181559p2f4bac5ai1b14e039b1247f75(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hi Axel, Some answers to your excellent questions follow: On 1/17/08, Axel Bojer <axelb(a)skolelinux.no> wrote: > Hello! > > I have some comments and questions concerning the Koha-translation, and > hope there is someone out there that could help me :-) > > As you see for instance here: > http://translate.koha.org/editpot.php?lg=en&db_table=fr__FR__i__opac__t__pr… > > there are strings like: > > $  > > But I suppose those are not to be localized at all, but just left as is? > Something like: > > $  > (translated to Norwegian) > > would supposedly not work, would it? > But since it is there I assume something has to be configurable, so I am > a little bit confused about those (there are more of them, some with > some text in between, some without). You're right, the example should NOT be translated, but should be left as is. It's a failing of the gettext tool perhaps, or maybe we need to edit our base template in that case to prevent that example from showing up. > Other than that, it would be nice if strings occurring twice could be > eliminated, I am thinking of strings like this: > > In the staff file: > ------------------ > Catalogue by Item Type > Catalogue by itemtype > (strings 1447 and 1448) Yes, we should attempt to normalize the strings, sorry ... it's a lot of work, I know! > Other than inconsistent spelling, those are perfectly the same. > Sometimes I see the same strings twice, but one of them misspelled, like > this: > > Combinaisons de techiques diverses de detection thermique par infrarouge > Combinaisons de techiques en faible emission > Combinaisons de techniques diverses de detection thermique par infrarouge > Combinaisons de techniques en faible emission > (1683--86) > Two of those obviously would have to be removed. Agreed. I can attempt to do this for 3.0 beta > String 1403 is also misspelled: > Cannot Delete Currencey > > I also don't quite follow the necessity of string pairs like these: > > Couleur > Couleur: > (1179 and 1780) > -- sometimes even more of them, just with * or extra an extra space > before : added also, which makes up to four practically identical strings. Yes yes yes ... > with just a small effort in scripting these copies could be erased. > I suppose some hundred, if not more, of the strings could be omitted by > correcting such mistakes. I know I can search and replace (Kbabel and > Kaider), copy and paste -- or even just use the translation database > (Kbabel), but for the poor people using the web interface this is not > easy to do. So if someone could take a look at this we could ease the > translation job for everyone :-) Agreed. I will attempt to do this for 3.0 beta. > Then for some mystic strings that I don't quite understand the meaning of: > > Bibs -- Is this a Unique Name and therefore not translatable? I could > not find it on Google or Wikipedia. Bibs is an abbreviation of 'Bibliographic Records'. > mc:v or mc-rtype:o > and more of the same sort, are those really to be translated, and what > do they mean? No added comment there, that could have helped :-) Those are 'material category' and are mainly just CCL codes, you can ignore them as they are used for the internal search API. > moon script -- What is this? I know what Braille is, but moon script? This is a real script, identified by the Library of Congress apparently ... :) > road type -- We are not talking about cars, are we, so what is it? > http://en.wikipedia.org/wiki/Types_of_road We are talking about street types (such as 'St., Rd., etc.). It's a feature in Koha that you can have authorized value lists for road types. > reconcillation -- What is this according to Koha? Reconciliation (yes it is misspelled), is a term that has to do with the current day's activities I believe (transactions of the day). Someone else might know better than I. > If someone could clear this up, we would be happy :-) > > BTW: How do we give credits to the translators? I see some names in the > staff-file, but no string like: Translator or similar, like KDE has. Do > you add this, and do we then have to submit all the names of our > translators to you to get it in? We are a group of four, maybe five > translators, mainly because we have two writing languages :-P > http://en.wikipedia.org/wiki/Norwegian Please tell us who was responsible for the translation, by posting a mail to this list (koha-translate). I will add the credits to the 'About' page for the Koha 3.0 beta (I already have a list of some of you, but obviously if you want credit you must identify yourselves as a contributor :-)). Thanks again for these excellent questions, let us know if we can help further. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS ------------------------------ Message: 2 Date: Sat, 19 Jan 2008 01:30:55 +0100 From: Axel Bojer <axelb(a)skolelinux.no> Subject: Re: [Koha-translate] Some questions To: Joshua Ferraro <jmf(a)liblime.com> Cc: koha-translate(a)nongnu.org Message-ID: <479144BF.8010809(a)skolelinux.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Joshua Ferraro wrote: > Hi Axel, > > Some answers to your excellent questions follow: Thank you! > On 1/17/08, Axel Bojer <axelb(a)skolelinux.no> wrote: (...) >> with just a small effort in scripting these copies could be erased. >> I suppose some hundred, if not more, of the strings could be omitted by >> correcting such mistakes. I know I can search and replace (Kbabel and >> Kaider), copy and paste -- or even just use the translation database >> (Kbabel), but for the poor people using the web interface this is not >> easy to do. So if someone could take a look at this we could ease the >> translation job for everyone :-) > Agreed. I will attempt to do this for 3.0 beta. Very good! >> Then for some mystic strings that I don't quite understand the meaning of: >> >> Bibs -- Is this a Unique Name and therefore not translatable? I could >> not find it on Google or Wikipedia. > Bibs is an abbreviation of 'Bibliographic Records'. That makes sense :-) >> mc:v or mc-rtype:o >> and more of the same sort, are those really to be translated, and what >> do they mean? No added comment there, that could have helped :-) > Those are 'material category' and are mainly just CCL codes, you can ignore > them as they are used for the internal search API. Will do :-) >> moon script -- What is this? I know what Braille is, but moon script? > This is a real script, identified by the Library of Congress apparently ... :) In the meantime we found this: http://en.wikipedia.org/wiki/Moon_code so perhaps it should be rephrased to moon code? >> road type -- We are not talking about cars, are we, so what is it? >> http://en.wikipedia.org/wiki/Types_of_road > We are talking about street types (such as 'St., Rd., etc.). It's a > feature in Koha > that you can have authorized value lists for road types. Really? hmm ... ok :-) >> reconcillation -- What is this according to Koha? > Reconciliation (yes it is misspelled), is a term that has to do with the current > day's activities I believe (transactions of the day). Someone else might know > better than I. Some sort of unification, we thought: http://www.m-w.com/dictionary/Reconciliation So probably, then, some way to unite something: <a1>Home</a> &rsaquo; <a2>Reports</a> &rsaquo; Till Reconciliation would perhaps, then, be the unification/merging of two different reports into one? That is our best guess by now :-) Perhaps also here a rephrasing (into some of the more well known (close to be) synonyms mentioned)? >> BTW: How do we give credits to the translators? I see some names in the >> staff-file, but no string like: Translator or similar, like KDE has. Do >> you add this, and do we then have to submit all the names of our >> translators to you to get it in? We are a group of four, maybe five >> translators, mainly because we have two writing languages :-P >> http://en.wikipedia.org/wiki/Norwegian > Please tell us who was responsible for the translation, by posting a mail > to this list (koha-translate). I will add the credits to the 'About' > page for the > Koha 3.0 beta (I already have a list of some of you, but obviously if you want > credit you must identify yourselves as a contributor :-)). We are: Norwegian Bokmål: Axel Bojer and Thomas Gramstad Norwegian Nynorsk: Unni Knutsen and Marit Kristine Ådland We will tell you if there are changes, but I suppose that will be it :-) > Thanks again for these excellent questions, let us know if we can help further. Actually, one more right away -- about the html-encodings :-) In Norway we don't citate with "word" but with «word». I see many places, that " is used instead (in English). Do we, then, have to change ours into » and « everywhere, or will « and » be recognized? I thought of doing a search and replace for all of them at the last moment before submitting, just to be sure everything is viewed correctly, or will some of the text be rendered differently than by html (just text f.i.), so that we will have to use « and » somewhere too? I suppose – (or —) will be better than -- too, will it not? I found this in many strings ... Best regards Axel Bojer ------------------------------ Message: 3 Date: Sat, 19 Jan 2008 15:58:49 +0100 From: Dorian Meid <dnmeid(a)gmx.de> Subject: Re: [Koha-translate] Some questions To: koha-translate(a)nongnu.org Message-ID: <0DC40086-6393-4879-BB01-453AC6DD3387(a)gmx.de> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Am 19.01.2008 um 01:30 schrieb Axel Bojer: > Actually, one more right away -- about the html-encodings :-) > > In Norway we don't citate with "word" but with «word». I see many > places, that " is used instead (in English). Do we, then, have > to change ours into » and « everywhere, or will « and » > be recognized? I thought of doing a search and replace for all of > them at the last moment before submitting, just to be sure > everything is viewed correctly, or will some of the text be > rendered differently than by html (just text f.i.), so that we will > have to use « and » somewhere too? Another good question. Apparently the quotes have been left out while rewriting the html for CSS. I suggest to use the q-tag instead of quotes: <q>word</q> Then most browsers should handle the quotation marks correctly according to the browsers set language. For a better control we can specify how the q-tag is handeled in the stylesheet. Here is an excelent articel about that: http://www.456bereastreet.com/archive/200411/ quotations_and_citations_quoting_text/ This would also be a great advantage for theme-designers. Dorian Meid PS: if you want a quick and dirty solution: If you have encoded your files in UTF8 « and » will work. ------------------------------ Message: 4 Date: Sat, 19 Jan 2008 11:17:23 -0500 From: "Joshua Ferraro" <jmf(a)liblime.com> Subject: Re: [Koha-translate] Some questions To: "Dorian Meid" <dnmeid(a)gmx.de> Cc: koha-translate(a)nongnu.org Message-ID: <2dfa91e40801190817n188f788dl629f9b35dd8341f9(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 On 1/19/08, Dorian Meid <dnmeid(a)gmx.de> wrote: > > Am 19.01.2008 um 01:30 schrieb Axel Bojer: > > Actually, one more right away -- about the html-encodings :-) > > > > In Norway we don't citate with "word" but with «word». I see many > > places, that " is used instead (in English). Do we, then, have > > to change ours into » and « everywhere, or will « and » > > be recognized? I thought of doing a search and replace for all of > > them at the last moment before submitting, just to be sure > > everything is viewed correctly, or will some of the text be > > rendered differently than by html (just text f.i.), so that we will > > have to use « and » somewhere too? > > Another good question. > Apparently the quotes have been left out while rewriting the html for > CSS. > I suggest to use the q-tag instead of quotes: <q>word</q> > Then most browsers should handle the quotation marks correctly > according to the browsers set language. > For a better control we can specify how the q-tag is handeled in the > stylesheet. > Here is an excelent articel about that: > http://www.456bereastreet.com/archive/200411/ > quotations_and_citations_quoting_text/ > This would also be a great advantage for theme-designers. OK, I think this is the correct solution, I will also work to fix this for the 3.0 beta. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS ------------------------------ _______________________________________________ Koha-translate mailing list Koha-translate(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-translate End of Koha-translate Digest, Vol 19, Issue 10 ********************************************** __________________________________________________________ Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com

2 1