gucharmap branched for 2.22
Hi; gucharmap has been retroactively branched for GNOME 2.22; the branch name is gnome-2-22. New development has already taken place on trunk. Regards, Christian ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gucharmap branched for 2.22
hi! seems gucharmap wasn't branched for 2.18 but in 2.20 instead, so which branch applies to 2.18? already added the gnome-2-22 branch and set it to 2.22 release set cheers, El dt 08 de 01 del 2008 a les 09:27 +0100, en/na Christian Persch va escriure: Hi; gucharmap has been retroactively branched for GNOME 2.22; the branch name is gnome-2-22. New development has already taken place on trunk. Regards, Christian ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n -- gil forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gucharmap branched for 2.22
thanks, already fixed in DL El dt 08 de 01 del 2008 a les 13:06 +0100, en/na Christian Persch va escriure: Hi; Le mardi 08 janvier 2008 à 12:35 +0100, Gil Forcada a écrit : seems gucharmap wasn't branched for 2.18 but in 2.20 instead, so which branch applies to 2.18? I think the gnome-2-16 branch should be listed for 2.18 too. I've fixed the jhbuild modulset accordingly. Regards, Christian. -- gil forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gucharmap branched for 2.22
Hi; Le mardi 08 janvier 2008 à 12:35 +0100, Gil Forcada a écrit : seems gucharmap wasn't branched for 2.18 but in 2.20 instead, so which branch applies to 2.18? I think the gnome-2-16 branch should be listed for 2.18 too. I've fixed the jhbuild modulset accordingly. Regards, Christian. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
gconf branched
Hi. I just created a gnome-2-20 gconf branch so that I could fix some strings on trunk. Cheers Kjartan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String additions to 'gconf.HEAD'
This is an automatic notification from status generation scripts on: http://l10n.gnome.org/. There have been following string additions to module 'gconf.HEAD': + Backend `%s' failed to return a vtable\n + Failed to log addition of listener %s (%s); will not be able to restore this listener on gconfd restart, resulting in unreliable notification of configuration changes. + Failed to move new saved state file into place: %s + WARNING: failed to install schema `%s', locale `%s': %s\n + WARNING: failed to uninstall schema `%s', locale `%s': %s\n Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String additions to 'gconf.HEAD'
This is an automatic notification from status generation scripts on: http://l10n.gnome.org/. There have been following string additions to module 'gconf.HEAD': + Bypass server, and access the configuration database directly. Requires that gconfd is not running. + Error loading some configuration sources: %s + Error syncing configuration data: %s + Failed to spawn the configuration server (gconfd): %s\n + Failure shutting down configuration server: %s + Launch the configuration server (gconfd). (Normally happens automatically when needed.) + No configuration files found. Trying to use the default configuration source `%s' + No configuration source addresses successfully resolved. Can't load or store configuration data + No configuration sources in the source path. Configuration won't be saved; edit %s%s + No writable configuration sources successfully resolved. May be unable to save some configuration changes + Properly installs schema files on the command line into the database. Specify a custom configuration source in the GCONF_CONFIG_SOURCE environment variable, or set set the variable to an empty string to use the default configuration source. + Properly uninstalls schema files on the command line from the database. GCONF_CONFIG_SOURCE environment variable should be set to a non-default configuration source or set to the empty string to use the default. + Resolved address \%s\ to a partially writable configuration source at position %d + You must specify a configuration source with --config-source when using --direct\n Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String additions to 'gconf.HEAD'
This is an automatic notification from status generation scripts on: http://l10n.gnome.org/. There have been following string additions to module 'gconf.HEAD': + '\\%o' is not an ASCII character and thus isn't allowed in key names + Can't have a period '.' right after a slash '/' + Can't have two slashes '/' in a row + Key/directory may not end with a slash '/' + Must begin with a slash '/' Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gconf branched
thanks, DL updated El dt 08 de 01 del 2008 a les 15:17 +0100, en/na Kjartan Maraas va escriure: Hi. I just created a gnome-2-20 gconf branch so that I could fix some strings on trunk. Cheers Kjartan ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n -- gil forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Friulian Translation:Super Help!
2007-12-22 klockan 14:47 skrev F Wolff: Op Saterdag 2007-12-22 skryf Claude Paroz: Maybe the question was related to glibc? Is there any requirement to be able to use an entirely new language on Linux? On my system I can install a package called 'locales-fur' which will enable the appropriate locale. So I assume glibc has supported this for some time at least. Confirming that glibc (at least 2.7) supports the fur_IT locale. mvrgr, Wouter -- :wq mail [EMAIL PROTECTED] web http://uwstopia.nl now she's gone love burns inside me -- black rebel motorcycle club signature.asc Description: Digital signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Incorrect linefeeds (ie. Windows) in ChangeLogs
2008-01-02 klockan 19:10 skrev Yannig MARCHEGAY: 2008/1/2, Daniel Nylander [EMAIL PROTECTED]: Please don't use Windows when editing ChangeLog files. This one is from file-roller but I've seen this on many files. 2007-12-31 Yannig Marchegay [EMAIL PROTECTED] ^M ^M * oc.po: Updated Occitan translation.^M ^M I don't use Windows: I edited the files with the Edit command in Rapidsvn (and the files were edited in gedit). I've fixed this particular case since it annoyed me as well. It's fixed in SVN now. mvrgr, Wouter -- :wq mail [EMAIL PROTECTED] web http://uwstopia.nl it's the last day on earth :: we'll never say goodbye -- marilyn manson signature.asc Description: Digital signature ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gucharmap branched for 2.22
Le mardi 08 janvier 2008 à 13:06 +0100, Christian Persch a écrit : Hi; Le mardi 08 janvier 2008 à 12:35 +0100, Gil Forcada a écrit : seems gucharmap wasn't branched for 2.18 but in 2.20 instead, so which branch applies to 2.18? I think the gnome-2-16 branch should be listed for 2.18 too. I've fixed the jhbuild modulset accordingly. This case is interesting (and not alone). When there isn't a branch for a release, it's probably not the preceding branch that was used, but rather the trunk at the time of the release, is it? In such cases, I'm inclined to think that the branch we should track is more the next branch than the preceding, that is, in this situation, the gnome-2-20 branch is closer to the real gnome-2-18 version than the gnome-2-16. At least, there was no new string between trunk at 2.18 release time and gnome-2-20 branching. I may be wrong... Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gucharmap branched for 2.22
Hi; Le mardi 08 janvier 2008 à 19:41 +0100, Claude Paroz a écrit : Le mardi 08 janvier 2008 à 13:06 +0100, Christian Persch a écrit : Hi; Le mardi 08 janvier 2008 à 12:35 +0100, Gil Forcada a écrit : seems gucharmap wasn't branched for 2.18 but in 2.20 instead, so which branch applies to 2.18? I think the gnome-2-16 branch should be listed for 2.18 too. I've fixed the jhbuild modulset accordingly. This case is interesting (and not alone). When there isn't a branch for a release, it's probably not the preceding branch that was used, but rather the trunk at the time of the release, is it? In such cases, I'm inclined to think that the branch we should track is more the next branch than the preceding, that is, in this situation, the gnome-2-20 branch is closer to the real gnome-2-18 version than the gnome-2-16. You can't tell without examining the trunk at that revision. E.g. it might depend on APIs that weren't in the platform for 2.18 but only for 2.20. In the case of gucharmap, examining the branches and tags in svn leads me to believe that we should use the 2-16 branch (gucharmap 1.8.x) for 2.18 too. Regards, Christian ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: What about integration with damned lies?
Hello, Leonardo Ferreira Fontenelle wrote: Em Dom, 2008-01-06 às 18:45 +0100, Nacho escreveu: I think is better a plugin. Because maybe someone wants to make a plugin for kde DL equivalent. If both options are equally feasible, a plugin would be better, but if it's easier to make it part of the catalog manager, then IMHO we should do it. AFAIK KDE translators are happy with Kbabel, so I don't think they would miss gtranslator integration with their SVN. (Catalogs are msgmerged in the very SVN by a bot, so there's no DL equivalent.) aren't there at least a few translators who translate all manner of things, be it Gnome, KDE, Ubuntu or TP stuff? If there are many who do that, they'd probably be happy to be remembered. BR, Gudmund ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
removed some modules
hi, doing a brand new install in one of my machines I spotted that there were some modules that were moved to svn-archive.gnome.org but not removed from DL, I have already removed, just to put to your known the affected modules are: gpdf giftoxic gnomechat webeyes evolution-gconf-ldap-backend cheers, -- gil forcada [ca] guifi.net - una xarxa lliure que no para de créixer [en] guifi.net - a non-stopping free network bloc: http://gil.badall.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: What about integration with damned lies?
You're right. It's very uncommon in Brazil but there are many locales where it does happen. Leonardo Fonenelle http://leonardof.org Em Ter, 2008-01-08 às 22:10 +0100, Gudmund Areskoug escreveu: Aren't there at least a few translators who translate all manner of things, be it Gnome, KDE, Ubuntu or TP stuff? If there are many who do that, they'd probably be happy to be remembered. BR, Gudmund ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: removed some modules
Le mercredi 09 janvier 2008 à 00:19 +0100, Gil Forcada a écrit : hi, doing a brand new install in one of my machines I spotted that there were some modules that were moved to svn-archive.gnome.org but not removed from DL, I have already removed, just to put to your known the affected modules are: gpdf giftoxic gnomechat webeyes evolution-gconf-ldap-backend Thanks Gil for this housekeeping :-) Now if it were somewhat possible to know each time a module is moved to svn-archive, it would be so cool! Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
