request for string change in evolution
Hi guys,
I need to change a couple of strings in evolution:
! em_format_format_error(emf, stream, ex->desc?("Could not parse
S/MIME message"):_("Could not parse S/MIME message: Unknown error"));
To:
! em_format_format_error(emf, stream, ex->desc?_("Error decrypting
message"):_("Unknown error decrypting message"));
For starters the first isn't marked for translation anyway, and second
the message is incorrect.
If it would make any difference, I could just use the one string "Error
decrypting message" instead, since the 'unknown error' bit doesn't add
anything useful.
Part of patch for this bug:
http://bugzilla.gnome.org/show_bug.cgi?id=271894
Thanks,
Michael
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: ui and string changes in gnome-volume-manager
Le mercredi 17 août 2005 à 09:55 -0600, Elijah Newren a écrit : > On 8/17/05, Jeffrey Stedfast <[EMAIL PROTECTED]> wrote: > > The attached patch changes most of the strings in manager.c as well as > > changing the way the dialog prompts look. > > > > you can see the before/after here: > > > > http://primates.ximian.com/~glesage/stuff/gvm/ > > > > Jeff > > Ooh, looks much prettier. :-) I tend towards approving but want to > hear how it would affect documentation and translation first...adding > Shaun to the cc list. Just fixing the gnome-i18n address and adding gnome-doc-list so we get a faster answer ;-) 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
libgnome: change for 2 strings?
Hi, This is http://bugzilla.gnome.org/show_bug.cgi?id=311524: "With the changes to the mouse capplet for GNOME 2.12 and GTK 2.8 you don't need to restart your session to change a cursor, the keys description need to be updated to reflect that. http://bugzilla.gnome.org/attachment.cgi?id=49741&action=view fix this" Cheers, Sebastien Bacher ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Translating the GNOME 2.12 release notes
The release notes will be ready for translation on August 31st, giving you one week for translation before the release on September 7th. We are using the xml2po system again, after it worked so well last time: http://www.gnome.org/start/2.10/ Maybe you can reuse some strings from your previous .po files. This time, the files are in gnomeweb-wml instead of releng. It would be good if the experts added some instructions here: http://live.gnome.org/ReleaseNotes_2fTranslating As a start, here are Danilo's instructions for the 2.10 notes, though it should be easier this time: http://mail.gnome.org/archives/gnome-i18n/2005-February/msg00207.html -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translating the GNOME 2.12 release notes
On 2005-08-18T17:19:14+0300, [EMAIL PROTECTED] wrote: > The release notes will be ready for translation on August 31st, > giving you one week for translation before the release on September > 7th. I just wonder if any of you have heard about HTTP content negotiation? Content negotiation is a way for the web browser to send accepted languages in a HTTP request and get the best translation (according to user's preferences) as return. For example Debian's website uses this technique, and you can read more at http://www.debian.org/intro/cn > Of course there are some proxies et cetera in wild which have broken support for this technique, and therefore sometimes at least Debian gets feedback because of badly configured browsers or broken proxy servers, but IMHO the technique works well. As a translator this is interesting question for me because having a link "http://www.gnome.org/start/2.12/notes/"; select language automatically would increase visibility of translations as users no longer need to manually select translation every time. To use such technique, the pages need to be named in a way that HTTP server's content negotiation module understands those to be same page, and content negotiation module loaded -- that should be enough. In Apache it would mean that when english page is notes/index.html, then Finnish translation is index.fi.html (or index.html.fi depending on some settings), and French translation is index.fr.html (or index.html.fr). Then user accesses URL http://www.g.o/s/2.12/notes/ or .../notes/index and gets version of the page according to his/her browser settings. (Technically it sends Accept-Language header in HTTP request.) -- Tommi Vainikainen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translating the GNOME 2.12 release notes
On Thu, 2005-08-18 at 18:28 +0300, Tommi Vainikainen wrote: > On 2005-08-18T17:19:14+0300, [EMAIL PROTECTED] wrote: > > The release notes will be ready for translation on August 31st, > > giving you one week for translation before the release on September > > 7th. > > I just wonder if any of you have heard about HTTP content negotiation? Yeah, that could be nice, but it's really an issue for the gnome-web-list. Right now, I'm more concerned with actually generating the content in the first place. > Content negotiation is a way for the web browser to send accepted > languages in a HTTP request and get the best translation (according to > user's preferences) as return. For example Debian's website uses this > technique, and you can read more at > http://www.debian.org/intro/cn > > > Of course there are some proxies et cetera in wild which have broken > support for this technique, and therefore sometimes at least Debian > gets feedback because of badly configured browsers or broken proxy > servers, but IMHO the technique works well. > > As a translator this is interesting question for me because having a > link "http://www.gnome.org/start/2.12/notes/"; select language > automatically would increase visibility of translations as users no > longer need to manually select translation every time. > > To use such technique, the pages need to be named in a way that HTTP > server's content negotiation module understands those to be same page, > and content negotiation module loaded -- that should be enough. > > In Apache it would mean that when english page is notes/index.html, > then Finnish translation is index.fi.html (or index.html.fi depending > on some settings), and French translation is index.fr.html (or > index.html.fr). Then user accesses URL http://www.g.o/s/2.12/notes/ or > .../notes/index and gets version of the page according to his/her > browser settings. (Technically it sends Accept-Language header in HTTP > request.) -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translating the GNOME 2.12 release notes
Today at 16:19, Murray Cumming wrote: > It would be good if the experts added some instructions here: > http://live.gnome.org/ReleaseNotes_2fTranslating I have put the instructions on the page above. Release Notes are now a proper gnome-doc-utils module, so everyone can track the status online at: http://kvota.net/doc-l10n/by-modules.html#gnome-tour Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Translating the GNOME 2.12 release notes
On Thu, 2005-08-18 at 23:14 +0200, Danilo Šegan wrote: > Today at 16:19, Murray Cumming wrote: > > > It would be good if the experts added some instructions here: > > http://live.gnome.org/ReleaseNotes_2fTranslating > > I have put the instructions on the page above. Thanks. Remember that the Tour and the Release Notes are two different things. It doesn't seem likely that we'll finish the Tour in time for the 2.12 release, unless someone other than me does it. > Release Notes are now a proper gnome-doc-utils module, so everyone can > track the status online at: > > http://kvota.net/doc-l10n/by-modules.html#gnome-tour Excellent. That seems to be the Tour. Can we have the Release Notes on there too, please. -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: possible break of string freeze in recent-files
On 8/18/05, Emmanuele Bassi <[EMAIL PROTECTED]> wrote: > Hi all, > > While fixing bug #129195, I investigated the possibility of marking as > translatable the strings in EggRecent, since there weren't. > > This would break the string freeze in every program that is using an > updated version of the code present in libegg/recent-files, and since we > are late in the release process, I was wondering if this could be done > now or should wait the next cycle. According to http://mail.gnome.org/archives/desktop-devel-list/2005-February/msg00092.html: "The following types of changes do not need explicit approval, however we would still very much like them to be announced so that we know about them: * Marking a message for translation that was previously not marked for translation by accident." If I understand you correctly, this is the case that covers what you're talking about, in which case it should be fine to go ahead--just have the module authors notify the translation team. Cheers, Elijah ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Marking strings in libegg/recent-files as translatable
Hi all. While fixing bug #129195 in libegg/recent-files, came to my attention that the strings in there are not marked for translation. Marking them would not mean breaking the string freeze (according to the rules the GTP sent on the desktop-devel list), but, also, this would mean that every project using the code in libegg/recent-files is going to have those new strings. Please, let me know if I may go ahead, or stop before committing. Kind regards, Emmanuele. -- Emmanuele Bassi <[EMAIL PROTECTED]> Web site: http://log.emmanuelebassi.net ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Weekly translation status for Gnome 2.12
Translation status changes from 2005-08-11 to 2005-08-18. Total message count is stable at 32864. Average change during this period was 0.875%. Top 5 movers of the week: * Macedonian (up 9.72%, now supported) * Bengali (up 7.5%, partially supported) * Indonesian (up 3.14%, supported) * Romanian (up 3.11%, supported) * Hungarian (up 2.51%, supported) Supported languages (more than 80% strings translated). 1. Canadian English (en_CA) 100.00% up 0.01% 2. Hungarian (hu) 99.99% up 2.51% 3. Spanish (es) 100.00% up 0.02% 4. Greek (el) 99.91% up 2.48% Finnish (fi) 99.91% up 0.24% 6. Norwegian Bookmal (nb) 99.87% up 0.17% 7. Bulgarian (bg) 99.83% up 0.04% 8. Gujarati (gu) 99.81% down 0.01% 9. Czech (cs) 99.65% up 0.09% 10. Chinese Simplified (zh_CN) 99.29% up 0.06% 11. Japanese (ja) 99.23% up 0.08% 12. German (de)98.71% up 1.12% 13. Dutch (nl) 98.51% up 0.10% 14. Hindi (hi) 98.09% up 0.12% 15. Albanian (sq) 98.10% up 2.30% 16. Lithuanian (lt)97.68% up 0.78% 17. Brazilian Portuguese (pt_BR) 97.54% up 0.36% 18. Serbian (sr) 97.51% up 0.25% 19. Chinese Traditional (zh_TW)97.45% up 0.88% 20. Danish (da)97.47% up 0.79% 21. Vietnamese (vi)96.41%no change 22. Catalan (ca) 96.10% up 2.39% 23. Polish (pl)96.05% up 1.73% 24. Punjabi (pa) 96.00% up 0.87% 25. British English (en_GB)95.78% up 0.78% 26. Ukrainian (uk) 94.45% up 2.24% 27. Portuguese (pt)94.24% up 1.50% 28. French (fr)92.12% up 0.76% 29. Nepali (ne)91.80% up 0.76% 30. Korean (ko)91.60% up 0.81% 31. Russian (ru) 91.46% up 1.64% 32. Indonesian (id)90.39% up 3.14% 33. Swedish (sv) 88.91% up 0.01% 34. Macedonian (mk)88.40% up 9.72% 35. Welsh (cy) 86.48% up 0.14% 36. Turkish (tr) 84.35% up 1.61% 37. Romanian (ro) 82.36% up 3.11% Partially supported languages (between 50% and 80%). 38. Estonian (et) 77.83% up 0.88% 39. Galician (gl) 77.34% up 0.53% 40. Italian (it) 75.68% up 0.65% 41. Croatian (hr) 74.27% up 0.57% 42. Tamil (ta) 74.20% up 0.60% 43. Norwegian Nynorsk (nn) 69.08% up 0.57% 44. Basque (eu)66.58% up 0.50% 45. Hebrew (he)66.25% up 0.74% 46. Slovak (sk)65.21% up 0.36% 47. Arabic (ar)65.44% up 0.48% 48. Azerbaijani (az) 65.02% up 0.52% 49. Xhosa (xh) 63.86% up 0.54% 50. Thai (th) 60.15% up 2.14% 51. Malay (ms) 57.50% up 0.49% 52. Bengali (bn) 57.37% up 7.50% 53. Mongolian (mn) 52.54% up 0.35% 54. Bosnian (bs) 52.53% up 0.35% Unsupported languages (less than 50%). 55. Belarusian (be)49.17% up 0.42% 56. Persian (fa) 46.63% up 0.74% 57. Slovenian (sl) 37.09% up 0.30% 58. Telugu (te)35.23% up 0.01% 59. Latvian (lv) 30.62% up 0.25% 60. Wallon (wa)22.62% up 0.19% 61. Afrikaans (af) 19.05% up 2.50% 62. Irish Gaelic (ga) 18.33% up 0.13% 63. Icelandic (is) 17.95% up 0.10% 64. Northern Sotho (nso) 17.68% up 2.31% 65. Malayalam (ml) 15.98% up 0.11% 66. Serbian Jekavian ([EMAIL PROTECTED]) 14.32% up 1.88% 67. Zulu (zu) 12.77% up 1.68% 68. Amharic (am) 12.47% up 0.08% 69. Turkmen (tk) 11.39% up 1.49% 70. Limburgish (li)11.10% up 1.45% 71. Marathi (mr) 10.12% up 1.32% 72. Oriya (or) 9.99% up 1.31% 73. Kinyarwanda (rw)8.98% up 0.07% 74. Uighur (ug) 6.15% up 0.81% 75. Yiddish (yi)5.92% up 0.78% 76. Esperanto (eo) 3
Weekly translation status for Gnome 2.10
Translation status changes from 2005-08-11 to 2005-08-18. Total message count is stable at 32561. Average change during this period was 0.029%. Top 5 movers of the week: * Indonesian (up 1.2%, now supported) * Estonian (up 1.16%, partially supported) * Slovak (up 0.31%, partially supported) * Spanish (up 0.01%, supported) * Northern Sotho (down 0%, unsupported) Supported languages (more than 80% strings translated). 1. Canadian English (en_CA) 100.00%no change Dutch (nl)100.00%no change Gujarati (gu) 100.00%no change Punjabi (pa) 100.00%no change Spanish (es) 100.00% up 0.01% 6. Albanian (sq) 99.99%no change German (de)99.99%no change 8. Chinese Traditional (zh_TW)99.98%no change Danish (da)99.98%no change Czech (cs) 99.98%no change Hungarian (hu) 99.98%no change Serbian (sr) 99.98%no change 13. Brazilian Portuguese (pt_BR) 99.97%no change British English (en_GB)99.97%no change Lithuanian (lt)99.97%no change Portuguese (pt)99.97%no change 17. Finnish (fi) 99.95%no change 18. Greek (el) 99.94%no change Ukrainian (uk) 99.94%no change 20. Japanese (ja) 99.90%no change 21. Catalan (ca) 99.86%no change 22. Korean (ko)99.35%no change 23. French (fr)98.91%no change 24. Bulgarian (bg) 98.85%no change 25. Nepali (ne)98.69%no change 26. Polish (pl)98.50%no change 27. Norwegian Bookmal (nb) 97.04%no change 28. Vietnamese (vi)96.86%no change 29. Russian (ru) 96.07%no change 30. Swedish (sv) 94.44%no change 31. Welsh (cy) 91.96%no change 32. Indonesian (id)91.23% up 1.20% 33. Turkish (tr) 90.46%no change 34. Chinese Simplified (zh_CN) 87.61%no change 35. Romanian (ro) 86.34%no change 36. Italian (it) 85.71%no change 37. Hindi (hi) 83.22%no change 38. Galician (gl) 82.44%no change 39. Tamil (ta) 80.61%no change Partially supported languages (between 50% and 80%). 40. Estonian (et) 78.33% up 1.16% 41. Norwegian Nynorsk (nn) 74.22%no change 42. Basque (eu)72.88%no change 43. Arabic (ar)71.79%no change 44. Azerbaijani (az) 70.81%no change 45. Xhosa (xh) 70.59%no change 46. Macedonian (mk)67.09%no change 47. Malay (ms) 63.05%no change 48. Slovak (sk)63.02% up 0.31% 49. Croatian (hr) 59.57%no change 50. Mongolian (mn) 57.58%no change 51. Bosnian (bs) 57.39%no change 52. Slovenian (sl) 57.20%no change 53. Bengali (bn) 55.47%no change 54. Belarusian (be)54.65%no change Unsupported languages (less than 50%). 55. Persian (fa) 48.09%no change 56. Thai (th) 45.57%no change 57. Hebrew (he)40.94%no change 58. Latvian (lv) 33.74%no change 59. Wallon (wa)23.89%no change 60. Icelandic (is) 21.21%no change 61. Irish Gaelic (ga) 20.50%no change 62. Afrikaans (af) 19.89%no change 63. Malayalam (ml) 17.53%no change 64. Northern Sotho (nso) 17.50%no change 65. Amharic (am) 14.41%no change 66. Serbian Jekavian ([EMAIL PROTECTED]) 14.14%no change 67. Zulu (zu) 13.09%no change 68. Turkmen (tk) 11.54%no change 69. Limburgish (li)11.30%no change 70. Oriya (or) 9.34%no change 71. Kinyarwanda (rw)9.27%no change 72. Marathi (mr)8.76%no change 73. Yiddish (yi)5.24%no change 74. Esperanto (eo) 4.54%no change 75. Telugu (te) 2.94%no change 76. Kannada (kn)
Gucharmap migrated to gnome-doc-utils
Hi, I've just applied a patch to gucharmap, which migrated it to use gnome-doc-utils for help system. -- Tommi Vainikainen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
