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

List of not to translate entries and advises
by Job 13 May '11

13 May '11

Hello All, I am finishing a full translation of Koha for Brazilian Portuguese with revision. Today I finish opac, but, some days ago I read a note about to note translate "at" for an entry. Then some entries need to be revised. Since I am also programmer, I recognise many entries, that I need to be very carefull, but sometimes we need advises. I would like to suggest to a have a public list of advises for translators, about entries that could not be translated and translation with caution. Using a wiki could be better way For example: --- Advises for Opac 3.2 --- entry - note 1500 : "show_contact" could be translated but must maintain underline without accents. 142 : copy only, translation forbidden Thanks Job

2 2

Doubt if I could translate some words
by Job 13 May '11

13 May '11

Hello All, I found some entries in that contain 2 words with underlines like "show_holds", show_contacs" Could I translate these kind of words? Theres same advises? Thanks Job

1 0

Version Control for Pootle.
by Andre Caldas 13 May '11

13 May '11

Hi! It seems Pootle is capable of integrating with version control systems like subversion, etc. Do we have this enabled in http://translate.koha-community.org/ ? If yes, where is it? How do I access it? If no, is it possible to arrange? Is this the right place to ask such a question? :-) The reason I'd be happy to have version control integration is that it is far more productive to work offline. But simply uploading po files to pootle generates problems when two different individuals are editing the same file. Thanks, André Caldas.

3 4

3.2.x String Freeze and Roadmap Update
by Chris Nighswonger 09 May '11

09 May '11

Hi All, We are going to keep with May 15, 2011 for the 3.2.8 release which puts 3.2.x into a string freeze as of today. The 3.2.x branch has quite a few commits since 3.2.7, so this will be an important release. 3.2.x will thaw on May 16. Subsequent 3.2.x releases will be largely dependent upon commits available for back porting and patches submitted directly against the 3.2.x branch. At present, the plan is to support 3.2.x through 3.2.10 *if* there are commits/patches to do so. When we get to 3.2.10 or when it is clear we will not get there, I'll add a monthly IRC meeting agenda item to discuss EOL for the 3.2.x branch. As always: Thanks to all the individuals who have put time, effort, and money into making Koha a great ILS! Kind Regards, Chris Nighswonger 3.2.x/3.4.x Release Maintainer

1 0

Japanese
by Jonathan Lin 30 Apr '11

30 Apr '11

Could we have Japanese translation files for 3.4. Thank you.

1 0

Re: [Koha-translate] [Koha-devel] Translation bug 6278 (XSLT subfield select pars)
by Frédéric DEMIANS 28 Apr '11

28 Apr '11

> 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

1 0

Translation bug 6278 (XSLT subfield select pars)
by Marcel de Rooy 28 Apr '11

28 Apr '11

If your translation file translates the English word "at", please check your XSLT files. See problem below. English XSLT contains constructs as: <xsl:call-template name="subfieldSelect"> <xsl:with-param name="codes">at</xsl:with-param> </xsl:call-template> The translated Dutch XSLT contains: <xsl:call-template name="subfieldSelect"> <xsl:with-param name="codes">bij</xsl:with-param> </xsl:call-template> 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. Note: Occurs 5 times in MARC21slim2OPACDetail.xsl. And affects display of fields 490/8XX, 773, 780/785.

1 0

Re: [Koha-translate] 3.2.x Roadmap Update
by Karen Myers 18 Apr '11

18 Apr '11

Hi all regarding the release of the updated versions, what percentage of a translation has to be complete before it will be included in the release? I seem to recall it was previously 50%? Is that still the case? Karen

1 0

3.2.x Roadmap Update
by Chris Nighswonger 16 Apr '11

16 Apr '11

