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__prog__v__3000000&view=all&total=956 there are strings like: $<!-- TMPL_VAR NAME=\"code\" --> <!-- TMPL_VAR NAME=\"value\" --> But I suppose those are not to be localized at all, but just left as is? Something like: $<!-- TMPL_VAR NAME=\"verdi\" --> <!-- TMPL_VAR NAME=\"verdi\" --> (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
Hi to all, I have same question about self check interface: ../koha-tmpl/opac-tmpl/prog/en/modules/sco file sco-main.tmpl:91 msgid "Check out or return an item:" But 'check out' isn't an equivalent of 'return' ? I have understood that the self check interface is only to 'return' items to the library. Or does the self check interface do loans and the returns ? And what is it the phrase for the loan and the phrase for the return ? Bye to all Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)
Zeno Tajoli a écrit :
Hi to all,
Hi neighbour (i'm in Marseille, so 2 hours from italy by car)
I have same question about self check interface:
../koha-tmpl/opac-tmpl/prog/en/modules/sco file sco-main.tmpl:91 msgid "Check out or return an item:"
But 'check out' isn't an equivalent of 'return' ? nope, it's exactly the opposite ;-)
check-OUT means the document go OUT of your library. So it's an issue. check-IN means the document go IN your library, so it's a return. (I had the same trouble when us ppl changed the vocabulary)
I have understood that the self check interface is only to 'return' items to the library.
nope, it's to do check-out, so issues. NOT returns. -- Paul POULAIN BibLibre SARL Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19
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__prog__v__3000000&view=all&total=956
there are strings like:
$<!-- TMPL_VAR NAME=\"code\" --> <!-- TMPL_VAR NAME=\"value\" -->
But I suppose those are not to be localized at all, but just left as is? Something like:
$<!-- TMPL_VAR NAME=\"verdi\" --> <!-- TMPL_VAR NAME=\"verdi\" --> (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
Hi Axel, Some answers to your excellent questions follow: On 1/17/08, Axel Bojer <axelb@skolelinux.no> wrote: 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@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
Joshua Ferraro wrote:
Hi Axel,
Some answers to your excellent questions follow:
Thank you!
On 1/17/08, Axel Bojer <axelb@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> › <a2>Reports</a> › 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
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.
On 1/19/08, Dorian Meid <dnmeid@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@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
Joshua Ferraro wrote:
On 1/19/08, Dorian Meid <dnmeid@gmx.de> wrote:
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
Am 19.01.2008 um 01:30 schrieb Axel Bojer: 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.
Perhaps the best, all in all, I agree. But, there is a problem still there for some: <q> seems not to be fully supported (especially not in IE, not surprisingly), and therefore will render many strings in a wrong way. And if the *browser* gets to decide, then I can't read the Norwegian opac with for instance an English Firefox without getting the wrong quotation marks, witch I find a pity. Of course everyone is free to change <q>, then, as with " also, so from that point of view it would not give more work either. And, as a pro, it can be fully automated as the "s in the code declarations won't be influenced by it. But I would prefer to replace either one of those with either the html-code or the utf-8-encoded signs (« and » for us). For everyone using English quotation marks this would really not be any problem any way, so ... :-) Best regards Axel Bojer
participants (5)
-
Axel Bojer -
Dorian Meid -
Joshua Ferraro -
Paul POULAIN -
Zeno Tajoli