Re: [Koha-devel] Translation

2024-01-25 Thread Kevin Carnes via Koha-devel
The strings should also match:
contributors

to:


Regards,
Kevin

Från: Kevin Carnes 
Skickat: den 25 januari 2024 10:07
Till: Koha-devel ; Marcel de Rooy 

Ämne: Sv: Translation

Hi again Marcel,

The example should be:
contributors

to:


I accidentally copied the wrong line.

Regards,
Kevin

Från: Koha-devel  för Kevin Carnes 
via Koha-devel 
Skickat: den 25 januari 2024 10:00
Till: Koha-devel ; Marcel de Rooy 

Ämne: Re: [Koha-devel] Translation

Hi Marcel,

The link is created using XSLT and the names of the classes are in text nodes 
which are extracted and can be translated. To prevent this, the names can be 
specified in an attribute since they are not extracted and won't be translated. 
You can use a value-of element with the select attribute set to the class name 
in single quotation marks.

For example, in 
koha-tmpl/opac-tmpl/bootstrap/en/xslt/MARC21slim2OPACDetail.xsl, you can 
replace:
contributor

With:


Regards,
Kevin

Från: Koha-devel  för Marcel de 
Rooy via Koha-devel 
Skickat: den 24 januari 2024 13:58
Till: Koha-devel 
Ämne: [Koha-devel] Translation

Hi,

I came across this link on opac-detail in our Dutch OPAC:

Dalbajewa, 
Birgit [contributor]

As you may see, various class names, attribute names etc. are being translated 
(while they should not have been translated). In the PO file it just says for 
instance msgstr "contributor", so things get translated.
In the above co-auteur and Persoon should not have been there.

Anyone have an idea how we could prevent such entries from coming into the PO 
file at the first place?

Thanks,
Marcel

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


Re: [Koha-devel] Translation

2024-01-25 Thread Kevin Carnes via Koha-devel
Hi again Marcel,

The example should be:
contributors

to:


I accidentally copied the wrong line.

Regards,
Kevin

Från: Koha-devel  för Kevin Carnes 
via Koha-devel 
Skickat: den 25 januari 2024 10:00
Till: Koha-devel ; Marcel de Rooy 

Ämne: Re: [Koha-devel] Translation

Hi Marcel,

The link is created using XSLT and the names of the classes are in text nodes 
which are extracted and can be translated. To prevent this, the names can be 
specified in an attribute since they are not extracted and won't be translated. 
You can use a value-of element with the select attribute set to the class name 
in single quotation marks.

For example, in 
koha-tmpl/opac-tmpl/bootstrap/en/xslt/MARC21slim2OPACDetail.xsl, you can 
replace:
contributor

With:


Regards,
Kevin

Från: Koha-devel  för Marcel de 
Rooy via Koha-devel 
Skickat: den 24 januari 2024 13:58
Till: Koha-devel 
Ämne: [Koha-devel] Translation

Hi,

I came across this link on opac-detail in our Dutch OPAC:

Dalbajewa, 
Birgit [contributor]

As you may see, various class names, attribute names etc. are being translated 
(while they should not have been translated). In the PO file it just says for 
instance msgstr "contributor", so things get translated.
In the above co-auteur and Persoon should not have been there.

Anyone have an idea how we could prevent such entries from coming into the PO 
file at the first place?

Thanks,
Marcel

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


Re: [Koha-devel] Translation

2024-01-25 Thread Kevin Carnes via Koha-devel
Hi Marcel,

The link is created using XSLT and the names of the classes are in text nodes 
which are extracted and can be translated. To prevent this, the names can be 
specified in an attribute since they are not extracted and won't be translated. 
You can use a value-of element with the select attribute set to the class name 
in single quotation marks.

For example, in 
koha-tmpl/opac-tmpl/bootstrap/en/xslt/MARC21slim2OPACDetail.xsl, you can 
replace:
contributor

With:


Regards,
Kevin

Från: Koha-devel  för Marcel de 
Rooy via Koha-devel 
Skickat: den 24 januari 2024 13:58
Till: Koha-devel 
Ämne: [Koha-devel] Translation

Hi,

I came across this link on opac-detail in our Dutch OPAC:

Dalbajewa, 
Birgit [contributor]

As you may see, various class names, attribute names etc. are being translated 
(while they should not have been translated). In the PO file it just says for 
instance msgstr "contributor", so things get translated.
In the above co-auteur and Persoon should not have been there.

Anyone have an idea how we could prevent such entries from coming into the PO 
file at the first place?

Thanks,
Marcel

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


[Koha-devel] Translation

2024-01-24 Thread Marcel de Rooy via Koha-devel
Hi,

I came across this link on opac-detail in our Dutch OPAC:

