[i18n] Danish translations of forwards and vacation

[Jose Carlos Pereira]

More or less my  thoughts (ie, to translate you should not  need to be a
programing "guru").

Maybe a  small text explaining  how translate.php works would  make life
much easier (translate.php does make your life easier ;)).


Another thing that would help, direct links to translation help files:

  eg:
        http://www.horde.org/source/contribute.php
           A separate section for translations
           (link to latest /horde/po/README ?)

        http://lists.horde.org/mailman/listinfo/i18n
           A link to afore mentioned link

An example of a small text (my quick guide for future translations)
(maybe suggestion should be sent to  horde-doc list?)

 ** Simple steps to update a translation ** 

 BASE     =       base PATH where horde is installed
 ll_CC.po =       gettext language file
                ( ll: two letter language code 
                  CC: two letter country code
                  ex de_DE.po, fr.FR)

   + Update .po files with new strings
           cd BASE
           ./translation.php update -m horde -l ll_CC
           ./translation.php update -m imp   -l ll_CC
           ./translation.php update -m turba -l ll_CC

           OR all packages in one go

           ./translation.php update -l ll_CC

   + create a compendium file (do this only once)
        ./translation.php compendium -l ll_CC

        (creates compendium file.
         create it and ignore it)

   + edit individual files... ll_CC.po
        (delete fuzzy comment entries after correcting entries)
        ex BASE/po/ll_CC.po
           BASE/imp/po/ll_CC.po
           BASE/turba/po/ll_CC.po
   
   + generate the system translation binaries
        cd BASE
        ./translation.php make -m horde -l ll_CC
        ./translation.php make -m imp -l ll_CC
        ./translation.php make -m turba -l ll_CC

        OR all packages:
        ./translation.php make -l ll_CC

        (this generates .mo files into correct system dir.
        ex:
                BASE/locale/ll_CC/LC_MESSAGES/horde.mo
                BASE/imp/locale/ll_CC/LC_MESSAGES/imp.mo
                ...

   + restart webserver
        (ex apachectl restart)

   + send individual corrected .po files to 
        i18n at lists.horde.org
 

Off  course, this  would help  guys like  me that  don't really  want to
understand how it works, just want to get the job done quickly. :)

This would have helped me quite a bit.


regards
-- 
Reality is just a crutch for people who can't handle science fiction.
---
Jose' Carlos


On Tue, 30 Mar 2004, Espen Jürgensen wrote:

> tir, 2004-03-30 kl. 22:51 skrev Jan Schneider:
> 
> > >   Very nice technically, and great when it works. But it took me 2-3
> > > hours to get it running, which is a bit daunting for just a small
> > > translation. Translators really only need and want to translate, not
> > > install and operate the newest Horde & PEAR (and even gettext). A nice
> > 
> > Can you be more specific what problems exactly you had?
> > 
> 
> Certainly. A short account of my troubles:
> 
> 1) Locales: The test-server which runs Horde HEAD didn't have the
> appropriate Danish locale. So first I had to get that up and running,
> since I believe translation.php required it.
> 2) PEAR: The server didn't have Console_Table and File_Find. The server
> is Debian/unstable, and I don't like installing stuff without apt... it
> gets too messy. Downloading a .tar.gz and installing is out of the
> question. Didn't know pear could download, install and maintain stuff
> updated by itself, which is more acceptable. Took a while to figure that
> one out.
> 3) Gettext: I tested on commandline with 'gettext -V', which said it was
> a good version. But translation.php complains that there is no
> 'msgattrib'. Haven't got a clue what it is. And I had gettext, right?
> Think again, I had the Debian package gettext-base, not the full
> gettext. This one cost me another half hour of frustration.
> 
> Granted, most of the problems were just caused by my own lack of
> knowledge concerning gettext and PEAR. That's why I wasn't so specific
> about why it took so long. I just wanted to warn you that perhaps you
> are creating a barrier for the less patient translators.
> 
> Espen
> 
> PS: I sent this to i18n, I suppose it's more relevant there.
> 
>