Lao team
Hi, Hope all is well. I was wondering if you could re-activate Lao team. Some of my members have been translating GNOME under Ubuntu but I told them to hold off and do it from GNOME so the files can be upstream later on. I check live.gnome and see that our Lao team has been de-activated thus I would like to ask to re-active and let us translate the remaining files. Also please tell me the status of my SVN account, I also need to activate. Info: Name: Anousak Anthony Souphavanh Email: [EMAIL PROTECTED] Team: Lao Gnome Country: Laos Link: http://sourceforge.net/laofoss Many thanks for help. Cheers, -- Anousak (Anthony) Souphavanh "Small can make a big impact" ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
New team for [Lao] ([lo])" as the subject
My name is Outhai SAIOUDOM. i'm trying to look for Lao team on Gnome but There is no team for Lao language is listed in GNOME I18n site and I would like to request for new team, I have a small team working with translating Ubuntu, some friends at National University of Laos and some volunteers. My Email is : [EMAIL PROTECTED] The url is a part of Lao Open Source ( Lao Ubuntu ) initiative at: http://www.laoubuntu.com Regard Os -- Os555 www.laoubuntu.com ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: How do I get Tasque added to Damned Lies?
Thanks! Gil Forcada wrote: > Hi! > > Already added :) > > Cheers, > > El dt 21 de 10 de 2008 a les 08:29 -0700, en/na Sandy Armstrong va > escriure: > >> Hi Wonderful Folks, >> >> How do I get Tasque [1][2] added to Damned Lies? Seems like it should >> maybe be in the gnome-extras category? This would really help out our >> translators. >> >> Thanks, >> Sandy >> >> [1] http://live.gnome.org/Tasque >> [2] http://svn.gnome.org/svn/tasque/trunk >> ___ >> gnome-i18n mailing list >> gnome-i18n@gnome.org >> http://mail.gnome.org/mailman/listinfo/gnome-i18n >> ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: msgctxt conversion for 2.26 ?
"Kenneth Nielsen" <[EMAIL PROTECTED]>, Tue, 28 Oct 2008 22:26:09 +0100: > 2008/10/28 Petr Kovar <[EMAIL PROTECTED]>: (...) > > That's nice, but still, the problem is current from the moment the first > > string migrates. And that was done some months ago. So many translators > > got a problem now. But the most interesting part is what the > > MsgctxtMigration page says: > > > > "Warning: > > This is only a proposal at this time, and not approved for project-wide > > application. This should not be applied before being officially turned > > into a GNOME Goal." > > > > Oh really? Does anybody look at that? Does anybody give a damn about > > that? Just wondering... ;-) > > Yes I remember you objected back then and still someone decided to > test the transition, but now however, we _are_ discussing the > possibility to make it an official GNOME goal! Any input in _that_ > subject ;) Well, then I misunderstood the thread. So please, could this what I might call, say, a discreditable situation be make an official GNOME goal finally? Because the migration is already happening for some time, and the warning notice seems like a confirmation that the current i18n team work is, with all due respect, weak, irresolute, and generally gives inconvincible results. Thus please, any senior member, do something with that. Thanks. Regards, Petr Kovar ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: msgctxt conversion for 2.26 ?
2008/10/28 Petr Kovar <[EMAIL PROTECTED]>: > Hi! > > "Kenneth Nielsen" <[EMAIL PROTECTED]>, Mon, 27 Oct 2008 12:34:54 +0100: > >> 2008/10/27 Matthias Clasen <[EMAIL PROTECTED]>: >> > This was discussed at several points in the past, most recently in >> > August. Is http://live.gnome.org/GnomeGoals/MsgctxtMigration something >> > that we should target for Gnome 2.26 ? >> >> I definitely think so, the sooner we get rid of the "|" source of >> errors the better. Besides, if I remember correctly the only objection >> to fast integration of this, was that some popular translation tools >> didn't yet support it. > > Correct. It was (and unfortunately still is) Poedit, to be specific. > Thus, as I believe, a well known and widely used l10n tool among the GNOME > translators. > >> Deciding on it now will give the developers on >> those projects a good 4 months to implement it, make a new release and >> have this new version find its way into the repos of the different >> distributions, that is not an abundance of time, but it should be >> do-able. > > That's nice, but still, the problem is current from the moment the first > string migrates. And that was done some months ago. So many translators got > a problem now. But the most interesting part is what the MsgctxtMigration > page says: > > "Warning: > This is only a proposal at this time, and not approved for project-wide > application. This should not be applied before being officially turned into > a GNOME Goal." > > Oh really? Does anybody look at that? Does anybody give a damn about that? > Just wondering... ;-) Yes I remember you objected back then and still someone decided to test the transition, but now however, we _are_ discussing the possibility to make it an official GNOME goal! Any input in _that_ subject ;) Regards Kenneth Nielsen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[Bug 363398] can not display Lao character
If you have any questions why you received this email, please see the text at the end of this email. Replies to this email are NOT read, please see the text at the end of this email. You can add comments to this bug at: http://bugzilla.gnome.org/show_bug.cgi?id=363398 l10n | other | Ver: unspecified Claude Paroz changed: What|Removed |Added CC||[EMAIL PROTECTED] Status|UNCONFIRMED |RESOLVED Resolution||OBSOLETE --- Comment #4 from Claude Paroz 2008-10-28 21:13 UTC --- Thanks Theppitak for the feedback. -- See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received this email, why you can't respond via email, how to stop receiving emails (or reduce the number you receive), and how to contact someone if you are having problems with the system. You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=363398. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: msgctxt conversion for 2.26 ?
On Tue, Oct 28, 2008 at 01:49:47PM -0400, Rodney Dawes wrote:
> On Tue, 2008-10-28 at 08:16 +0100, Claude Paroz wrote:
> > Le lundi 27 octobre 2008 ?? 17:11 -0400, Daniel Macks a ??crit :
> > > Can configure.{ac,in} do a version-check for the new gettext when
> > > packages start requiring it? I don't know enough of gettext's autoconf
> > > macros so I don't know if this is an actual feature-request or just a
> > > friendly reminder:) But anyway, gtkhtml-3.24.0 already uses msgctxt
> > > but there's no indication that a new gettext version is required. On
> > > my machine with gettext-0.14.5, I got a cryptic build crash rather
> > > than a clear ./configure "checking for gettext>=FOO... no" failure.
> >
> > I don't know if intltool checks for a specific gettext version. CC'd to
> > dobey as he should be able to answer.
>
> It just checks for gnu gettext. All it calls is AC_PATH_PROG(PROGRAM,
> program) to find the tools, and then calls some of the commands with
> --version to check that they are actually GNU tools. If your error is
> "checking for gettext >= FOO... no" then I would guess the app itself
> is checking for the tools separately, and that is failing. The
> intltool.m4 doesn't have "FOO" in it anywhere.
Sorry, you mis-interpretted most of my comment. "FOO" is just a
placeholder for "whaver minimum version of gettext is needed to
support whatever new gettext feature (for example, msgctxt) is used".
And that's not what the error *is*, it's what the error *should be* if
we want to be helpful to people who are compiling the sources.
dan
--
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: msgctxt conversion for 2.26 ?
On Tue, 2008-10-28 at 08:16 +0100, Claude Paroz wrote:
> Le lundi 27 octobre 2008 à 17:11 -0400, Daniel Macks a écrit :
> > Can configure.{ac,in} do a version-check for the new gettext when
> > packages start requiring it? I don't know enough of gettext's autoconf
> > macros so I don't know if this is an actual feature-request or just a
> > friendly reminder:) But anyway, gtkhtml-3.24.0 already uses msgctxt
> > but there's no indication that a new gettext version is required. On
> > my machine with gettext-0.14.5, I got a cryptic build crash rather
> > than a clear ./configure "checking for gettext>=FOO... no" failure.
>
> I don't know if intltool checks for a specific gettext version. CC'd to
> dobey as he should be able to answer.
It just checks for gnu gettext. All it calls is AC_PATH_PROG(PROGRAM,
program) to find the tools, and then calls some of the commands with
--version to check that they are actually GNU tools. If your error is
"checking for gettext >= FOO... no" then I would guess the app itself
is checking for the tools separately, and that is failing. The
intltool.m4 doesn't have "FOO" in it anywhere.
-- Rodney
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: msgctxt conversion for 2.26 ?
Hi! "Kenneth Nielsen" <[EMAIL PROTECTED]>, Mon, 27 Oct 2008 12:34:54 +0100: > 2008/10/27 Matthias Clasen <[EMAIL PROTECTED]>: > > This was discussed at several points in the past, most recently in > > August. Is http://live.gnome.org/GnomeGoals/MsgctxtMigration something > > that we should target for Gnome 2.26 ? > > I definitely think so, the sooner we get rid of the "|" source of > errors the better. Besides, if I remember correctly the only objection > to fast integration of this, was that some popular translation tools > didn't yet support it. Correct. It was (and unfortunately still is) Poedit, to be specific. Thus, as I believe, a well known and widely used l10n tool among the GNOME translators. > Deciding on it now will give the developers on > those projects a good 4 months to implement it, make a new release and > have this new version find its way into the repos of the different > distributions, that is not an abundance of time, but it should be > do-able. That's nice, but still, the problem is current from the moment the first string migrates. And that was done some months ago. So many translators got a problem now. But the most interesting part is what the MsgctxtMigration page says: "Warning: This is only a proposal at this time, and not approved for project-wide application. This should not be applied before being officially turned into a GNOME Goal." Oh really? Does anybody look at that? Does anybody give a damn about that? Just wondering... ;-) Best, Petr Kovar ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: msgctxt conversion for 2.26 ?
Le lundi 27 octobre 2008 à 17:11 -0400, Daniel Macks a écrit :
> Can configure.{ac,in} do a version-check for the new gettext when
> packages start requiring it? I don't know enough of gettext's autoconf
> macros so I don't know if this is an actual feature-request or just a
> friendly reminder:) But anyway, gtkhtml-3.24.0 already uses msgctxt
> but there's no indication that a new gettext version is required. On
> my machine with gettext-0.14.5, I got a cryptic build crash rather
> than a clear ./configure "checking for gettext>=FOO... no" failure.
I don't know if intltool checks for a specific gettext version. CC'd to
dobey as he should be able to answer.
Claude
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
