Re: A few suggestions for http://live.gnome.org/TranslationProject/GitHowTo
Le mardi 30 mars 2010 à 00:09 +0200, Kenneth Nielsen a écrit : > > ...or both failed because the commit check on git.gnome.org detected an > > error you didn't notice locally. And then you should revert the > > cherry-pick, amend the first commit, re-commit, re-cherry-pick and > > re-push, hoping that it will really succeed :-) > > > > Personally I prefer to push before cherry-picking, but it might not be > > the case for everyone, I admit. > > > > Claude > > So would I. Thanks Simos for updating the GitHowTo. Very appreciated! Claude -- www.2xlibre.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[gok] Created branch gnome-2-30
The branch 'gnome-2-30' was created pointing to: cb61aad... Prepare 2.30.0 release ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: zenity documentation integration wierdness
> On l10n.gnome.org, xml2po is always run with th -e switch > (--expand-all-entities), which is probably the reason of this difference > in fuzzy strings. Ahh thanks. I don't know how I could have missed that one. Regards Kenneth > > Claude > -- > www.2xlibre.net > > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: A few suggestions for http://live.gnome.org/TranslationProject/GitHowTo
> ...or both failed because the commit check on git.gnome.org detected an > error you didn't notice locally. And then you should revert the > cherry-pick, amend the first commit, re-commit, re-cherry-pick and > re-push, hoping that it will really succeed :-) > > Personally I prefer to push before cherry-picking, but it might not be > the case for everyone, I admit. > > Claude So would I. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: A few suggestions for http://live.gnome.org/TranslationProject/GitHowTo
Le mardi 30 mars 2010 à 00:37 +0300, Simos Xenitellis a écrit : > On Mon, Mar 29, 2010 at 5:09 PM, Claude Paroz wrote: > > Le lundi 29 mars 2010 à 11:36 +0200, Kenneth Nielsen a écrit : > >> Hello > >> > >> I was wondering if someone, someone more knowledgeable about git than > >> me, would add information to: > >> http://live.gnome.org/TranslationProject/GitHowTo about what to do > >> when you encounter this message: > >> > >> warning: You did not specify any refspecs to push, and the current remote > >> warning: has not configured any push refspecs. The default action in this > >> warning: case is to push all matching refspecs, that is, all branches > >> warning: that exist both locally and remotely will be updated. This may > >> warning: not necessarily be what you want to happen. > >> warning: > >> warning: You can specify what action you want to take in this case, and > >> warning: avoid seeing this message again, by configuring 'push.default' to: > >> warning: 'nothing' : Do not push anything > >> warning: 'matching' : Push all matching branches (default) > >> warning: 'tracking' : Push the current branch to whatever it is tracking > >> warning: 'current' : Push the current branch > >> > >> Or possible show how to set it up right in the setup part of the guide. > > > > I suggest to add an entry in the troubleshooting section, suggesting the > > following: > > With recent versions of git, you have to indicate the default push > > method for your local branches. You will probably want to configure it > > this way: > > $ git config --global push.default tracking > > > > Does this sound correct to git gurus? > > I am not a git guru. My view would be that it's better to have > 'matching' instead of 'tracking'. > > This option makes sense for translatros if they are committing to a > branch, as well to master. > If you are translating evolution for branch gnome-2-30, you normally > want to commit the same translation to master. > > Here is a workflow, > 1. Update/Clone a repository, for example 'evolution'. > > 2. Checkout the 'gnome-2-30' branch with > > $ git checkout --track origin/gnome-2-30 > $ _ > > 3. Add the translation and commit it, > $ git commit -m "Updated Greek translation for evolution documentation" el.po > [gnome-2-30 afa65e1] Updated Greek translation for evolution documentation > 1 files changed, 23 insertions(+), 131 deletions(-) > $ _ > > 4. Checkout master. > $ git checkout master > Switched to branch 'master' > $ _ > > 5. Cherry-pick the 'afa65e1' commit, > $ git cherry-pick afa65e1 > Finished one cherry-pick. > [master 3c1c071] Updated Greek translation for evolution documentation > 1 files changed, 23 insertions(+), 131 deletions(-) > $ _ > > 6. Finally, perform a 'git push' and send both commits to > git.gnome.org in one go, > $ git push > Counting objects: 14, done. > Delta compression using up to 2 threads. > Compressing objects: 100% (8/8), done. > Writing objects: 100% (8/8), 1.69 KiB, done. > Total 8 (delta 5), reused 0 (delta 0) > To ssh://si...@git.gnome.org/git/evolution >e8d32b7..afa65e1 gnome-2-30 -> gnome-2-30 >f84793e..3c1c071 master -> master > $ _ > > Both 'gnome-2-30' and 'master' succeeded, so we are fine. ...or both failed because the commit check on git.gnome.org detected an error you didn't notice locally. And then you should revert the cherry-pick, amend the first commit, re-commit, re-cherry-pick and re-push, hoping that it will really succeed :-) Personally I prefer to push before cherry-picking, but it might not be the case for everyone, I admit. Claude > Without 'push.default=matching', we would need to run 'git 'push'es > twice, once on each branch. > > Simos ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: A few suggestions for http://live.gnome.org/TranslationProject/GitHowTo
On Mon, Mar 29, 2010 at 5:09 PM, Claude Paroz wrote: > Le lundi 29 mars 2010 à 11:36 +0200, Kenneth Nielsen a écrit : >> Hello >> >> I was wondering if someone, someone more knowledgeable about git than >> me, would add information to: >> http://live.gnome.org/TranslationProject/GitHowTo about what to do >> when you encounter this message: >> >> warning: You did not specify any refspecs to push, and the current remote >> warning: has not configured any push refspecs. The default action in this >> warning: case is to push all matching refspecs, that is, all branches >> warning: that exist both locally and remotely will be updated. This may >> warning: not necessarily be what you want to happen. >> warning: >> warning: You can specify what action you want to take in this case, and >> warning: avoid seeing this message again, by configuring 'push.default' to: >> warning: 'nothing' : Do not push anything >> warning: 'matching' : Push all matching branches (default) >> warning: 'tracking' : Push the current branch to whatever it is tracking >> warning: 'current' : Push the current branch >> >> Or possible show how to set it up right in the setup part of the guide. > > I suggest to add an entry in the troubleshooting section, suggesting the > following: > With recent versions of git, you have to indicate the default push > method for your local branches. You will probably want to configure it > this way: > $ git config --global push.default tracking > > Does this sound correct to git gurus? I am not a git guru. My view would be that it's better to have 'matching' instead of 'tracking'. This option makes sense for translatros if they are committing to a branch, as well to master. If you are translating evolution for branch gnome-2-30, you normally want to commit the same translation to master. Here is a workflow, 1. Update/Clone a repository, for example 'evolution'. 2. Checkout the 'gnome-2-30' branch with $ git checkout --track origin/gnome-2-30 $ _ 3. Add the translation and commit it, $ git commit -m "Updated Greek translation for evolution documentation" el.po [gnome-2-30 afa65e1] Updated Greek translation for evolution documentation 1 files changed, 23 insertions(+), 131 deletions(-) $ _ 4. Checkout master. $ git checkout master Switched to branch 'master' $ _ 5. Cherry-pick the 'afa65e1' commit, $ git cherry-pick afa65e1 Finished one cherry-pick. [master 3c1c071] Updated Greek translation for evolution documentation 1 files changed, 23 insertions(+), 131 deletions(-) $ _ 6. Finally, perform a 'git push' and send both commits to git.gnome.org in one go, $ git push Counting objects: 14, done. Delta compression using up to 2 threads. Compressing objects: 100% (8/8), done. Writing objects: 100% (8/8), 1.69 KiB, done. Total 8 (delta 5), reused 0 (delta 0) To ssh://si...@git.gnome.org/git/evolution e8d32b7..afa65e1 gnome-2-30 -> gnome-2-30 f84793e..3c1c071 master -> master $ _ Both 'gnome-2-30' and 'master' succeeded, so we are fine. Without 'push.default=matching', we would need to run 'git 'push'es twice, once on each branch. Simos >> On another note, I assume there has been a ruling on this issue from >> the same guide >> >> >Commit your changes >> > >> >... We probably will not have to update the ChangeLog file with Git. Watch >> >this space for a final announcement. >> >The issue is whether it would be sufficient to simply to use the commit >> >message (the message you type with '-m'). >> >For translations, it would make sense to simply use the commit message. >> >> If someone knows about it, would they update that as well. > > Updated (no more ChangeLogs...). -- A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
2.30 Release Notes screenshot update
Hi all, With a recommendation from the Andreas on the Art team, I've replaced the screenshot of the GNOME Zazzle store with a png of just the t-shirts Andreas provided. I'll also be adding the GNOME 2.30 desktop screenshot later tonight. Sorry for the late edits. Paul ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[gnome-games] Created branch gnome-2-30
The branch 'gnome-2-30' was created pointing to: e79d11c... Fixes to Catalan translation ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
New Gnumeric stable release
FYI, I intend to release a new stable version of Gnumeric (1.10.2) within a week or so. Gnumeric has a large number of strings that need translation. Please note, that Gnumeric's po files are split between directories po and po-functions. The latter contains all strings related by plugin's functions. The former contains the rest, mainly the gui. * If you have to prioritize between po and po-functions, the former is more important. In fact, just going over the menus and making sure they are properly translated would be huge step forward. * Please do not update po/LINUGAS unless both po and po-functions have translation files for you language. Doing so breaks the build. * Updating Goffice's translations too would be helpful. Thanks, Morten Welinder te...@gnome.org ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-2-30
The branch 'gnome-2-30' was created pointing to: 602f23b... Update NEWS to include latest translations for 2.30. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: 2.30 Release Notes
On Sun, Mar 28, 2010 at 10:35 PM, Johannes Schmid wrote: > Hi! > > Hi! > > > > > How can we submit translations for release notes? > > > > As said some mail ago on the the list, checkout the release-notes module > (gnome-2-30 branch) and translate it as you would any other GNOME > module. > > Thanks! Already submitted Bengali (bn) translation. Cheers, -Jamil ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: zenity documentation integration wierdness
Le lundi 29 mars 2010 à 10:23 +0200, Kenneth Nielsen a écrit : > Hello > > According to damned lies the documentation for zenity, branch 2-30 has > two fuzzy strings, so I translator downloaded the file updated it and > sent it to me for integration. I pulled the repo, switched branch, > copied in the po-file and ran xml2po -u da.po ../C/*.xml the same way > I always do, and then it reports 11 fuzzy string in the result. > > That had me wondering a little bit, because I know that the translator > had not had the file that long. So then I tried simply pulling the > repo and running xml2po on the file that was already there, same > result 11 fuzzy. Why isn't damned lies showing these strings? I > updated the file and sent it in and damned lies still reports 2 fuzzy, > what gives? On l10n.gnome.org, xml2po is always run with th -e switch (--expand-all-entities), which is probably the reason of this difference in fuzzy strings. Claude -- www.2xlibre.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: 2.30 Release Notes
Paul Cutler wrote: > The 2.30 release notes are almost ready for translation. I've sent them > out for review, so there may be some minor changes in the next 24-48 > hours, but for the most part they're ready to be translated. Also I just created the "en" translation, to host late typo fix, so there are no changes in the original file and no fuzzy strings in the translations. Frederic ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Commit Git For Malay [ms] Translation
2010/3/29 Claude Paroz > Le lundi 29 mars 2010 à 20:51 +0800, Umarzuki Mochlis a écrit : > > > 2010/3/29 Simos Xenitellis > > > > In addition, according to > > https://bugzilla.gnome.org/describecomponents.cgi?product=l10n > > for the Malay language the contact address is Hasbullah Bin > > Pit. > > When a bug report is filed for Malay, the contact address > > receives a > > notification e-mail. > > You may want to add either your own e-mail address or put a > > mailing > > list address (like Google Groups). > > > how do i change that on gnome bugzilla? > > > > I've updated it to your address. > If you'd rather have an alias like l10n-ms-ma...@gnome.bugs that anyone > can watch, you should enter a bug report against the bugzilla.gnome.org > product. > > thanks > Claude > -- > www.2xlibre.net > > -- Regards, Umarzuki Mochlis http://debmal.my ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[brasero] Created branch gnome-2-30
The branch 'gnome-2-30' was created pointing to: 03a7999... Bump to 2.30.0 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Commit Git For Malay [ms] Translation
Le lundi 29 mars 2010 à 20:51 +0800, Umarzuki Mochlis a écrit : > 2010/3/29 Simos Xenitellis > > In addition, according to > https://bugzilla.gnome.org/describecomponents.cgi?product=l10n > for the Malay language the contact address is Hasbullah Bin > Pit. > When a bug report is filed for Malay, the contact address > receives a > notification e-mail. > You may want to add either your own e-mail address or put a > mailing > list address (like Google Groups). > how do i change that on gnome bugzilla? > I've updated it to your address. If you'd rather have an alias like l10n-ms-ma...@gnome.bugs that anyone can watch, you should enter a bug report against the bugzilla.gnome.org product. Claude -- www.2xlibre.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: A few suggestions for http://live.gnome.org/TranslationProject/GitHowTo
Le lundi 29 mars 2010 à 11:36 +0200, Kenneth Nielsen a écrit : > Hello > > I was wondering if someone, someone more knowledgeable about git than > me, would add information to: > http://live.gnome.org/TranslationProject/GitHowTo about what to do > when you encounter this message: > > warning: You did not specify any refspecs to push, and the current remote > warning: has not configured any push refspecs. The default action in this > warning: case is to push all matching refspecs, that is, all branches > warning: that exist both locally and remotely will be updated. This may > warning: not necessarily be what you want to happen. > warning: > warning: You can specify what action you want to take in this case, and > warning: avoid seeing this message again, by configuring 'push.default' to: > warning: 'nothing' : Do not push anything > warning: 'matching' : Push all matching branches (default) > warning: 'tracking' : Push the current branch to whatever it is tracking > warning: 'current' : Push the current branch > > Or possible show how to set it up right in the setup part of the guide. I suggest to add an entry in the troubleshooting section, suggesting the following: With recent versions of git, you have to indicate the default push method for your local branches. You will probably want to configure it this way: $ git config --global push.default tracking Does this sound correct to git gurus? > On another note, I assume there has been a ruling on this issue from > the same guide > > >Commit your changes > > > >... We probably will not have to update the ChangeLog file with Git. Watch > >this space for a final announcement. > >The issue is whether it would be sufficient to simply to use the commit > >message (the message you type with '-m'). > >For translations, it would make sense to simply use the commit message. > > If someone knows about it, would they update that as well. Updated (no more ChangeLogs...). Claude -- www.2xlibre.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[gucharmap] Created branch gnome-2-30
The branch 'gnome-2-30' was created pointing to: 6d12528... Docs fuzz ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Commit Git For Malay [ms] Translation
2010/3/29 Simos Xenitellis > On Mon, Mar 29, 2010 at 10:32 AM, Umarzuki Mochlis > wrote: > > > > > > 2010/3/29 Claude Paroz > >> > >> Le lundi 29 mars 2010 à 10:40 +0800, sir_ade a écrit : > >> > Hi, > >> > I need someone who have git access to commit the bug for malay > >> > translation. here the link. > >> > > >> > https://bugzilla.gnome.org/show_bug.cgi?id=613503 > >> > https://bugzilla.gnome.org/show_bug.cgi?id=613500 > >> > https://bugzilla.gnome.org/show_bug.cgi?id=613497 > >> > https://bugzilla.gnome.org/show_bug.cgi?id=613500 > >> > > >> > Thanks. > >> > >> Hi, > >> > >> Unless we have a green light from the Malay coordinator, these files > >> should not be committed by anyone on this list. > >> > >> Umarzuki ? > >> > > > > All files seems ok. Please commit. > > Committed. > > Umarzuki, there are more translation files at http://bit.ly/b53tA2 > Could you please note which ones you would like to see committed? > > i'll wait till sir_ade uploaded the right .po files > In addition, according to > https://bugzilla.gnome.org/describecomponents.cgi?product=l10n > for the Malay language the contact address is Hasbullah Bin Pit. > When a bug report is filed for Malay, the contact address receives a > notification e-mail. > You may want to add either your own e-mail address or put a mailing > list address (like Google Groups). > > how do i change that on gnome bugzilla? > Simos > > -- > A. Because it breaks the logical sequence of discussion > Q. Why is top posting bad? > -- Regards, Umarzuki Mochlis http://debmal.my ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Commit Git For Malay [ms] Translation
On Mon, Mar 29, 2010 at 10:32 AM, Umarzuki Mochlis wrote: > > > 2010/3/29 Claude Paroz >> >> Le lundi 29 mars 2010 à 10:40 +0800, sir_ade a écrit : >> > Hi, >> > I need someone who have git access to commit the bug for malay >> > translation. here the link. >> > >> > https://bugzilla.gnome.org/show_bug.cgi?id=613503 >> > https://bugzilla.gnome.org/show_bug.cgi?id=613500 >> > https://bugzilla.gnome.org/show_bug.cgi?id=613497 >> > https://bugzilla.gnome.org/show_bug.cgi?id=613500 >> > >> > Thanks. >> >> Hi, >> >> Unless we have a green light from the Malay coordinator, these files >> should not be committed by anyone on this list. >> >> Umarzuki ? >> > > All files seems ok. Please commit. Committed. Umarzuki, there are more translation files at http://bit.ly/b53tA2 Could you please note which ones you would like to see committed? In addition, according to https://bugzilla.gnome.org/describecomponents.cgi?product=l10n for the Malay language the contact address is Hasbullah Bin Pit. When a bug report is filed for Malay, the contact address receives a notification e-mail. You may want to add either your own e-mail address or put a mailing list address (like Google Groups). Simos -- A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[hamster-applet] Created branch gnome-2-30
The branch 'gnome-2-30' was created. Summary of new commits: f81457e... release notes and version bump to 2.30 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
String additions to 'gnome-packagekit.master'
This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'gnome-packagekit.master': + "Automatically remove unused dependencies" + "When removing a package, also remove those dependencies that are not required by other packages" 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
[gnome-packagekit] Created branch gnome-2-30
The branch 'gnome-2-30' was created pointing to: 8995423... Post release version bump ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[gnome-power-manager] Created branch gnome-2-30
The branch 'gnome-2-30' was created pointing to: 85773cf... Post release version bump ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[gdl] Created branch gnome-2-30
The branch 'gnome-2-30' was created pointing to: 2bd18b7... Updated files for 2.30 release ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
GNOME Color Manager 2.30.0
gnome-color-manager is a session program that makes it easy to manage, install and generate color profiles in the GNOME desktop. Version 2.30.0 ~~ Released: 2010-03-29 * Translations - Add Simplified Chinese translation (Eleanor Chen) - Update Czech translation (Milan Knížek) - Updated German doc translation (Mario Blättermann) - Updated German translation (Christian Kirbach) - Updated German translation (Mario Blättermann) - Updated Lithuanian translation (Gintautas Miliauskas) - Updated Norwegian bokmål translation (Kjartan Maraas) - Updated Polish translation (Piotr Drąg) - Updated Portuguese translation (António Lima) - Updated Russian translation (Alexandre Prokoudine) - Updated Slovenian translation (Andrej Žnidaršič) - Updated Spanish translation (Jorge González) * New Features: - Add a 'created' and 'modified' key to each device in the config file (Richard Hughes) - Add a DBus method GetDevices() and relax the checks in GetProfilesForDevice() to also take a device ID (Richard Hughes) - Add an entry to the FAQ to explain the difference between calibration and characterization (Richard Hughes) - Add a notification when devices with profiles need recalibrating (Richard Hughes) - Add CMP DT 003 target image submitted by Guy Kloss (Pascal de Bruijn) - Add images of the Colorimtre HCFR (Richard Hughes) - Add images of the i1 Pro (Richard Hughes) - Add info regarding high precision for display profiling (Milan Knížek) - Allow the user to choose the calibration precision using an interactive dialog (Richard Hughes) - Convert the .tiff files to .jpeg if we are creating a print profile (Richard Hughes) - Do not rely on usb.ids, but instead encode the colorimeter type in the udev rules (Richard Hughes) - Emit ::changed on the public DBus interface when devices are added or removed (Richard Hughes) - For laptops, use the DMI data to contruct the calibration filename (Richard Hughes) - Make sure the profile comboboxes are alphabetically sorted (Richard Hughes) - Show each device setting when we use gcm-inspect --dump (Richard Hughes) - Use libsane to get our scanners, which means remote devices are now supported (Richard Hughes) - When devices are connected and disconnected, do not remove then add them, just change the state (Richard Hughes) * Bugfix: - Check and correct TIFF image files with alpha channels before using them in argyllcms. Fixes rh#569564 (Richard Hughes) - Correct terminology in help file (Milan Knížek) - Correct use of calibrate/profile and replace device by instrument (Milan Knížek) - Do not crash attempting to add cups printers without PPD file (Martin Szulecki) - Do not crash the DBus service if a device does not have a profile set and it is included in a query (Richard Hughes) - Do not crash when GetProfileForWindow() succeeds in finding a window (Richard Hughes) - Do not use ACL_MANAGE, udev is already doing this for us (Richard Hughes) - Fix "cast increases required alignment of target type" [ia64] (Kamal Mostafa) - Fix up some translatable messages. Fixes #612111 (Richard Hughes) - Fix wrong word in data/gnome-color-manager.schemas.in. Fixes #612105 (Christian Kirbach) - If there are any lcms warnings in gcm-fix-profile, do not attempt to re-save the profile (Richard Hughes) - Make gcm-install-system-wide a little more paranoid from users that might want to be horrible (Richard Hughes) - Parse the EDID more carefully to not overwrite the model with junk for an invalid entry. Fixes #155410 (Richard Hughes) - Prevent a segfault if ppdOpenFile() fails for whatever reason (Richard Hughes) - Update profiling precision wording (Milan Knížek) - Use the model name for the SANE id, the 'name' attribute depends on the USB port used (Richard Hughes) - Warn if GConf is not set correctly when setting up the dialog (Richard Hughes) Additionally, it has branched for 2-30 and development continues in master. Richard. ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[gnome-color-manager] Created branch gnome-2-30
The branch 'gnome-2-30' was created pointing to: fc9120a... Post release version bump ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
A few suggestions for http://live.gnome.org/TranslationProject/GitHowTo
Hello I was wondering if someone, someone more knowledgeable about git than me, would add information to: http://live.gnome.org/TranslationProject/GitHowTo about what to do when you encounter this message: warning: You did not specify any refspecs to push, and the current remote warning: has not configured any push refspecs. The default action in this warning: case is to push all matching refspecs, that is, all branches warning: that exist both locally and remotely will be updated. This may warning: not necessarily be what you want to happen. warning: warning: You can specify what action you want to take in this case, and warning: avoid seeing this message again, by configuring 'push.default' to: warning: 'nothing' : Do not push anything warning: 'matching' : Push all matching branches (default) warning: 'tracking' : Push the current branch to whatever it is tracking warning: 'current' : Push the current branch Or possible show how to set it up right in the setup part of the guide. On another note, I assume there has been a ruling on this issue from the same guide >Commit your changes > >... We probably will not have to update the ChangeLog file with Git. Watch >this space for a final announcement. >The issue is whether it would be sufficient to simply to use the commit >message (the message you type with '-m'). >For translations, it would make sense to simply use the commit message. If someone knows about it, would they update that as well. Regards Kenneth Nielsen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
zenity documentation integration wierdness
Hello According to damned lies the documentation for zenity, branch 2-30 has two fuzzy strings, so I translator downloaded the file updated it and sent it to me for integration. I pulled the repo, switched branch, copied in the po-file and ran xml2po -u da.po ../C/*.xml the same way I always do, and then it reports 11 fuzzy string in the result. That had me wondering a little bit, because I know that the translator had not had the file that long. So then I tried simply pulling the repo and running xml2po on the file that was already there, same result 11 fuzzy. Why isn't damned lies showing these strings? I updated the file and sent it in and damned lies still reports 2 fuzzy, what gives? Regards Kenneth ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Commit For Malay [ms] Translation
hi, anyone with git access please help me to commit these files. https://bugzilla.gnome.org/show_bug.cgi?id=614225 https://bugzilla.gnome.org/show_bug.cgi?id=614224 https://bugzilla.gnome.org/show_bug.cgi?id=614223 thanks ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Automatic translation of new msgs, marking them as fuzzy
Am Sonntag, den 21.03.2010, 19:52 +0200 schrieb Thanos Lefteris: > I noticed that for some modules when the devs add new strings, the > msgs in .po stay untranslated and when devs modify a string, the msgs > are marked as fuzzy and there is also the previous version of the > original string in the po. Those are the modules I like :) This is the case for ALL modules on l10n.gnome.org, not only some. andre -- mailto:ak...@gmx.net | failed http://www.iomc.de/ | http://blogs.gnome.org/aklapper ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Commit Git For Malay [ms] Translation
2010/3/29 Claude Paroz > Le lundi 29 mars 2010 à 10:40 +0800, sir_ade a écrit : > > Hi, > > I need someone who have git access to commit the bug for malay > > translation. here the link. > > > > https://bugzilla.gnome.org/show_bug.cgi?id=613503 > > https://bugzilla.gnome.org/show_bug.cgi?id=613500 > > https://bugzilla.gnome.org/show_bug.cgi?id=613497 > > https://bugzilla.gnome.org/show_bug.cgi?id=613500 > > > > Thanks. > > Hi, > > Unless we have a green light from the Malay coordinator, these files > should not be committed by anyone on this list. > > Umarzuki ? > > All files seems ok. Please commit. > Claude > -- > www.2xlibre.net > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n > -- Regards, Umarzuki Mochlis http://debmal.my ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Commit Git For Malay [ms] Translation
Le lundi 29 mars 2010 à 10:40 +0800, sir_ade a écrit : > Hi, > I need someone who have git access to commit the bug for malay > translation. here the link. > > https://bugzilla.gnome.org/show_bug.cgi?id=613503 > https://bugzilla.gnome.org/show_bug.cgi?id=613500 > https://bugzilla.gnome.org/show_bug.cgi?id=613497 > https://bugzilla.gnome.org/show_bug.cgi?id=613500 > > Thanks. Hi, Unless we have a green light from the Malay coordinator, these files should not be committed by anyone on this list. Umarzuki ? Claude -- www.2xlibre.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