Hi all, With the release of 3.2.7 and the eminent release of 3.4.0, I want to let the community know what my plans are moving forward. Due to the excellent work during the recent hack-fest sponsored by Biblibre, there were a multitude of bugfixes which did not make it into 3.2.7. My plans are to begin work on getting these backported into the 3.2.x branch over the next week or so. Because there are such a large number, I will be releasing 3.2.8 on May 15, 2011. I had originally intended to go to a bi-monthly release schedule for 3.2.x after the release of 3.2.0. This will still be the case, but will be delayed until the release of 3.2.8. Subsequent 3.2.x releases will take place on the 15th of the month with 3.4.x releases taking place on the 22nd of the month. ***Translators please take especial note of the above dates.*** As long as there are commits to backport to 3.2.x, I will release on a bi-monthly schedule. If there are no commits during a two month period, no release will be made. If you have template related bugfixes you want included in 3.2.x, it will be your responsibility to ensure that they apply correctly to the current 3.2.x branch. With the switch to TT in master, backporting template commits will be nigh impossible. Of course any related underlying logic changes should be applicable to the current 3.2.x branch as well. After the 3.2.10 release, I will add an agenda item for the next monthly IRC to discuss EOL of the 3.2.x branch. The results of that discussion will determine the direction of 3.2.x from that point forward. I plan to handle 3.4.x maintenance in the same fashion as I have handled 3.2.x. If anyone has any suggestions for improvement, please speak up! I'm very open to suggestions, critiques, etc. Thanks to everyone for the hard work being put into Koha lately. Things have moved along at a fantastic rate! Keep up the good work. Kind Regards, Chris Nighswonger Koha 3.2.x/3.4.x Release Maintainer

1 0

Re: [Koha-translate] Koha-translate Digest, Vol 54, Issue 7
by massoud alshareef 15 Apr '11

15 Apr '11

Thank you Ray for sharing your thoughts about the Confluence issue. Sorry, but I felt like my suggestion was offending to the OSS notion, as it seems to preach for a non OSS product in the wrong territory. My apology if I did. I will be extra careful next time before suggesting anything. My suggestion was based on the fact that the latest releases of DSpace and Fedora Commons, both of which are OSS like Koha, are using Confluence for managing and publishing their documentation. I understand now the marketing notion that Altassian is trying to reach new clients through non-profit organizations. However, were DSpace and Fedora communities mislead as well or they are using a different business model than Koha ? Handling R2L orientation with Koha UI required quite some work at all screens, and extending such work to the documentation interface became essential for the Arabic users. This is why I thought it will be awesome if we collectively localize a documentation product, like Confluence if it fits the profile, at the source code level to handle such R2L requirements. Anyway, we will move our Arabization work for Koha (POs and PDFs for documentation) very soon to a Koha wiki location. We may need help from you to complete the movement. Thanks Massoud M. AlShareef, ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 13 Apr 2011 11:09:58 +0100 (BST) > From: MJ Ray <mjr(a)phonecoop.coop> > Subject: Re: [Koha-translate] Koha translation web site > To: koha-translate(a)lists.koha-community.org, ayousef(a)kwareict.com, > amaher(a)kwareict.com > Message-ID: <20110413100958.6A435FA146(a)nail.towers.org.uk> > > massoud alshareef wrote: > > A few days ago I ran into a great tool for document wiki collaboration. > It > > is called Confluence< > http://www.atlassian.com/software/confluence/tour/?gclid=CN7t1ZO3l6gCFY0jfA… > > > > from > > Altassian. It provides an Open Source software > > license< > http://www.atlassian.com/software/views/opensource-license-request.jsp > >when > > used with OSS products like Koha. [...] > > Confluence is a terrible tool and its marketing seems to have mislead > you, because that is not an Open Source software licence. It is a > cost-free proprietary licence they grant if you use Confluence to work > on Free and Open Source Software (FOSS). They give you a licence and > seem to add adverts to the bottom of every page, which I guess helps > to promote their non-FOSS product to FOSS users. > > Also, by using Confluence, you are locking out potential collaborators > who care about freedom and helping Atlassian Pty Ltd to replace open > project communities. Please, I beg you to move your work to a FOSS > wiki as soon as reasonably possible. > > Hope that explains, > -- > MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. > http://koha-community.org supporter, web and LMS developer, statistician. > In My Opinion Only: see http://mjr.towers.org.uk/email.html > Available for hire for Koha work http://www.software.coop/products/koha >

2 1