Claude/i18n team:
This is regarding the outstanding GDM 2.30.3 release.
Just to follow up, is it possible to have someone from the i18n team
programmatically fix the msgid and msgstr strings to remove the
underscore (or the "(_K)" from msgstr for non-Latin languages) for
the following strings:
Kenneth:
Actually, I will back out that fix before releasing the 2.28.0 tarball.
No worries.
Actually, that's not good enough. The string freeze period is, among
other things, there to ensure that translators have something stable
to work on for the last few weeks before release, without stri
Claude:
Actually, I will back out that fix before releasing the 2.28.0 tarball.
No worries.
Brian
On 09/11/09 04:02, Claude Paroz wrote:
Le jeudi 10 septembre 2009 à 01:13 +, GNOME Status Pages a écrit :
This is an automatic notification from status generation scripts on:
http://l10n.gn
Johannes Schmid va
escriure:
Hi!
Although this is really late I guess we need to avoid such a regression
for 2.26 as some people seem to dislike PulseAudio for various reasons.
1 of 2 from i18n.
Regards,
Johannes
Am Freitag, den 06.03.2009, 10:44 -0600 schrieb Brian Cameron:
I would like to
Frederic:
Sorry about this. I just asked for approval. I will backout the
change if I do not get approval. Or, perhaps, I could just make
the tab use the existing "Sound Theme:" string. It's a little
awkward to have the ":" in the tab label, but it is better than not
having the functionality
I would like to request a string freeze change for GNOME 2.26.
Note that if you do not have PulseAudio, that it is now impossible
to configure Sound Themes. This is because the new Sound Theme
configuration has been moved to the new PulseAudio-only
gnome-volume-control. When not using PulseAud
Peter:
Agreed. The solution you suggest is in the works. By solving the
problem in gnome-settings-daemon, the solution should work the same
way in both the GNOME session and in GDM, so it will be a huge
improvement over what existed before (a GDM-only solution which was
typically turned off by
Gil:
Just thinking about it ...
Wouldn't it be reasonable to enable everything the first time the user
logs in and the if no accessible technology has been used ask if they
have to be turned off by default (and with a little explain about how to
re-enable them)?
From a usability standpoint,
Willie:
While I disagree with Brian's assessment (I think he tends to lean more
to the 'it's OK as long as an able-bodied sysadmin can configure the
system for the disabled user' side than the 'let the user be
independent' side), I'll support the decision nonetheless.
I wasn't trying to spe
Will:
While I disagree with Brian's assessment (I think he tends to lean more
to the 'it's OK as long as an able-bodied sysadmin can configure the
system for the disabled user' side than the 'let the user be
independent' side), I'll support the decision nonetheless.
I agree with you that "l
Wouter:
Thanks for reviewing the code. I will test, and we can discuss further
if there are any problems. If there is any other suggestions you have,
please let me know.
Thanks again,
Brian
> 2008-03-11 klockan 21:08 skrev Brian Cameron:
>> I tried this and the code does no
Wouter:
I'm removing the gnome-docs-team and release-team from the cc:list since
we are now talking about how to better implement this feature, and this
isn't a concern for string breakage anymore.
> 2008-03-10 klockan 20:44 skrev Brian Cameron:
>> Thanks for explaining. I u
Wouter:
> No, the gui/gdmcommon.c part of the patch is wrong. The N_() macro
> only *marks* for translation, without actually doing any translations
> (that's why you can use it in static array initializers, #defines, and
> such). It's just there so that intltool knows that the string should
> be
Wouter:
Great idea. I wrote the attached patch to fix the problem more
cleanly based on your suggestion. Does this look right to you?
Can I get approval to add translations for these two strings?
Thanks,
Brian
2008-03-07 klockan 23:06 skrev Brian Cameron:
I think you are looking at the
t
of GDM just to get the strings translated. I'm not sure this is
the best way, but I can also use a different technique if someone
has a better suggestion.
The patch you discuss below is the patch that was already approved
by the release team a few days ago.
Brian
> Am Freitag, den 07.03
It was recently reported that there is a problem translating two strings
in GDM. The two strings are the default welcome and remote welcome
strings that are shown to the user on the GDM dialog.
These strings are currently marked for translation, but improperly. So
although these strings are tr
L10N team:
It was recently reported that there is a problem translating two strings
in GDM. They are currently marked for translation, but I think
improperly. You can read more in the bug report.
http://bugzilla.gnome.org/show_bug.cgi?id=519528
Refer to comment #10 for a description of the
Deniz/Claude:
Thanks, the changes are now committed. So now the docs and i18n team
can help to translate these small changes. I think it is nice to get
these fixes into GDM 2.20.
Brian
>> As this contains some security implication, I would say this is worth
>> committing, as if we don't do
I would like to request a string freeze break for GDM 2.20. Since
GDM 2.22 was not approved for inclusion in GNOME 2.22, I would like
to get some fixes into GDM 2.20 that would be nice to address, but
affect strings. I plan to do a new GDM 2.20 release sometime in
the near future so that people
Deniz:
Sorry, backed out that change.
Brian
> On Nov 14, 2007 8:44 PM, GNOME Status Pages <[EMAIL PROTECTED]> wrote:
>> This is an automatic notification from status generation scripts on:
>> http://l10n.gnome.org/.
>>
>> There have been following string additions to module 'gdm.gnome-2-20'
Johannes:
>> Formally, we need a second approval though.
>> And please, next time ask before committing!
>
> Second approval of i18n-team!
Thanks.
> I would also agree not to translate these debug messages.
I think this also makes the most sense. Those doing translations
shouldn't be bother
Claude/Others:
Apologies for breaking string freeze in GDM 2.20. However, I think that
this change is acceptable for the following reasons, mainly reason #2
which is a security issue. I think, in this case, security trumps
translation. However, I do recognize that I should have sent an email
t
GDM2 has been branched for GNOME 2.20.
Brian
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Everyone:
Yesterday I branched GDM for 2.18, sorry for the late notice. 2.19
develoment now going on in HEAD.
Brian
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Danilo:
Thanks for catching this. I believe I have fixed this in SVN head.
Brian
> Today at 18:54, Daniel Nylander wrote:
>
>> Ermm.. some problems with the GDM2 doc module.
>> Number of strings has fallen from 1000+ to 64 and it looks wierd.
>>
>> http://progress.gnome.org/POT/gdm2.HEAD/docs
GDM is branched for GNOME 2.16, the branch is called gnome-2-16.
Future development work and bug fixing will be done in CVS head.
Brian
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
The stable branch for gdm2 is gnome-2-14, HEAD is now released from
freezes.
Brian
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Honza:
maybe I was not clear in my previous question.
All locales what are in gdmlanguages.c file appear in GDM login (i.e.
including French) on Cinnabar Linux build 32.
Great. I thought you included French in the list of missing languages
in your previous email. I must have misread.
But my quest
Adam:
Hi Brian,
It seems you have only "tagged" GDM2 with "gnome-2-10", instead of
branching. That might have happend if you missed "-b" flag in "cvs
tag" command.
I don't know how easy it is to resolve this in CVS (can one have same
branch and tag names?).
No, but luckily removing a tag is much,
Abel/i18n team:
There are two affected messages. First of all, it is this added message:
#: gui/gdmlanguages.c:83
msgid "A-M|Chinese (HongKong)"
Which, AFAIK, includes a typo. It is supossed to read "Hong Kong",
right?
You are right. I'm from Hong Kong too, so let me express my op
The gdm2 module has been branched for GNOME 2.10
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
is change. I didn't realize that this
was a string freeze issue.
Furthermore, it is this message:
#: gui/gdmsetup.c:2191
msgid "_Remove Theme"
The relevant parts of the big ChangeLog entry seems to be these:
Fri Mar 04 12:50:00 2005 Brian Camero
There are a few gdm2 bugs that seem to relate to i18n that I'm unsure how to
fix and was wondering if someone could provide some hints or otherwise help
out.
54667 - Fine grained locale selection. Users should have the ability to
select different locale things (monetary/dates/etc). Not
33 matches
Mail list logo
