Hi, I am glad to announce String Freeze for 3.0.1. Translators, you have 3 week time for translations. It should be only differences from 3.0.0 But strings Normalization sometimes did many tiny changes. Sorry about that. Chris will tell you more about Pootle site that will allow good translations. Let me know if you encounter any problem. Hopefully, christmas will bring us 3.0.1 release. ;) -- Henri-Damien LAURENT
On Tue, Oct 28, 2008 at 4:57 AM, Chris Cormack <chris@bigballofwax.co.nz> wrote:
That sounds like a great idea, Ill make sure the new translation system is all up and ready for november 15th, with automatic template generation going.
More or less when this will be ready? On Thu, Sep 18, 2008 at 4:56 AM, <paul.poulain@free.fr> wrote:
koha.org is moving to a new platform (zope), that will give tools to translate the manual. In the meantime, no specific project.
More or less when this will be ready? The Spanish-speaking community has many people who offer to translate both Koha manual and templates, and this tools would be *very* useful !!
On Wed, Nov 26, 2008 at 2:39 AM, Pablo A. Bianchi <pbianchi@fi.uba.ar> wrote:
On Tue, Oct 28, 2008 at 4:57 AM, Chris Cormack <chris@bigballofwax.co.nz> wrote:
That sounds like a great idea, Ill make sure the new translation system is all up and ready for november 15th, with automatic template generation going.
More or less when this will be ready?
Im just waiting on some firewall changes where its being hosted, then this will be ready to go. So I hope very soon. Chris
On Tue, Nov 25, 2008 at 3:23 PM, Chris Cormack <chris@bigballofwax.co.nz> wrote:
On Wed, Nov 26, 2008 at 2:39 AM, Pablo A. Bianchi <pbianchi@fi.uba.ar> wrote:
On Tue, Oct 28, 2008 at 4:57 AM, Chris Cormack <chris@bigballofwax.co.nz> wrote:
That sounds like a great idea, Ill make sure the new translation system is all up and ready for november 15th, with automatic template generation going.
More or less when this will be ready?
Im just waiting on some firewall changes where its being hosted, then this will be ready to go. So I hope very soon.
Great!! I've great expectations! So, now that Koha 3 was released more than three months ago: Does anyone know more or less when the koha.org site will up and running with Plone!? I totally agree with Nicolas Morin, Roberto Allende, Paul Poulain, Rachel Hamilton-Williams, and all those who think issues should be divided, we need Plone's functionalities, that is far more important than the template issue, and should not stop it. Cheers, Pablo PS: Related posts: On Thu, Sep 18, 2008 at 4:56 AM, <paul.poulain@free.fr> wrote:
koha.org is moving to a new platform (zope), that will give tools to translate the manual. In the meantime, no specific project.
On Mon, Jul 28, 2008 at 8:32 AM, Joshua Ferraro <jmf@liblime.com> wrote:
We're still planning to proceed with Plone, but we've had other priorities (like the release of Koha 3.0) that have prevented us from focusing our attention on what to do with the koha.org Plone migration.
Some have suggested we switch to Plone and just use the standard Plone template; others have suggested we pick one of the submitted designs even though we didn't like them, just to move things forward; others have suggested we run another contest or perhaps just select someone to pay to design a koha.org site that the community is happy with. So there are lots of ideas, but I think most of us have been too busy to execute them.
So Koha community, how shall we proceed?
On Tue, Jul 29, 2008 at 3:45 AM, Nicolas Morin <nicolas.morin@biblibre.com> wrote:
On Mon, Jul 28, 2008 at 1:32 PM, Joshua Ferraro <jmf@liblime.com> wrote:
Some have suggested we switch to Plone and just use the standard Plone template;
That's my vote: we need the functionalities sooner rather than later, especialy as far as the Koha doc for version 3 is concerned. I agree with Roberto that the issues should be divided: the problems with the proposed Plone templates should not stop us from moving forward with the plan to switch to Plone.
On Thu, Aug 14, 2008 at 10:45 PM, Rachel Hamilton-Williams <rachel@katipo.co.nz> wrote:
Is it possible to basically put the current design into Plone? I had thought people were generally happy with the current look, it's just the CMS functionality that's missing.
Henri-Damien LAURENT skrev:
Hi, I am glad to announce String Freeze for 3.0.1. Translators, you have 3 week time for translations. It should be only differences from 3.0.0 But strings Normalization sometimes did many tiny changes. Sorry about that.
Chris will tell you more about Pootle site that will allow good translations. Let me know if you encounter any problem. Hopefully, christmas will bring us 3.0.1 release. ;)
Nice, thank you! We are working on the Norwegian translation to complete it. I tried to merge our po-files with the ones in git, are those updated to 3.0.1? It brought many changes, so I hope the very latest string changes are also there, but the date for the last change was in august, therefore I was a bit puzzled. Best regards Axel Bojer
Hi to all, At 22.55 24/11/2008, Henri-Damien LAURENT wrote:
Hi, I am glad to announce String Freeze for 3.0.1.
we are starting to update our transaltion with the present version of 3.0.x The git web repository is http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=shortlog;h=3.0.x ? The last update was at 2008-10-28 ? Bye Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)
Hi, Henri-Damien LAURENT wrote:
Hi, I am glad to announce String Freeze for 3.0.1. Translators, you have 3 week time for translations. It should be only differences from 3.0.0 But strings Normalization sometimes did many tiny changes. Sorry about that.
Chris will tell you more about Pootle site that will allow good translations. Let me know if you encounter any problem. Hopefully, christmas will bring us 3.0.1 release. ;)
Can you consider the last three patches from my git tree in the branch wip-for-upstream: http://git.debian.org/?p=collab-maint/koha.git;a=shortlog;h=refs/heads/wip-f... I would be glad if they are applied on koha master and on koha 3.0.x branches. Here is a brief description of these patches: - "Use relative path to avoid people dependent paths": misc/translator/install.pl and misc/translator/update.pl uses absolute paths depending on one particular developer (/home/jmf/kohaclone for example) - "Force ordering of files when creating/updating po files": This avoid to generate false differences in po files due to different file ordering on different machines - "Remove temporary files when updating po files" Do not let temporary files on the filesystem after regenerating translated files The aim of these patches is to allow to regenerate translated files at Debian build-package time. This will allow to correct (with a new Debian package with a patch) a translation error without waiting for a new upstream release of koha fixing this error. Best regards, Vincent -- Vincent Danjean GPG key ID 0x9D025E87 vdanjean@debian.org GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87 Unofficial pacakges: http://www-id.imag.fr/~danjean/deb.html#package APT repo: deb http://perso.debian.org/~vdanjean/debian unstable main
On Mon, Dec 8, 2008 at 6:42 AM, Vincent Danjean <vdanjean.ml@free.fr> wrote:
Hi,
Henri-Damien LAURENT wrote:
Hi, I am glad to announce String Freeze for 3.0.1. Translators, you have 3 week time for translations. It should be only differences from 3.0.0 But strings Normalization sometimes did many tiny changes. Sorry about that.
Chris will tell you more about Pootle site that will allow good translations. Let me know if you encounter any problem. Hopefully, christmas will bring us 3.0.1 release. ;)
Can you consider the last three patches from my git tree in the branch wip-for-upstream: http://git.debian.org/?p=collab-maint/koha.git;a=shortlog;h=refs/heads/wip-f... I would be glad if they are applied on koha master and on koha 3.0.x branches. Here is a brief description of these patches: - "Use relative path to avoid people dependent paths": misc/translator/install.pl and misc/translator/update.pl uses absolute paths depending on one particular developer (/home/jmf/kohaclone for example) - "Force ordering of files when creating/updating po files": This avoid to generate false differences in po files due to different file ordering on different machines - "Remove temporary files when updating po files" Do not let temporary files on the filesystem after regenerating translated files
The aim of these patches is to allow to regenerate translated files at Debian build-package time. This will allow to correct (with a new Debian package with a patch) a translation error without waiting for a new upstream release of koha fixing this error.
Those patches look fine to me. I also really like the idea of being able to correct the translation errors :) Chris
participants (6)
-
Axel Bojer -
Chris Cormack -
Henri-Damien LAURENT -
Pablo A. Bianchi -
Vincent Danjean -
Zeno Tajoli