Czech NLS
Hi,
the patch contains complete messages transaltion of:
libpq
pg_controldata
pg_resetxlog
psql
pg_dump
pgscripts
Beacuse this patch is a little greater than pgsql-patches list limit
I put it to my FTP instead to mail attachement. Please, load it from
following URL:
ftp://ftp2.zf.jcu.cz/users/zakkr/pg/nls-cs-07222003.patch.gz
Thanks,
Karel
PS. Is pgsql-patches list limit 40Kb?
--
Karel Zak <zakkr@zf.jcu.cz>
http://home.zf.jcu.cz/~zakkr/
On Wed, Jul 23, 2003 at 11:48:19AM +0200, Peter Eisentraut wrote:
Karel Zak writes:
the patch contains complete messages transaltion of:
Installed. Nice work.
Thanks. What time will "freeze" backend messages? I think after beta
release.
Karel
--
Karel Zak <zakkr@zf.jcu.cz>
http://home.zf.jcu.cz/~zakkr/
Import Notes
Reply to msg id not found: Pine.LNX.4.56.0307231131080.1649@krusty.credativ.de
Karel Zak writes:
the patch contains complete messages transaltion of:
Installed. Nice work.
--
Peter Eisentraut peter_e@gmx.net
Karel Zak writes:
Thanks. What time will "freeze" backend messages? I think after beta
release.
Typically (meaning in other large projects that care about these things),
a "string freeze" is called much later during the release process, about
2/3 of the way between what we call start of beta and the final release.
Translation updates are then accepted up to about the time of the first
release candidates.
Note that now there is a message style guide, so we can easily designate
any misworded message a bug and change it during beta. ;-)
What I can tell you is that I just committed a batch of such message
changes (affecting all message catalogs except libpq and backend), and I
hope that that will be the last major such change in the affected programs
until release. Most of the changes were in punctuation, so you don't have
to start all over.
--
Peter Eisentraut peter_e@gmx.net
On Wed, Jul 23, 2003 at 12:42:36PM +0200, Peter Eisentraut wrote:
Karel Zak writes:
Thanks. What time will "freeze" backend messages? I think after beta
release.Typically (meaning in other large projects that care about these things),
a "string freeze" is called much later during the release process, about
2/3 of the way between what we call start of beta and the final release.
Translation updates are then accepted up to about the time of the first
release candidates.
OK.
What I can tell you is that I just committed a batch of such message
changes (affecting all message catalogs except libpq and backend), and I
hope that that will be the last major such change in the affected programs
until release. Most of the changes were in punctuation, so you don't have
to start all over.
I think gettext system is good designed for strings updates and if
somebody use cool tool like "poedit" it's simple found changes
and fix updated .po files.
BTW, small suggestion - maybe will good add to your NLS page
information about ispell .po files checking by "pospell" tool
from "spellutils" package.
pospell -n file.po -p ispell -- -d langname %f
Karel
--
Karel Zak <zakkr@zf.jcu.cz>
http://home.zf.jcu.cz/~zakkr/
Karel Zak <zakkr@zf.jcu.cz> writes:
Thanks. What time will "freeze" backend messages? I think after beta
release.
I'm hoping to have the bulk of the backend message changes done by the
time we go beta (now scheduled for Monday). So you should be able to
start on translation work after that. There will doubtless be some
further tweaking, as Peter says.
regards, tom lane