Re: webmin translations status

--===============0698222488==
Content-Type: multipart/signed; boundary="nextPart1282421.4RrKv2rPu3";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1282421.4RrKv2rPu3
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 12 October 2005 02:50, Jamie Cameron wrote:
> On Tue, 2005-10-11 at 23:34, Wanderlei Antonio Cavassin wrote:
> > Em Tue, Oct 11, 2005 at 03:12:11PM +0200, Martin Mewes escreveu:
> > > Hi all,
> > >
> > > Wanderlei Antonio Cavassin <cavassin-4qZELD6FgxhWk0Htik3J/[email protected]> wrote:
> > > > Em Tue, Oct 11, 2005 at 12:48:00PM +0000, Jamie Cameron escreveu:
> > > > > However, perhaps some simple programs could be written to convert
> > > > > between Webmin's format and the .po file format? That would allow
> > > > > other translation programs to be used..
> > > >
> > > > Exactaly. We already have that scripts (and skolelinux have as
> > > > well). So we'll continue using them, mainly for pt_BR and fr
> > > > translations.
> > > >
> > > > The main question is if we should add these PO files in the webmin
> > > > translation project itself.
> > >
> > > Well I think that including more files to the webmin repository would
> > > be useless. The main goal must be that updated translations to webmin
> > > must be in $format to be easily included for Jamie.
> > >
> > > As long as Webmin/Usermin/Virtualmin does not directly support
> > > po-files I could think of something that $official_po_repo is
> > > converting the lang-files once a time and send them to Jamie in the
> > > format he needs?
> >
> > I was not clear enough. I meant to make the PO files available
> > for translators in webmin web site. An i18n coordinator will have to
> > convert them back to be included for Jamie.
> >
> > So the translator will have both options: to use PO files or to stay
> > with old way. IMHO, PO format will help to attract more translators,
> > since many projects use it.
>
> I could certainly add links to those files from the Webmin site.
> However, I would strongly recommend using only Webmin's native language
> file format wherever possible, as you are likely to get out of sync when
> converting to and from the .po format ..

When I was working on po-webmin for Skolelinux I tested it by running it on=
=20
the source of all webmin modules present in Debian unstable.  At that point=
=20
in time there were virtually no translations present that were in sync,=20
most had a combination of the following problems:
=2D message codes in the english master that weren't in the translation
=2D message codes in the translation that were no longer in the english mas=
ter
=2D the same message code multiple times in the translation with differing=
=20
translations

There's some webmin specific tools mentioned at [1] to help with this.=20
However I'd wager that most translators don't know about them as those=20
tools aren't even mentioned at [2] and the former is the documentation for=
=20
writing a new module (which a not-to-technical translator, i.e. most,=20
definately will not think to look at).

The po mechanism on the other hand is well known and simple, it boiles down=
=20
to: look at the date the po template (english masterfile) was last=20
generated, if that's newer then the one you used (date of generation of the=
=20
po-file used for the translation is documented in the header of the=20
translation) update with the new one)

P.S. [1] should really be linked from [2] to at least make it easier to find

[1] http://www.webmin.com/modules.html#newlang (by the way the link to the=
=20
langdiff seems to be dead)
[2] http://www.webmin.com/mailing-trans.html
=2D-=20
cobaco (aka Bart Cornelis):
    Co=F6rdinator Belgisch Skolelinux team
    Co=F6rdinator Nederlandse Skolelinux vertaling

--nextPart1282421.4RrKv2rPu3
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBDTMg05ihPJ4ZiSrsRAjR3AKCVF78HusXL4Xi0tr8ICMY/4VtG5wCdEOzP
c3PXL8rFazAhr6KpIf7BROA=
=z2bD
-----END PGP SIGNATURE-----

--nextPart1282421.4RrKv2rPu3--

--===============0698222488==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
webmin-trans mailing list
[email protected]
http://mailman.mamemu.de/mailman/listinfo/webmin-trans

--===============0698222488==--