Dalbajewa, 
Birgit [contributor]

As you may see, various class names, attribute names etc. are being translated 
(while they should not have been translated). In the PO file it just says for 
instance msgstr "contributor", so things get translated.
In the above co-auteur and Persoon should not have been there.

Anyone have an idea how we could prevent such entries from coming into the PO 
file at the first place?

Thanks,
Marcel

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


[Koha-devel] Translation server migrated

2023-11-11 Thread Jonathan Druart via Koha-devel
Hello,

The translation server has been migrated from Pootle to Weblate.
It's a whole new server with a complete new workflow.
The goal was to have it ready to translate 23.11, but everything is not set
up yet (downtimes may appear).

You can login with your Pootle credentials, and you should have the same
privileges (part of a language team/administrator of the team).
Note that no SMTP server (email) is configured yet.
There are some heavy tasks that will be run from 1:00 to 2:00 UTC and from
3:00 to 5:00 (or 6:00? I don't know yet!), expect a slow response time
during these slots (can be adjusted later if needed).

More information (about what has been done and what still need to be done)
can be found on the wiki page
https://wiki.koha-community.org/wiki/Translation_server_migration_weblate

Please report any problems you encounter!

Happy translating!

Cheers,
Jonathan

PS: email to the general mailing list about this migration will be sent
next week.
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


Re: [Koha-devel] translation issues fix script for Release Maintainers

2022-11-22 Thread Jonathan Druart
[resending, my previous reply didn't reach the list]

release_tools is the place I guess.
https://gitlab.com/koha-community/release-tools

But, I run it on master:
sed: -e expression #1, char 1: unknown command: `-'
sed: -e expression #1, char 1: unknown command: `-'

% more translate-errors
misc/translator/po/hy-Armn-opa
c-bootstrap.po:687
misc/translator/po/id-ID-messages.po:3
misc/translator/po/ka-messages.po:3

So I run it again
git diff now shows
-#, c-format
+#, fuzzy, fuzzy, c-format

It is not ready to be widely used I'd say ;)

Le lun. 21 nov. 2022 à 19:42, Katrin Fischer
 a écrit :
>
> Hi Arthur,
>
> thx for sharing :) Is there a place we could store this for future RMaints?
>
> We could also add a note to:
> https://wiki.koha-community.org/wiki/Release_maintenance#Push_updated_translation_files
>
> Katrin
>
>
> On 21.11.22 17:35, Arthur Suzuki wrote:
> > Hello Koha Folks, RMaint fellows,
> > Struggling with translation issues at each release I've started to
> > write a script to fix "most" small translation issues.
> > The script is to be executed in Koha's source folder after merging the
> > translation branch.
> > Best,
> > Arthur
> >
> >
> > ___
> > Koha-devel mailing list
> > Koha-devel@lists.koha-community.org
> > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> > website : https://www.koha-community.org/
> > git : https://git.koha-community.org/
> > bugs : https://bugs.koha-community.org/
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


Re: [Koha-devel] translation issues fix script for Release Maintainers

2022-11-22 Thread Arthur Suzuki

On 2022-11-21 19:42, Katrin Fischer wrote:

thx for sharing :)

yw, thx for storing my valuable(?) things :)


Is there a place we could store this for future RMaints?
best place would be in the "release-tools" repository. not allowed to 
push to https://gitlab.com/koha-community/release-tools
Guess I have to be added to the members of the project (or to the 
"Koha-community" group).



We could also add a note to:
https://wiki.koha-community.org/wiki/Release_maintenance#Push_updated_translation_files

Sure, as soon as I make this script available through the repo?

Arthur


On 21.11.22 17:35, Arthur Suzuki wrote:

Hello Koha Folks, RMaint fellows,
Struggling with translation issues at each release I've started to
write a script to fix "most" small translation issues.
The script is to be executed in Koha's source folder after merging the
translation branch.
Best,
Arthur

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


Re: [Koha-devel] translation issues fix script for Release Maintainers

2022-11-21 Thread Katrin Fischer

Hi Arthur,

thx for sharing :) Is there a place we could store this for future RMaints?

We could also add a note to:
https://wiki.koha-community.org/wiki/Release_maintenance#Push_updated_translation_files

Katrin


On 21.11.22 17:35, Arthur Suzuki wrote:

Hello Koha Folks, RMaint fellows,
Struggling with translation issues at each release I've started to
write a script to fix "most" small translation issues.
The script is to be executed in Koha's source folder after merging the
translation branch.
Best,
Arthur


___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


[Koha-devel] translation issues fix script for Release Maintainers

2022-11-21 Thread Arthur Suzuki

