inserting "underlined" characters
If I wanted to insert these characters into a gnome editor application, say in an evolution email, you know how I can do that? I have the "compose" key enabled, and can insert characters like ô without trouble. Thanks in advance, picFanen Ahua Random quote: Sex, Drugs & Linux Rules -- MaDsen Wikholm, mwikh...@at8.abo.fi On Tue, 2009-01-20 at 23:26 -0500, Thomas Thurman wrote: > > U+0331 COMBINING MACRO BELOW: fe̱ed fo̱od > > U+0332 COMBINING LOW LINE: fe̲ed fo̲od > > Receiving my own message back again, Thunderbird had problems with > U+0332 and U+0332 also doesn't work in "view source" for the web page, > whereas U+0331 works fine for both. So I think U+0331 should be what > you want, assuming it looks like the character you're looking for. > > peace > > Thomas signature.asc Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Evolution - UI change - ask for an approval
On Thu, 2009-02-12 at 00:43 +0100, Vincent Untz wrote: > Le lundi 09 février 2009, à 19:54 +0100, Andre Klapper a écrit : > > Ahoj Milan, > > > > Am Montag, den 09.02.2009, 13:35 +0100 schrieb Milan Crha: > > > m sorry, I just realized I broke an UI freeze with my recent commits > > > from below bugs. It only hides some widgets in the Network Preferences, > > > those which are not used in the code, thus which could confuse users. > > > The UI is a bit simpler now. > > > > > > I'll revert my changes with respect to UI if you disapprove such change. > > > > > > http://bugzilla.gnome.org/show_bug.cgi?id=548623 > > > > http://bugzilla.gnome.org/show_bug.cgi?id=555888 > > > > > > > > to Evolution and Evolution-Data-Server, which involves UI change in > > > > Edit->Preferences->Network Preferences. > > > > Release team approval 1 of 2 if user documentation and potential > > screenshots will definitely be updated > > Late 2 of 2 :-) > > Vincent Hi, thanks. I asked Jony and he, with Radhika, managed to do the documentation work too. Thus it's in now officially. Bye, Milan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
New string in gnome-media
Heya, A new string now in gnome-media: "Waiting for sound system to respond" It will show up when PulseAudio isn't running, or isn't responding, and the new gnome-volume-control is launched. See http://bugzilla.gnome.org/show_bug.cgi?id=566835 Cheers ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String changes in gnome-session
Il giorno gio, 12/02/2009 alle 02.20 +, Lucas Rocha ha scritto: > Hi all, > > I've changed changed the name and description of the session capplet > to better match what it actully does nowadays. The changes were made > in the capplet .desktop file. > > Name is now: Startup Applications > Description is now: Choose what applications to start when you log in Lucas, you should update the window title/name too, changing to "Startup Applications Preferences" (according to other capplets). Also note the tab label is "Startup programs"... ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: R-T doesn't care about i18n? (was: Problem with committing to gnome-screensaver)
Il giorno mer, 11/02/2009 alle 09.44 -0500, William Jon McCann ha scritto: > When we move to git immediately after 2.26.0 I trust that everyone > will be informed and ready to tackle the workflow changes that result. > I suggest that instead of continuing this conversation we focus on > making sure we're ready. William, sorry if this could appear a blackmail, but IMHO this plan of you is very un-polite for all GNOME community, so I think if you will move gnome-screensaver to git *before* the DVCS decision (if I'm right by now git is only an option, not the final choice) I'll ask to remove it from the list of GNOME Desktop modules. In the past years we have hard worked in order to have *all* *official* GNOME Desktop & Platform modules stored on the same repository (see for example mousetweaks or hamster-applet), not only for translators' sake, but for entire GNOME community. Do you like git? OK, *by now* it's a *your* choice, not a *community* choice. Start to develop on a separate, private git tree and frequently update the official module on svn, like the empathy team is currently doing. Respectfully[1] , Luca. [1] but little shocked for recent "I'm myself and I don't care about GNOME community rules" events :( ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: inserting "underlined" characters
2009/2/12 Fanen Ahua :
> If I wanted to insert these characters into a gnome editor application, say
> in an evolution email, you know how I can do that? I have the "compose" key
> enabled, and can insert characters like ô without trouble.
The Compose key will not help you here because it does not have the
full range of Latin characters with macro below (has nine only).
You can use Ctrl+Shift+u as in
1. Type, for example, G
2. Press Ctrl+Shift+u
3. Type 332, then press Spacebar
4. You get G̲
You can also edit your current keyboard layout so that it outputs
0x0331/0x0332.
Currently, only us(olpc) has that character, and is under AltGr+{.
Between 0x0331 and 0x0332, I think it's better for your work to choose
the latter because it is flatter.
with 0x0331 G̱ṈO̱M̱E̱
with 0x0332 G̲N̲O̲M̲E̲
To be able to view these characters, you need to view the text in a
window that has advanced text layout (for example, a GTK+ application
that uses Pango). You should expect that for some characters, the
macron will not be positioned perfectly under the letter.
Regardless of the above, I think that in your case, you should also
consider typing those e-mails as HTML e-mails, and using Underline for
the specific characters. To use 0x030[12] would be more of a hack, or
test-casing the text layout engines of your e-mail recipients.
Simos
> On Tue, 2009-01-20 at 23:26 -0500, Thomas Thurman wrote:
>
>> U+0331 COMBINING MACRO BELOW: fe̱ed fo̱od
>> U+0332 COMBINING LOW LINE: fe̲ed fo̲od
>
> Receiving my own message back again, Thunderbird had problems with
> U+0332 and U+0332 also doesn't work in "view source" for the web page,
> whereas U+0331 works fine for both. So I think U+0331 should be what
> you want, assuming it looks like the character you're looking for.
>
> peace
>
> Thomas
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: UI freeze break request: incoming muc invitation in Empathy
Le mercredi 11 février 2009 à 18:40 +0100, Milo Casagrande a écrit : > Il giorno mar, 10/02/2009 alle 17.45 +0100, Frederic Peters ha scritto: > > The UI change is minimal, and from a quick look at the documentation > > it doesn't seem the actions that can be performed from the status icon > > are mentioned at all. > > I've been asked to add a little comment into this thread since I'm the > last person that has been (and still is) working on Empathy > documentation. This changes doesn't affect the documentation (yet). Work > is ongoing, even if at a low pace than I would really like: it's not > that easy to balance an easy to read document for end user with a > complex application without falling into too technical/nerdy details. > > If somebody is willing to help with directions, proofreading or > whatever, please contact me, I'll be more than happy! Thanks for your comments. We got the 2 approvals from the release team so it would be good to have the advice of the doc-team as well. :) Thanks, G. -- Guillaume Desmottes Jabber GPG 1024D/711E31B1 | 1B5A 1BA8 11AA F0F1 2169 E28A AC55 8671 711E 31B1 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: UI freeze break request: incoming muc invitation in Empathy
Le jeudi 12 février 2009, à 15:34 +, Guillaume Desmottes a écrit : > Le mercredi 11 février 2009 à 18:40 +0100, Milo Casagrande a écrit : > > Il giorno mar, 10/02/2009 alle 17.45 +0100, Frederic Peters ha scritto: > > > The UI change is minimal, and from a quick look at the documentation > > > it doesn't seem the actions that can be performed from the status icon > > > are mentioned at all. > > > > I've been asked to add a little comment into this thread since I'm the > > last person that has been (and still is) working on Empathy > > documentation. This changes doesn't affect the documentation (yet). Work > > is ongoing, even if at a low pace than I would really like: it's not > > that easy to balance an easy to read document for end user with a > > complex application without falling into too technical/nerdy details. > > > > If somebody is willing to help with directions, proofreading or > > whatever, please contact me, I'll be more than happy! > > Thanks for your comments. > > We got the 2 approvals from the release team so it would be good to have > the advice of the doc-team as well. :) I take Milo's mail as a "it's fine from the documentation side", fwiw. Vincent -- Les gens heureux ne sont pas pressés. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Freeze break request for the keyboard capplet
On Wed, 2009-02-11 at 18:12 -0500, Matthias Clasen wrote: > On Wed, Feb 11, 2009 at 3:18 PM, Frederic Peters wrote: > > Andre Klapper wrote: > > > >> Am Mittwoch, den 11.02.2009, 13:09 -0500 schrieb Matthias Clasen: > >> > the new sound capplet in gnome-media doesn't have the 'visible bell' > >> > controls anymore that the > >> > old one had. The general agreement between the gnome-media maintainers > >> > and the a11y team > >> > seems to be that this is better off in the a11y UI, anyway. > >> > >> r-t approval 1 of 2 > > > > 2 of 2. > > > > Thanks, committed. > The new strings are: > > Visual cues for sounds > Show _visual feedback for the alert sound > Flash _window titlebar > Flash entire _screen Hi Matthias, I assume this means the documentation is out of date. Could you open a bug against gnome-user-docs? I'll be going through the bugs again this weekend. -- Shaun ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: UI freeze break request: incoming muc invitation in Empathy
On Thu, 2009-02-12 at 16:39 +0100, Vincent Untz wrote: > Le jeudi 12 février 2009, à 15:34 +, Guillaume Desmottes a écrit : > > Le mercredi 11 février 2009 à 18:40 +0100, Milo Casagrande a écrit : > > > Il giorno mar, 10/02/2009 alle 17.45 +0100, Frederic Peters ha scritto: > > > > The UI change is minimal, and from a quick look at the documentation > > > > it doesn't seem the actions that can be performed from the status icon > > > > are mentioned at all. > > > > > > I've been asked to add a little comment into this thread since I'm the > > > last person that has been (and still is) working on Empathy > > > documentation. This changes doesn't affect the documentation (yet). Work > > > is ongoing, even if at a low pace than I would really like: it's not > > > that easy to balance an easy to read document for end user with a > > > complex application without falling into too technical/nerdy details. > > > > > > If somebody is willing to help with directions, proofreading or > > > whatever, please contact me, I'll be more than happy! > > > > Thanks for your comments. > > > > We got the 2 approvals from the release team so it would be good to have > > the advice of the doc-team as well. :) > > I take Milo's mail as a "it's fine from the documentation side", fwiw. Milo is listed as the maintainer of the Empathy Manual, so if he says it's OK, that's good enough for me. -- Shaun ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: inserting "underlined" characters
Never mind, found it out. You insert the unicode sequence after you type the character. Thanks. picFanen Ahua Random quote: ... bleakness ... desolation ... plastic forks ... On Thu, 2009-02-12 at 10:06 +0100, Fanen Ahua wrote: > If I wanted to insert these characters into a gnome editor > application, say in an evolution email, you know how I can do that? I > have the "compose" key enabled, and can insert characters like ô > without trouble. > > Thanks in advance, > > picFanen Ahua > Random quote: Sex, Drugs & Linux Rules -- MaDsen Wikholm, > mwikh...@at8.abo.fi > > > > > > On Tue, 2009-01-20 at 23:26 -0500, Thomas Thurman wrote: > > > > U+0331 COMBINING MACRO BELOW: fe̱ed fo̱od > > > U+0332 COMBINING LOW LINE: fe̲ed fo̲od > > > > Receiving my own message back again, Thunderbird had problems with > > U+0332 and U+0332 also doesn't work in "view source" for the web page, > > whereas U+0331 works fine for both. So I think U+0331 should be what > > you want, assuming it looks like the character you're looking for. > > > > peace > > > > Thomas signature.asc Description: This is a digitally signed message part ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Please commit translations (crh)
Le jeudi 12 février 2009 à 01:09 -0600, Res,at SABIQ a écrit : > A few more are ready: > http://l10n.gnome.org/vertimus/alacarte/HEAD/po/crh > http://l10n.gnome.org/vertimus/gnome-icon-theme/HEAD/po/crh > http://l10n.gnome.org/vertimus/gnome-session/HEAD/po/crh > > Thanks. Done. Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Problem with committing to gnome-screensaver
Matthias Clasen wrote: > On Tue, Feb 10, 2009 at 6:57 PM, Frederic Peters wrote: > >> Pretty please, this is sensible ground, this is not the place to fuck >> up things not communicating. > > Clearly, Jon can do whatever he wants with gnome-screensaver. Its his > code, and he is the maintainer. If that means translators have a some > difficulties, and gnome-screensaver may be less perfectly translated > than it used to, thats unfortunate. But still ultimatively Jons > decision... Mathias, I have to disagree with that. GNOME is not an individualistic project but a group effort. For that reason, GNOME has a release process and the modules part of GNOME "core" (the various suites) have to follow the release process. Switching VCS like that, on the fly, is a disruption in this process. Even more when done in the middle of a release cycle. I see that Jon addressed the issue, but I just wanted emphasis how wrong your message was. And yes I'm eager to see GNOME move to git. Hub, who is not part of the release team. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: inserting "underlined" characters
Ah, Thanks for the reply, I pretty much stumbled upon the same solution
before I saw your email. :)
picFanen Ahua
Random quote: Lucy: Dance, dance, dance. That is all you ever do. Can't
you be serious for once? Snoopy: She is right! I think I had better
think of the more important things in life! (pause) Tomorrow!!
On Thu, 2009-02-12 at 13:52 +, Simos wrote:
> 2009/2/12 Fanen Ahua :
> > If I wanted to insert these characters into a gnome editor application, say
> > in an evolution email, you know how I can do that? I have the "compose" key
> > enabled, and can insert characters like ô without trouble.
>
> The Compose key will not help you here because it does not have the
> full range of Latin characters with macro below (has nine only).
>
> You can use Ctrl+Shift+u as in
> 1. Type, for example, G
> 2. Press Ctrl+Shift+u
> 3. Type 332, then press Spacebar
> 4. You get G̲
>
> You can also edit your current keyboard layout so that it outputs
> 0x0331/0x0332.
> Currently, only us(olpc) has that character, and is under AltGr+{.
>
> Between 0x0331 and 0x0332, I think it's better for your work to choose
> the latter because it is flatter.
>
> with 0x0331 G̱ṈO̱M̱E̱
> with 0x0332 G̲N̲O̲M̲E̲
>
> To be able to view these characters, you need to view the text in a
> window that has advanced text layout (for example, a GTK+ application
> that uses Pango). You should expect that for some characters, the
> macron will not be positioned perfectly under the letter.
>
> Regardless of the above, I think that in your case, you should also
> consider typing those e-mails as HTML e-mails, and using Underline for
> the specific characters. To use 0x030[12] would be more of a hack, or
> test-casing the text layout engines of your e-mail recipients.
>
> Simos
>
> > On Tue, 2009-01-20 at 23:26 -0500, Thomas Thurman wrote:
> >
> >> U+0331 COMBINING MACRO BELOW: fe̱ed fo̱od
> >> U+0332 COMBINING LOW LINE: fe̲ed fo̲od
> >
> > Receiving my own message back again, Thunderbird had problems with
> > U+0332 and U+0332 also doesn't work in "view source" for the web page,
> > whereas U+0331 works fine for both. So I think U+0331 should be what
> > you want, assuming it looks like the character you're looking for.
> >
> > peace
> >
> > Thomas
<>
signature.asc
Description: This is a digitally signed message part
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Freeze break request for the keyboard capplet
On Thu, Feb 12, 2009 at 11:10 AM, Shaun McCance wrote: > I assume this means the documentation is out of date. Could > you open a bug against gnome-user-docs? I'll be going through > the bugs again this weekend. http://bugzilla.gnome.org/show_bug.cgi?id=571529 This is also release notes material, imo (control moved from one place to another one...). What is the process for making that happen ? ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[URGENT] wrong gconf key description in gnome-session
In gnome-session schema file there is a string that we forgot to fix: List of components that are required as part of the session. (Each element names a key under "/desktop/gnome/session/required-components".) The Session Preferences will not normally allow users to remove a required component from the session, and the session manager will automatically add the required components back to the session if they do get removed. The actual key name is required_components: there is a FIXME comment from 2.24 claiming this should be fixed while not in string freeze. OK to commit attached patch ASAP? PS also note that /schemas/apps/gnome-session/options/logout_option GConf key is no longer used (it refers to old, all-in-one logout dialog). Should we add a "deprecated" label in short description and change the long to "This key is no longer used by gnome-session" or could we simply remove it from schema.in file? Index: data/gnome-session.schemas.in === --- data/gnome-session.schemas.in (revisione 5249) +++ data/gnome-session.schemas.in (copia locale) @@ -92,10 +92,9 @@ list string [windowmanager,panel,filemanager] - Required session components -List of components that are required as part of the session. (Each element names a key under "/desktop/gnome/session/required-components".) The Session Preferences will not normally allow users to remove a required component from the session, and the session manager will automatically add the required components back to the session if they do get removed. +List of components that are required as part of the session. (Each element names a key under "/desktop/gnome/session/required_components".) The Session Preferences will not normally allow users to remove a required component from the session, and the session manager will automatically add the required components back to the session if they do get removed. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [URGENT] wrong gconf key description in gnome-session
Il giorno gio, 12/02/2009 alle 20.42 +0100, Luca Ferretti ha scritto: > PS also note that /schemas/apps/gnome-session/options/logout_option > GConf key is no longer used (it refers to old, all-in-one logout > dialog). Should we add a "deprecated" label in short description and > change the long to "This key is no longer used by gnome-session" or > could we simply remove it from schema.in file? > Two more strings to change: /schemas/apps/gnome-session/options/auto_save_session If enabled, gnome-session will save the session automatically. Otherwise, the logout dialog will have an option to save the session. (current status: no more save option in logout dialog) /schemas/desktop/gnome/session/default_session List of applications that are part of the default session. (from file schema.in itself: "FIXME when not string frozen: mention that required components are added to the default session") ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [URGENT] wrong gconf key description in gnome-session
2009/2/12 Luca Ferretti : > In gnome-session schema file there is a string that we forgot to fix: > > List of components that are required as part of the session. > (Each element names a key under > "/desktop/gnome/session/required-components".) The Session > Preferences will not normally allow users to remove a required > component from the session, and the session manager will > automatically add the required components back to the session if > they do get removed. > > The actual key name is required_components: there is a FIXME comment > from 2.24 claiming this should be fixed while not in string freeze. > > OK to commit attached patch ASAP? Sounds fine to me to change the wrong key name. But is the description factually true ? The last time I checked, gnome-session would not bring nautilus back when I killed it, until I added the autorestart key to the nautilus desktop file. > PS also note that /schemas/apps/gnome-session/options/logout_option > GConf key is no longer used (it refers to old, all-in-one logout > dialog). Should we add a "deprecated" label in short description and > change the long to "This key is no longer used by gnome-session" or > could we simply remove it from schema.in file? I don't see any reason to keep the schema around if gnome-session is no longer using it. Why would you ? ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [URGENT] wrong gconf key description in gnome-session
Il giorno gio, 12/02/2009 alle 14.49 -0500, Matthias Clasen ha scritto: > 2009/2/12 Luca Ferretti : > > In gnome-session schema file there is a string that we forgot to fix: > > > >List of components that are required as part of the session. > >(Each element names a key under > >"/desktop/gnome/session/required-components".) The Session > Sounds fine to me to change the wrong key name. But is the description > factually true ? The last time I checked, gnome-session would not > bring > nautilus back when I killed it, until I added the autorestart key to > the nautilus desktop file. Tried in my jhbuild sandbox * nautilus - X-GNOME-AutoRestart=true X-GNOME-Provides=filemanager - is restarted * gnome-panel - no AutoRestart, no Provides - is restarted * metacity - X-GNOME-Provides=windowmanager - is not restated hmmm... we have a problem... > > PS also note that /schemas/apps/gnome-session/options/logout_option > > GConf key is no longer used (it refers to old, all-in-one logout > I don't see any reason to keep the schema around if gnome-session is > no longer using it. Why would you ? Dunno, here is a policy about no longer used gconf keys? Nautilus still provides its own old and deprecated key for icon theme, but maybe there is some kind of versioning in nautilus gconf keys. If remove the gnome-session key is hurtless, I'm for remove it ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: R-T doesn't care about i18n? (was: Problem with committing to gnome-screensaver)
On 2/12/09, Luca Ferretti wrote: > Il giorno mer, 11/02/2009 alle 09.44 -0500, William Jon McCann ha > scritto: > > When we move to git immediately after 2.26.0 I trust that everyone > > will be informed and ready to tackle the workflow changes that result. > > I suggest that instead of continuing this conversation we focus on > > making sure we're ready. > > William, sorry if this could appear a blackmail, but IMHO this plan of > you is very un-polite for all GNOME community, so I think if you will > move gnome-screensaver to git *before* the DVCS decision (if I'm right > by now git is only an option, not the final choice) I'll ask to remove > it from the list of GNOME Desktop modules. > > In the past years we have hard worked in order to have *all* *official* > GNOME Desktop & Platform modules stored on the same repository (see for > example mousetweaks or hamster-applet), not only for translators' sake, > but for entire GNOME community. > > Do you like git? OK, *by now* it's a *your* choice, not a *community* > choice. Start to develop on a separate, private git tree and frequently > update the official module on svn, like the empathy team is currently > doing. > > Respectfully[1] , Luca. > > [1] but little shocked for recent "I'm myself and I don't care about > GNOME community rules" events :( Reading up on this heated thread, here's my take on it. There are some non-arguable fundamental facts about any free software development. One of the most fundamental facts is this: 1) The maintainer of a project/module may do whatever he likes with it. However, there have always been some fundamental requirements we (the GNOME Translation Project) have required from modules officially included in GNOME. I don't know if they have been encarved into stone or sent out into space yet, but anyone who has ever followed GNOME release engineering and new module discussions closely, should be familiar with them. Some of the requirements include: 2) Translators with an account should have access to all modules officially part of GNOME. 3) All modules officially part of GNOME should be kept in *the same* GNOME repository. That last one is equally important. GNOME translators translate several hundreds of modules, and many translators need quick access to many, many of those modules on a daily basis in order to update translations. Using and remembering different workflows for each and every one of the modules would be a nightmare, so we require the workflow be the same for each module (with some extremely few exceptions for directory layout in some exceptional modules). But the "one repository" requirement has always been the same. The "one repository to rule them all" used to be cvs.gnome.org, now it is svn.gnome.org, and maybe in the not too distant future it will be git.gnome.org. However, the change to a git.gnome.org would require a Release Team decision on which DVCS GNOME should use, and a planned cutover date for the *whole* repository. The planned cutover date is because we would need to communicate the change, and carefully update all scripts and documentation, in time for the cutover date. *All* modules would need to be migrated at the same date, otherwise we have a script/documentation nightmare. Of course most of this situation is the same for the GNOME Documentation Project. So until the Release Team has decided on a DVCS for *all* of GNOME, and has announced a planned cutover date, and the cutover has happened, *no* core GNOME module should be removed from, or closed for commits, on svn.gnome.org. If a module maintainer wants to use a different repo in the mean time, fine, but then a requirement would be that they automatically sync *all* the changes in the module both back and forward with svn.gnome.org in the mean time. Unless you can reliably do all that synchronization automatically, you are *not* allowed to move. I have all the respect for module maintainers and their freedom to do whatever they like with their module. But at the same time, being "part of GNOME" is a stamp of approval of which there follows some real hard requirements, both in terms of software but also in release engineering and version control. So, if some core GNOME module "jumps the gun" and switches to a repository other than svn.gnome.org before the date of the Release Team mandated big project-wide repository cutover for all of GNOME, I would formally request of the Release Team to immediately *remove* that module/project from the list of software included in GNOME. Period. This is of course all speaking with my formal "GNOME Translation Project Spokesperson" hat on. Christian ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [URGENT] wrong gconf key description in gnome-session
Matthias Clasen wrote: > Sounds fine to me to change the wrong key name. But is the description > factually true ? The last time I checked, gnome-session would not > bring > nautilus back when I killed it, until I added the autorestart key to > the nautilus desktop file. It's poorly-worded. It's supposed to mean "even if you remove nautilus from your session, gnome-session will start it next time you log in anyway". -- Dan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: R-T doesn't care about i18n? (was: Problem with committing to gnome-screensaver)
El jue, 12-02-2009 a las 12:30 +0100, Luca Ferretti escribió: > [1] but little shocked for recent "I'm myself and I don't care about > GNOME community rules" events :( I think the most important thing to learn from these "events" is that when you delay a community-based decision so long, people start making decision on their own and moving forward. It is completely understandable that some maintainers may get tired of waiting for a decision from the community and simply decide what they think it's best for their own projects, even if this may eventually hurt other parts of the process. If we as a community can't agree on something like this and move forward, we will be facing the risk of fragmentation over and over again. Let's not allow this to happen and let's make a decision soon. Claudio -- Claudio Saavedra ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [URGENT] wrong gconf key description in gnome-session
Hi, 2009/2/12 Luca Ferretti : > Il giorno gio, 12/02/2009 alle 20.42 +0100, Luca Ferretti ha scritto: > >> PS also note that /schemas/apps/gnome-session/options/logout_option >> GConf key is no longer used (it refers to old, all-in-one logout >> dialog). Should we add a "deprecated" label in short description and >> change the long to "This key is no longer used by gnome-session" or >> could we simply remove it from schema.in file? >> > > Two more strings to change: > > /schemas/apps/gnome-session/options/auto_save_session > >If enabled, gnome-session will save the session automatically. >Otherwise, the logout dialog will have an option to save the >session. > > (current status: no more save option in logout dialog) This one should stay as I'm working on restoring the session saving (at least I should be working on this). > /schemas/desktop/gnome/session/default_session > >List of applications that are part of the default session. > > (from file schema.in itself: "FIXME when not string frozen: mention that > required components are added to the default session") Yep. --lucasr ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [URGENT] wrong gconf key description in gnome-session
Hi. 2009/2/12 Luca Ferretti : > Il giorno gio, 12/02/2009 alle 14.49 -0500, Matthias Clasen ha scritto: >> 2009/2/12 Luca Ferretti : >> > In gnome-session schema file there is a string that we forgot to fix: >> > >> >List of components that are required as part of the session. >> >(Each element names a key under >> >"/desktop/gnome/session/required-components".) The Session > >> Sounds fine to me to change the wrong key name. But is the description >> factually true ? The last time I checked, gnome-session would not >> bring >> nautilus back when I killed it, until I added the autorestart key to >> the nautilus desktop file. > > Tried in my jhbuild sandbox > * nautilus - X-GNOME-AutoRestart=true X-GNOME-Provides=filemanager >- is restarted > * gnome-panel - no AutoRestart, no Provides - is restarted > * metacity - X-GNOME-Provides=windowmanager - is not restated > > hmmm... we have a problem... This happens because apps can set their restart style using xsmp (most likely with GnomeClient api). So, even if you remove the key from gnome-panel .desktop file, gnome-panel is still doing gnome_client_set_restart_style. Yes, this is a bit confusing (well, XSMP per se is quite confusing). >> > PS also note that /schemas/apps/gnome-session/options/logout_option >> > GConf key is no longer used (it refers to old, all-in-one logout > >> I don't see any reason to keep the schema around if gnome-session is >> no longer using it. Why would you ? > > Dunno, here is a policy about no longer used gconf keys? Nautilus still > provides its own old and deprecated key for icon theme, but maybe there > is some kind of versioning in nautilus gconf keys. > > If remove the gnome-session key is hurtless, I'm for remove it Which key do you want to remove? If it's auto_save_session, you shouldn't. Thanks, --lucasr ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: [URGENT] wrong gconf key description in gnome-session
Hi, 2009/2/12 Luca Ferretti : > In gnome-session schema file there is a string that we forgot to fix: > >List of components that are required as part of the session. >(Each element names a key under >"/desktop/gnome/session/required-components".) The Session >Preferences will not normally allow users to remove a required >component from the session, and the session manager will >automatically add the required components back to the session if >they do get removed. > > The actual key name is required_components: there is a FIXME comment > from 2.24 claiming this should be fixed while not in string freeze. > > OK to commit attached patch ASAP? Feel free to commit (taking into account the danw's suggested change). > PS also note that /schemas/apps/gnome-session/options/logout_option > GConf key is no longer used (it refers to old, all-in-one logout > dialog). Should we add a "deprecated" label in short description and > change the long to "This key is no longer used by gnome-session" or > could we simply remove it from schema.in file? Ah, ok, you can remove this one. :-) --lucasr ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String change in Vino
Hi, I just fixed http://bugzilla.gnome.org/show_bug.cgi?id=556767 for Vino where a string was missing correct usage of plural form. Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
