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?
----- Original Message ----
From: "address@hidden" <address@hidden>
To: address@hidden
Sent: Saturday, 19 January, 2008 7:00:45 PM
Subject: Koha-translate Digest, Vol 19, Issue
10
Send Koha-translate mailing list submissions to
address@hiddenTo subscribe or unsubscribe via the World Wide Web, visit
http://lists.nongnu.org/mailman/listinfo/koha-translateor, via email, send a message with subject or body 'help' to
address@hiddenYou can reach the person managing the list at
address@hiddenWhen 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" <
address@hidden>
Subject: Re: [Koha-translate] Some questions
To: "Axel Bojer" <
address@hidden>
Cc:
address@hiddenMessage-ID:
<
address@hidden>
Content-Type: text/plain; charset=ISO-8859-1
Hi Axel,
Some answers to your excellent questions follow:
On 1/17/08, Axel Bojer <
address@hidden> 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__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
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_roadWe 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/NorwegianPlease 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
address@hidden |Full Demos at
http://liblime.com/koha |1(888)KohaILS
------------------------------
Message: 2
Date: Sat, 19 Jan 2008 01:30:55 +0100
From: Axel Bojer <
address@hidden>
Subject: Re: [Koha-translate] Some questions
To: Joshua Ferraro <
address@hidden>
Cc:
address@hiddenMessage-ID: <
address@hidden>
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 <
address@hidden> 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_codeso 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/ReconciliationSo 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
------------------------------
Message: 3
Date: Sat, 19 Jan 2008 15:58:49 +0100
From: Dorian Meid <
address@hidden>
Subject: Re: [Koha-translate] Some questions
To:
address@hiddenMessage-ID: <
address@hidden>
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" <
address@hidden>
Subject: Re: [Koha-translate] Some questions
To: "Dorian Meid" <
address@hidden>
Cc:
address@hiddenMessage-ID:
<
address@hidden>
Content-Type: text/plain; charset=ISO-8859-1
On 1/19/08, Dorian Meid <
address@hidden> 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
address@hidden |Full Demos at
http://liblime.com/koha |1(888)KohaILS
------------------------------
_______________________________________________
Koha-translate mailing list
address@hiddenhttp://lists.nongnu.org/mailman/listinfo/koha-translateEnd of Koha-translate Digest, Vol 19, Issue 10
**********************************************