Hello Koha Folks, RMaint fellows,
Struggling with translation issues at each release I've started to write 
a script to fix "most" small translation issues.
The script is to be executed in Koha's source folder after merging the 
translation branch.

Best,
Arthur

--
Arthur Suzuki, ️
Développeur @BibLibrejunitmsgfmt misc/translator/po/* | grep failure | grep -e "[^>:]*.po:[0-9]*" -o 
> translate-errors
for line in $(cat translate-errors)
do
file=$(echo $line|cut -d':' -f1)
from=$(echo $line|cut -d':' -f2)
sed -i -e "$((from -6)),$((from))s/#,/#, fuzzy,/" $file
done

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


[Koha-devel] Translation: One week remaining to complete 21.05 translation to avoid some duplicate work when 21.11 will be out

2021-11-01 Thread Victor Grousset/tuxayo

Hi :)

If your languages of choices don't have yet a full translation for Koha 
21.05, it's a good time to put as much a possible work towards that.


Because in a week, the 10th will be the string freeze to prepare the 
major release of Koha 21.11 which the scheduled around the 26th.
At that moment, translation of 21.05 will be copied as a starting point 
for 21.11.

After that, any translation work on 21.05 will have to be copied to 21.11.
If you usually translate multiple versions, that will spare you one copy 
compared if you do it after the 10th.
If you usually only translate the latest version, it will still help 
people that will stay on 21.05 to benefit from your work.


↓↓↓
https://translate.koha-community.org/projects/21.05/
↑↑↑

Happy translating :)

--
Victor Grousset/tuxayo
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


[Koha-devel] Translation platform sync delay: 2nd call to translators to prepare this month's minor release

2021-10-22 Thread Victor Grousset/tuxayo

Hi,

Due to a delay in getting the platform in sync with the to-be-released 
code, the new strings came Wednesday. So translators are advised to take 
another look to translate these:

https://translate.koha-community.org/

The minor releases of 21.05.x 20.11.x 20.05.x 19.11.x will be around the 
27th.


Happy translating :)

--
Victor Grousset/tuxayo
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


Re: [Koha-devel] Translation too long

2018-10-06 Thread Victor Grousset

Hi,

On 2018-10-06 10:36, BOUIS Sonia wrote:
I’ve noticed that there’s a translation too long in french in 
catalogue/moredetail.pl so it’s unreadable. Cf image.


Is there’s something to change in the code to allow a longer but clearer 
translation : Accession date -> Date d'entrée dans les collections


Or should we just change the translation for a shorter one ?



I noticed it and though I had changed the translation a few weeks ago.
But it's not the case
http://translate.koha-community.org/fr/17.11/translate/#search=Accession%20date%3A=source,target
http://translate.koha-community.org/fr/18.05/translate/#search=Accession%20date%3A=source,target

I though about "Date d'acquisition" which mean "Acquisition date" which 
seems to have a suitable meaning.



--
Victor Grousset, dev support/maintenance
BibLibre, Services en logiciels libres pour les bibliothèques
BibLibre, Libre/Open Source software and services for libraries
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/


[Koha-devel] Translation too long

2018-10-06 Thread BOUIS Sonia
Hello,
I've noticed that there's a translation too long in french in 
catalogue/moredetail.pl so it's unreadable. Cf image.
Is there's something to change in the code to allow a longer but clearer 
translation : Accession date -> Date d'entrée dans les collections
Or should we just change the translation for a shorter one ?

Thanks in advance


[cid:image001.png@01D45D60.7B76E4E0]

Sonia BOUIS
--
Responsable du Service des applications documentaires
Bibliothèques universitaires
Université Jean Moulin Lyon 3
ADRESSE GÉOGRAPHIQUE > Manufacture des Tabacs | 6 cours Albert Thomas | LYON 8e
ADRESSE POSTALE > Bibliothèque de la Manufacture | 1C avenue des Frères Lumière 
| CS 78242 - 69372 LYON CEDEX 08

Ligne directe : 33 (0)4 78 78 79 03

http://bu.univ-lyon3.fr| Suivez-nous > 
Facebook | 
Twitter| 
Instagram
---
L'Université Jean Moulin est membre de l'Université de Lyon

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Translation very difficult if use some tags among text paragraph in html

2015-10-23 Thread Hector Castro
Hi Koha Developers


I don't know if we can use another style when write down paragraphs; some
html tags among paragraph, for example if we use  , ,
 etc., are split in different entries in the po files, and this do
the translation very hard, for example this bug <
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14671>

In the new 3.22 exists another example:

koha-tmpl/intranet-tmpl/prog/en/modules/about.tt

lines 262-264

You are missing the upload_path entry in your
koha-conf.xml file. Please  add it, pointing to the configured file upload
directory for your Koha instance. Also note that you need to properly set
the OPACBaseURL preference for the file upload plugin to
work.

The generated PO file

#: intranet-tmpl/prog/en/modules/about.tt:255
#: intranet-tmpl/prog/en/modules/about.tt:262
#, c-format
msgid "You are missing the "
msgstr "Falta la entrada "

#: intranet-tmpl/prog/en/modules/about.tt:255
#: intranet-tmpl/prog/en/modules/about.tt:262
#, c-format
msgid "upload_path"
msgstr "upload_path"

#: intranet-tmpl/prog/en/modules/about.tt:262
#, c-format
msgid ""
"entry in your koha-conf.xml file. Please add it, pointing to the
configured "
"file upload directory for your Koha instance. Also note that you need to "
"properly set the "
msgstr ""

#: intranet-tmpl/prog/en/modules/about.tt:264
#, c-format
msgid "OPACBaseURL"
msgstr "OPACBaseURL"

#: intranet-tmpl/prog/en/modules/about.tt:264
#, c-format
msgid "preference for the file upload plugin to work. "
msgstr ""

Finally this end up in a nonsensical translation

IMHO, If developers can really take into consideration not to use this kind
of paragraphs and -if possible- modify the coding guidelines in wiki page
to reflect this.

Or if there are another option to do life easy for translators?...

Regards

-- 
Atte,

Hector Eduardo Castro Avalos
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Translation annoyances

2013-12-04 Thread Kallinen Pasi
Katrin Fischer wrote:

I'd rather keep some additional %s and not lose the context and the

Pity Koha doesn't support msgctxt - the gettext context string!
Translators are not coders, nor vice versa. The variable names will mean 
nothing to the translators - it's good if the translator knows what '%s' means, 
and '%%' will confuse them.


The translation script could be improved somewhat by discarding totally useless 
placeholders.

Some simple(?) improvements:

1) Replace all inline TT code in msgid with a placeholders. (eg [% 
variable_name|filter %] = %s)

2) If the msgid begins with a placeholder that is IF, and ends in a placeholder 
that's either END or ELSE, and there are no other placeholders, do not include 
the placeholders.

3) Do not include the placeholder in the msgid, if it is 'END' or 'ELSE' token 
and is at the beginning of the msgid.

4) Do not include the placeholder in the msgid, if it is 'END' or 'ELSE' token 
and is at the end of the msgid.

5) If there's only one placeholder, and it is a flow control token (IF, ELSE, 
etc), and it is not in the beginning or end of msgid, cut the msgid into two 
msgid's.

6) Ignore XSLT xsl:attribute name=hreffoobar/xsl:attribute

7) Ignore XSLT xsl:call-template name=subfieldSelectxsl:with-param 
name=codesfoobar/xsl:with-param/xsl:call-template

8) If msgid is nothing but placeholders (and spaces), do not use it.



--
Ystävällisin terveisin

Pasi Kallinen
ICT-asiantuntija

p. 0400-139747
pasi.kalli...@pttk.fi
Länsikatu 15
80110  Joensuu

Pohjois-Karjalan Tietotekniikkakeskus Oy - www.pttk.fi


From: koha-translate-boun...@lists.koha-community.org 
[koha-translate-boun...@lists.koha-community.org] on behalf of Katrin Fischer 
[katrin.fischer...@web.de]
Sent: Wednesday, December 04, 2013 13:43
To: koha-transl...@lists.koha-community.org
Subject: [Koha-translate]  Translation annoyances

Hi,

I'd rather keep some additional %s and not lose the context and the
chance to do grammatically more correct translations. I'd like to give
some examples:

Grouping together related sentences/error messages:

%sNote: your comment contained illegal markup code. It has been saved
with the markup removed, as below. You can edit the comment further, or
cancel to retain the comment as is. %s %sError! Your comment was
entirely illegal markup code. It has NOT been added.%s %sError! You
cannot add an empty comment. Please add content or cancel.%s

%sEdit course%sCreate course%s

Suggestion status:
%s Pending %s Accepted %s Ordered %s Rejected %s Checked %s %s %s %s 

Import status:
%s Cleaned %s Imported %s Importing %s Reverted %s Reverting %s Staged
%s %s %s 


Allowing translation of 'constructed' sentences:
%sEdit%sCreate%s Label layout

%s Delete %s %s Update %s %s Move %s %s Copy %s %s %s 1st %s %s field
%s%s$%s%s %s with value 


Also if you only take variables into account, a simple [% IF %] checking
for the existance of a variable could be a problem breakting the
translation string:

#. %1$s:  name
#. %2$s:  IF ( invoice )
#. %3$s:  invoice
#. %4$s:  END
#. %5$s:  ordernumber
#: intranet-tmpl/prog/en/modules/acqui/orderreceive.tt:130
#, c-format
msgid Receive items from : %s %s[%s] %s (order #%s)


I think the translation scripts are not so much the problem, but badly
constructed strings in the templates are. I think fixing the templates
would be the better way.

Katrin


Am 04.12.2013 11:34, schrieb Fischer, Katrin:



 -Ursprüngliche Nachricht-
 Von: koha-translate-boun...@lists.koha-community.org im Auftrag von
 Fridolin SOMERS
 Gesendet: Mi 04.12.2013 11:05
 An: koha-transl...@lists.koha-community.org
 Betreff: Re: [Koha-translate] Translation annoyances

 I agree, specially on point 6.
 PO shoould only consider  TT vars [% var %], no other TT tag.

 I will try to work on it.

 Le 02/12/2013 08:37, Kallinen Pasi a écrit :
 Hello.

 I've been translating Koha to Finnish for a bit, and I'm really
 starting to hate some of the automagically generated msgid's.

 1) String concatenation is BAD.
 For example, this line of code:
 var disabledForCurrent = _(Disabled for) + ' ' + $branch;
 turns into this translatable string:
 msgid Disabled for

 For some languages this is very hard to translate without sounding
 stupid or just plain wrong. jQuery has some string placeholder support
 for javascript, so Koha really should be using those instead!
 The example above would turn into:

 var disabledForCurrent = _(Disabled for {0});
 msgid Disabled for {0}


 2) Consistency would be good.
 msgid EAN:
 msgid EAN: 
 msgid EAN :


 3) Sentences should not be cut in pieces.
 msgid Please
 msgid upload
 msgid one.

 The upload-text is a link in the sentence. Ideally this should be:
 msgid Please %supload%s one.


 4) Is it a verb or a noun?
 msgid Copy


 5) The wiki-like help texts should be in separate po-file. The help
 texts inflate the staff UI po-file immensely, and the help 

Re: [Koha-devel] Translation annoyances

2013-12-04 Thread Katrin Fischer
Hi,

I know that things are not perfect for translating Koha, but we have
already fixed a lot of issues since I started translating it a few years
ago and we keep improving. It's not easy and it can only be done by
people dedicating time and work.

I have added some notes and comments to the points you raised:

 1) String concatenation is BAD.
 For example, this line of code:
var disabledForCurrent = _(Disabled for) + ' ' + $branch;
 turns into this translatable string:
msgid Disabled for

There is a bug for that:
Bug 7327 - Translation script doesn't like concatenated javascript strings
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7327


 For some languages this is very hard to translate without sounding stupid or 
 just plain wrong. jQuery has some string placeholder support for javascript, 
 so Koha really should be using those instead!
 The example above would turn into:
 
var disabledForCurrent = _(Disabled for {0});
msgid Disabled for {0}

I think this method looks good and I have seen something similar being
used in the newer code for translating the datatable toolbars:

#. For the first occurrence,
#. SCRIPT
#: intranet-tmpl/prog/en/includes/datatables-strings.inc:1
#: intranet-tmpl/prog/en/includes/datatables.inc:2
msgid (filtered from _MAX_ total entries)

So this looks like something we could do, but fixing all existing
strings will take a lot of work and testing.


 2) Consistency would be good.
msgid EAN:
msgid EAN: 
msgid EAN :

We already fixed a gazillion of those small inconsistencies when we
cleaned up the templates after agreeing on some capitalization rules.
Some things like this still remain, also often we will have a term with
and without :. For an additional space like this a patch would be really
easy.


 3) Sentences should not be cut in pieces.
msgid Please
msgid upload
msgid one.
 The upload-text is a link in the sentence. Ideally this should be:
msgid Please %supload%s one.

Agreed. Also, sentences should not be 'constructed' with
if-else-constructs where it can be avoided.

I think this problem here especially shows when there is a link in the
string, because the scripts look for html tags. It might be possible to
improve that.


 4) Is it a verb or a noun?
msgid Copy

I am not sure how to improve that - do you have a suggestion? Often it
helps to look at the list of files a string appears in to make a bit
more sense of it. In Pootle you can see the list when you hover over the
'Comment:' bit on the left.


 5) The wiki-like help texts should be in separate po-file. The help texts 
 inflate the staff UI po-file immensely, and the help translation is not quite 
 as critical as the UI. Having all the help texts interspersed between all the 
 actually important strings is irritating.

I've sent it to the koha-translate list earlier, but repeating it for
koha-devel - there are some bugs related to this:

Bug 7934 - Separate po file for help pages
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7934

Bug 7939 - Separate po files for different MARC dialects
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7939


 6) Translation is not programming. Replace all Template Toolkit code with 
 placeholders.
 For example
msgid Cancel [% IF TransferWhenCancelAllWaitingHolds %]and Transfer [% 
 END %]All
 and
msgid Cancel hold and return to : [% overloo.branchname %]

Are you suggesting to replace the %s with the real variable names? This
could be a bit easier to read. We got comments in Pootle showing you
what %s stands for what, but I admit that with a lot of %s in a string
it gets a bit hard.


 7) Exclude URLs. Those are not content that should be translatable.

In some cases I have wanted to change URLs in translation. For example I
am linking to the German Firefox Plugin page for the offline-circulation
plugin on the circulation home page:

#: intranet-tmpl/prog/en/modules/help/offline_circ/list.tt:5
#, c-format
msgid https://addons.mozilla.org/en/firefox/addon/koct/;
msgstr https://addons.mozilla.org/de/firefox/addon/koct/;


Hope it helps,

Katrin


___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/


[Koha-devel] Translation annoyances

2013-12-01 Thread Kallinen Pasi
Hello.

I've been translating Koha to Finnish for a bit, and I'm really starting to 
hate some of the automagically generated msgid's.

1) String concatenation is BAD.
For example, this line of code:
   var disabledForCurrent = _(Disabled for) + ' ' + $branch;
turns into this translatable string:
   msgid Disabled for

For some languages this is very hard to translate without sounding stupid or 
just plain wrong. jQuery has some string placeholder support for javascript, so 
Koha really should be using those instead!
The example above would turn into:

   var disabledForCurrent = _(Disabled for {0});
   msgid Disabled for {0}


2) Consistency would be good.
   msgid EAN:
   msgid EAN: 
   msgid EAN :


3) Sentences should not be cut in pieces.
   msgid Please
   msgid upload
   msgid one.

The upload-text is a link in the sentence. Ideally this should be:
   msgid Please %supload%s one.


4) Is it a verb or a noun?
   msgid Copy


5) The wiki-like help texts should be in separate po-file. The help texts 
inflate the staff UI po-file immensely, and the help translation is not quite 
as critical as the UI. Having all the help texts interspersed between all the 
actually important strings is irritating.


6) Translation is not programming. Replace all Template Toolkit code with 
placeholders.
For example
   msgid Cancel [% IF TransferWhenCancelAllWaitingHolds %]and Transfer [% END 
%]All
and
   msgid Cancel hold and return to : [% overloo.branchname %]


7) Exclude URLs. Those are not content that should be translatable.


--
Ystävällisin terveisin

Pasi Kallinen
ICT-asiantuntija

p. 0400-139747
pasi.kalli...@pttk.fi
Länsikatu 15
80110  Joensuu

Pohjois-Karjalan Tietotekniikkakeskus Oy - www.pttk.fi
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/


Re: [Koha-devel] Translation annoyances

2013-12-01 Thread Chris Cormack
* Kallinen Pasi (pasi.kalli...@pttk.fi) wrote:
 Hello.
 
 I've been translating Koha to Finnish for a bit, and I'm really starting to 
 hate some of the automagically generated msgid's.
 
 1) String concatenation is BAD.
 For example, this line of code:
var disabledForCurrent = _(Disabled for) + ' ' + $branch;
 turns into this translatable string:
msgid Disabled for
 
 For some languages this is very hard to translate without sounding stupid or 
 just plain wrong. jQuery has some string placeholder support for javascript, 
 so Koha really should be using those instead!
 The example above would turn into:
 
var disabledForCurrent = _(Disabled for {0});
msgid Disabled for {0}
 
 
 2) Consistency would be good.
msgid EAN:
msgid EAN: 
msgid EAN :
 
 
 3) Sentences should not be cut in pieces.
msgid Please
msgid upload
msgid one.
 
 The upload-text is a link in the sentence. Ideally this should be:
msgid Please %supload%s one.
 
 
 4) Is it a verb or a noun?
msgid Copy
 
 
 5) The wiki-like help texts should be in separate po-file. The help texts 
 inflate the staff UI po-file immensely, and the help translation is not quite 
 as critical as the UI. Having all the help texts interspersed between all the 
 actually important strings is irritating.
 
 
 6) Translation is not programming. Replace all Template Toolkit code with 
 placeholders.
 For example
msgid Cancel [% IF TransferWhenCancelAllWaitingHolds %]and Transfer [% 
 END %]All
 and
msgid Cancel hold and return to : [% overloo.branchname %]
 
 
 7) Exclude URLs. Those are not content that should be translatable.
 

Great ideas, 

I will be more than happy to do sign off on your patches implementing
them.

Chris

-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/


Re: [Koha-devel] Translation annoyances

2013-12-01 Thread Anthony Mao
Hi Kallinen,

I can not but agree with you.

2013/12/2 Kallinen Pasi pasi.kalli...@pttk.fi:
 Hello.

 I've been translating Koha to Finnish for a bit, and I'm really starting to 
 hate some of the automagically generated msgid's.

 1) String concatenation is BAD.
 For example, this line of code:
var disabledForCurrent = _(Disabled for) + ' ' + $branch;
 turns into this translatable string:
msgid Disabled for

 For some languages this is very hard to translate without sounding stupid or 
 just plain wrong. jQuery has some string placeholder support for javascript, 
 so Koha really should be using those instead!
 The example above would turn into:

var disabledForCurrent = _(Disabled for {0});
msgid Disabled for {0}


 2) Consistency would be good.
msgid EAN:
msgid EAN: 
msgid EAN :


 3) Sentences should not be cut in pieces.
msgid Please
msgid upload
msgid one.

 The upload-text is a link in the sentence. Ideally this should be:
msgid Please %supload%s one.


 4) Is it a verb or a noun?
msgid Copy


 5) The wiki-like help texts should be in separate po-file. The help texts 
 inflate the staff UI po-file immensely, and the help translation is not quite 
 as critical as the UI. Having all the help texts interspersed between all the 
 actually important strings is irritating.


 6) Translation is not programming. Replace all Template Toolkit code with 
 placeholders.
 For example
msgid Cancel [% IF TransferWhenCancelAllWaitingHolds %]and Transfer [% 
 END %]All
 and
msgid Cancel hold and return to : [% overloo.branchname %]


 7) Exclude URLs. Those are not content that should be translatable.


 --
 Ystävällisin terveisin

 Pasi Kallinen
 ICT-asiantuntija

 p. 0400-139747
 pasi.kalli...@pttk.fi
 Länsikatu 15
 80110  Joensuu

 Pohjois-Karjalan Tietotekniikkakeskus Oy - www.pttk.fi
 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/



-- 
Wishing you all the best. . . .


Anthony Mao 毛慶禎
+886 2 29052334 (voice)
+ 886 2 29017405 (FAX)
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Translation Manager for 3.14

2013-05-06 Thread Bernardo Gonzalez Kriegel
Hi all,
I'm so sorry to have missed the meeting, my apologies.

Anyway, I'm glad to have been elected, and expect to a do good
job at that post.

My sincere thanks for the opportunity,
Bernardo

-- 
Bernardo Gonzalez Kriegel
bgkrie...@gmail.com
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Translation Manager for 3.14

2013-05-06 Thread Liz Rea
Hi Bernardo,

I will take this as acceptance of the position, and update the wiki
accordingly.

Thanks so much for volunteering, and for your service.

Liz Rea
On 07/05/13 16:00, Bernardo Gonzalez Kriegel wrote:
 Hi all,
 I'm so sorry to have missed the meeting, my apologies.

 Anyway, I'm glad to have been elected, and expect to a do good
 job at that post.

 My sincere thanks for the opportunity,
 Bernardo



 ___
 Koha-devel mailing list
 Koha-devel@lists.koha-community.org
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 website : http://www.koha-community.org/
 git : http://git.koha-community.org/
 bugs : http://bugs.koha-community.org/

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Translation manager for v3.14

2013-04-20 Thread Bernardo Gonzalez Kriegel
Hi all,

On Fri, Apr 19, 2013 at 5:29 PM, D Ruth Bavousett dru...@gmail.com wrote:
  Given my situation, and after discussing the matter with Galen, I've
 decided
  that my term as Translation Manager should end after the release of 3.12
  next month.  I'll be happy to help hand off matters, and will update the
  wiki page to reflect current processes, in order to make for a smooth
  transition, once someone is elected.


Ruth, as many others have expressed , is sad news that you need to leave.
Also, we all expect that you remain involved as far as you can.


 As far as the election is concerned, I suggest that folks interested
 in being the Translation Manager for 3.14 submit their proposals in
 time for discussion to take place at the next general IRC meeting,
 which is scheduled for 7 May 2013.  In case there isn't a quick
 consensus achieved at that meeting, I further suggest that the vote
 for TM be held at the June meeting.


About the role of TM, I want to volunteer for the post.
I currently run the site dedicated to the translation of the manual,
also using Pootle. Certainly is a small site, there are only
2 active translations (Arabic and Spanish), but that gives me
a glimpse of the tasks involved.

I know there are some ideas about migrating out of Pootle to
better tools, but I am also appointed as RM for 3.10.x,
for that reason I prefer not to change our tools at this moment.

So, I think I can deal with both posts but without changes in current
infrastructure; or someone could take RM 3.10.x, I have no problem
to step back; or we found another volunteer for TM with more time.

As far as I know, there is no need to relocate current translate.k-c
server, anyone interested could use it without problem.

Best regards,
Bernardo
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] Translation manager for v3.14

2013-04-19 Thread D Ruth Bavousett
To my friends around the world in the Koha community:

When the election cycle for v3.14 was ramping up, I had just recently left
ByWater and moved to Houston for a new job.  My hope was that enough of my
time would be freed up for me to spend more time on translation-related
developments when things had settled down some.

That has, unfortunately, not been the case, and I'm just barely able to
keep things afloat with keeping the Pootle server happy! Frustrations with
that have persisted, and I so appreciate the patience of all the
translators, the RM, and the RMaint as I've struggled to keep things afloat
during this stressful period.  I also want to thank Katrin for loads of
help with the role that she has freely given while I've been in and out.

Given my situation, and after discussing the matter with Galen, I've
decided that my term as Translation Manager should end after the release of
3.12 next month.  I'll be happy to help hand off matters, and will update
the wiki page to reflect current processes, in order to make for a smooth
transition, once someone is elected.

I'll still be around some; several of the people that I am closest to are
Koha people, and that doesn't change. I just need some uncommitted time to
get my home and life in a little better order.

With sincerest regards,

D Ruth Bavousett
Translation Manager, Koha v3.12
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Translation manager for v3.14

2013-04-19 Thread Galen Charlton
Hi,

On Fri, Apr 19, 2013 at 5:29 PM, D Ruth Bavousett dru...@gmail.com wrote:
 Given my situation, and after discussing the matter with Galen, I've decided
 that my term as Translation Manager should end after the release of 3.12
 next month.  I'll be happy to help hand off matters, and will update the
 wiki page to reflect current processes, in order to make for a smooth
 transition, once someone is elected.

First, let me thank you for a job well done.  Also, thanks for knowing
when circumstances dictate that somebody else will have to try to fill
your shoes.  I am also happy to hear that you'll still be around.

As far as the election is concerned, I suggest that folks interested
in being the Translation Manager for 3.14 submit their proposals in
time for discussion to take place at the next general IRC meeting,
which is scheduled for 7 May 2013.  In case there isn't a quick
consensus achieved at that meeting, I further suggest that the vote
for TM be held at the June meeting.

Regards,

Galen
--
Galen Charlton
Manager of Implementation
Equinox Software, Inc. / The Open Source Experts
email:  g...@esilibrary.com
direct: +1 770-709-5581
cell:   +1 404-984-4366
skype:  gmcharlt
web:http://www.esilibrary.com/
Supporting Koha and Evergreen: http://koha-community.org 
http://evergreen-ils.org
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/


[Koha-devel] Translation of KOCT (Koha Offline Circulation Tool)

2012-07-16 Thread Paul Poulain
Hi,

BibLibre is working on a new version of KOCT
(http://wiki.koha-community.org/wiki/Offline_circulation_firefox_plugin)
that enable translation of the plugin.

We are currently testing the translation to french.
Once we're sure things are OK, I'll send here some explanations and
example file for those who want to translate the plugin in their own
language.
There are only a few strings (less than a dozen)

Stay tuned.
-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/


[Koha-devel] Translation question

2012-03-22 Thread Marcel de Rooy
Hi all,



Sorry for cross-posting ;) Something in between..



Does anyone of you foresee problems with translating a construction like this 
one just as in the sysprefs?



Allow/Do not allow (in combo)  -- followed by text like: -- anyone to delete 
items from the list

See screenshot:



http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=8467





Thanks for your attention.



Marcel
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Translation bug 6278 (XSLT subfield select pars)

2011-04-28 Thread Frédéric DEMIANS

 Since at is not a word here, but just two subfields a and t, they
 should not have been translated of course. Incidentally, bij is the
 Dutch translation of the English at. The word gets translated and so
 subfields a and t are replaced by b, i and j. In most cases resulting
 in no information.

That's why the context (the comment for translator) is so important. A
translator, knowing that 'at' comes from a .xsl file should suspect that
it isn't a isolate word but a parameter, and taking a look at the XSL
file he could see that the text comes from a XSLT template parameter.

I agree that at the first place, there is something wrong in our XSL
file strings extractor. There are also shortcomings in the other file
types strings extractors. The .po files are huge for some of those
reasons. We can discuss how to improve Koha localization/translation
process. The goal could be to: simplify translators work, improve string
extraction, improve Koha 'localizability', reduce .po files size.

For XSL files, we could (1) explicitly mark text to be translated or
(2) pick them up from an external XML file (performance warning).

Regards,
--
Frédéric DEMIANS
http://www.tamil.fr/u/fdemians.html

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/