[orca] Created branch gnome-42
The branch 'gnome-42' was created pointing to: d258071... Post-release version bump ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-41
The branch 'gnome-41' was created pointing to: e3f54bc... Post-release version bump ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-40
The branch 'gnome-40' was created pointing to: e0933f1... Release prep ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Status of Danish translation team and open merge request against Orca
Hey Translation Team. Could someone please take a look at this Danish translation merge request a translator submitted for Orca [1], and perhaps also help the submitter coordinate with the right team members going forward? Thanks in advance! --joanie [1] https://gitlab.gnome.org/GNOME/orca/-/merge_requests/114 ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-38
The branch 'gnome-3-38' was created pointing to: 09bbfb4... Web: Fall back on object attributes for absent text attribu ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-36
The branch 'gnome-3-36' was created pointing to: 8d79181... Update our state when input event has to search for the act ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-34
The branch 'gnome-3-34' was created pointing to: 2751a7f... Post-release version bump ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-32
The branch 'gnome-3-32' was created. Summary of new commits: ade193b... Post-release version bump ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-30
The branch 'gnome-3-30' was created pointing to: a1d6c7b... Merge branch 'profile-special-chars' into 'master' ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-28
The branch 'gnome-3-28' was created pointing to: 043487f... Release prep ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-26
The branch 'gnome-3-26' was created pointing to: 3d8d7ec... Post-release version bump ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-24
The branch 'gnome-3-24' was created pointing to: c2c209c... Handle missing events from submenus ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-22
The branch 'gnome-3-22' was created pointing to: 3484179... Post-release version bump ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Orca: Two new strings
Hi Translators! I'm afraid I've just added two new strings to Orca (pasted below). Sorry for the last-minuteness, and thank you (thank you, thank you) for all the work you do! --joanie #. Translators: Orca has a feature to speak the item under the pointer. This feature, #. known as mouse review, can be enabled and disabled via command. The following is #. the message which Orca will present when mouse review is toggled off via command. #: ../src/orca/messages.py:1339 msgid "Mouse review disabled." msgstr "" #. Translators: Orca has a feature to speak the item under the pointer. This feature, #. known as mouse review, can be enabled and disabled via command. The following is #. the message which Orca will present when mouse review is toggled on via command. #: ../src/orca/messages.py:1344 msgid "Mouse review enabled." msgstr ""___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-20
The branch 'gnome-3-20' was created pointing to: e834fd6... Work around Google Maps killing the focused widget ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Import problem - Spanish (es) - orca in gnome-orca trunk
Hey all. On 02/17/2016 10:40 AM, Daniel Mustieles García wrote: > Have no access to my Debian laptop at this momment, and Ubuntu has an > older version of gettext package, but the script I use to upload > translations (ran under Debian Testing) runs an msgfmt check before > uploading, and it didn't shouted any error... don't know why. When I use msgfmt as described, I don't get a syntax error. > Joanmarie: To quickly override it for now, please fix it yourself and > use it to create the package. Done: https://git.gnome.org/browse/orca/commit/?id=3d6f84a67 Thanks everyone! :) --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Fwd: Import problem - Spanish (es) - orca in gnome-orca trunk
Hey all. I was planning to do the Orca release this morning (yeah, I know it's late, sorry!!). But I received this automated notification. Is this something we can fix prior to the release? --joanie Forwarded Message Subject: Import problem - Spanish (es) - orca in gnome-orca trunk Date: Wed, 17 Feb 2016 07:13:27 - From: nore...@launchpad.net Reply-To: nore...@launchpad.net To: jdi...@igalia.com Hello Joanmarie, On 2016-02-16 23:20z (7 hours 52 minutes ago), you uploaded a file with Spanish (es) translations for orca in gnome-orca trunk to Launchpad. We were unable to import the file because of errors in its format: Line 13: Invalid content: u', 2015.' If you use gettext, you can check your file for correct formatting with the 'msgfmt -c' command. Please fix any errors raised by msgfmt and upload the file again. If you check the file and you don't find any error in it, please look for an answer or file a question at https://answers.launchpad.net/rosetta/ For your convenience, you can get the file you uploaded at: http://launchpadlibrarian.net/239473636/es.po Thank you, The Launchpad team ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-18
The branch 'gnome-3-18' was created pointing to: b5a1c8f... Prep for the 3.18.2 release ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
All-clear (was Re: Orca: Heads up re strings for spoken presentation of MathML content)
Hi all. Consensus-reaching is, alas, a slow process. But at the moment, Orca is speaking more or less what other screen readers speak when presenting MathML content. Because I do not anticipate this presentation changing much (if at all) between now and string freeze, I have removed the warnings I was shouting at you. :) Please consider these strings finalized. Thanks!! --joanie On 07/02/2015 02:02 AM, Joanmarie Diggs wrote: Hey all. I just committed some localizable strings to Orca master for spoken presentation of MathML content. As you will see, the translator notes include the following shouted warning: # TRANSLATORS: PLEASE NOTE THAT THIS STRING MAY BE CHANGED PRIOR TO THE 3.18 # RELEASE. IMPLEMENTING SUPPORT FOR SPOKEN MATH IS A CROSS-PLATFORM EFFORT # AND CONSENSUS ABOUT EXACT PRESENTATION HAS NOT YET BEEN REACHED. YOU CAN # CC YOURSELF TO https://bugzilla.gnome.org/show_bug.cgi?id=751816 TO BE # NOTIFIED WHEN STRINGS ARE FINALIZED. Hopefully it's self explanatory. :) As for why I went ahead and marked them for translation before they are potentially ready: As you may know, there are Orca users who are also Orca localizers. Having their input as users about Orca's spoken presentation of MathML content is very valuable to me, and marking the strings now should make it easier for them to provide me with that input. Lastly, in addition to the aforementioned bug, I'll send this list an all-clear when the strings are finalized. And I'll strive to finalize them ASAP. As always, I really appreciate the work you all do for Orca and its users! --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Orca: Heads up re strings for spoken presentation of MathML content
Hey all. I just committed some localizable strings to Orca master for spoken presentation of MathML content. As you will see, the translator notes include the following shouted warning: # TRANSLATORS: PLEASE NOTE THAT THIS STRING MAY BE CHANGED PRIOR TO THE 3.18 # RELEASE. IMPLEMENTING SUPPORT FOR SPOKEN MATH IS A CROSS-PLATFORM EFFORT # AND CONSENSUS ABOUT EXACT PRESENTATION HAS NOT YET BEEN REACHED. YOU CAN # CC YOURSELF TO https://bugzilla.gnome.org/show_bug.cgi?id=751816 TO BE # NOTIFIED WHEN STRINGS ARE FINALIZED. Hopefully it's self explanatory. :) As for why I went ahead and marked them for translation before they are potentially ready: As you may know, there are Orca users who are also Orca localizers. Having their input as users about Orca's spoken presentation of MathML content is very valuable to me, and marking the strings now should make it easier for them to provide me with that input. Lastly, in addition to the aforementioned bug, I'll send this list an all-clear when the strings are finalized. And I'll strive to finalize them ASAP. As always, I really appreciate the work you all do for Orca and its users! --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String freeze break request for 1 string for Orca
On 04/17/2015 11:16 AM, Alexandre Franke wrote: On Fri, Apr 17, 2015 at 3:21 PM, Joanmarie Diggs jdi...@igalia.com wrote: Hey all. Hi Joanie, I can either cause that symbol to not be spoken, or I can mark it for translation. I'm requesting the latter, but I'm fine with the former. Thanks for the detailed explanation, it really helps get a good grasp of the situation. You here have a +1 from i18n to mark it for translation, one more to go. Thanks! # Translators: this is the spoken representation for the character '◾' (U+25fe) _shapes['\u25fe'] = _(black medium small square) You said it's being used as a bullet. Isn't it weird to speak this then? I imagine Things I like colon black medium small square GNOME black medium small square playing guitar and that sounds really weird. In this particular case (user complaint) it is. But apparently this symbol is not always used as a bullet. And if it is used as a symbol, then the detail presumably matters. Furthermore, even when it is being used as a bullet, some users will be interested in knowing the detailed appearance (because they are proofreading a document, because a sighted peer says it's the item with the black square bullet, etc.). So I'm going to add some code whereby users can opt to have bullets presented as bullet. Then it's up to them. For the tell me everything! users, the string shouldn't be in English. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Heads-up re minor cp fail in an Orca translator comment
Hey all.
As you'll see in bug 746091 [1], there was an instance of copy and paste
fail on my part. I'm going to assume you all caught my error and did the
right thing. :) But just in case The change is below.
I'm really sorry. And thanks (as always) for all the work you do for
Orca -- especially with all these math symbols -- and the color names
last cycle. You guys really are the best!
--joanie
--- a/src/orca/mathsymbols.py
+++ a/src/orca/mathsymbols.py
@@ -1848,7 +1848,7 @@ _operators['\u22c6'] = C_('math symbol', 'star
operator')
# Translators: this is the spoken representation for the character '⋇'
(U+22c7)
_operators['\u22c7'] = C_('math symbol', 'division times')
-# Translators: this is the spoken representation for the character '⋇'
(U+22c8)
+# Translators: this is the spoken representation for the character '⋈'
(U+22c8)
_operators['\u22c8'] = C_('math symbol', 'bowtie')
[1] https://bugzilla.gnome.org/show_bug.cgi?id=746091
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-16
The branch 'gnome-3-16' was created pointing to: 54a8898... Post-release version bump ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: String additions to 'orca.gnome-3-14'
Argh! Cherry-pick fail. Sorry. Reverted that one. --joanie On 09/23/2014 09:23 AM, Alexandre Franke wrote: Hey Joanie, I think you broke the freeze with this commit https://git.gnome.org/browse/orca/commit/?h=gnome-3-14id=5de9bc5d0aeba7570a4c4407f765b83771107748 On Tue, Sep 23, 2014 at 2:24 PM, GNOME Status Pages nore...@gnome.org wrote: This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'orca.gnome-3-14': + To enable focus mode press %s. Note that this doesn't directly indicate a string freeze break, but it might be worth investigating. http://git.gnome.org/browse/orca/log/?h=gnome-3-14 ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Orca string-freeze (and technically gui-freeze) break request
Thank you Daniel and Alexandre!!! And thank you entire i18n team for all the work you do. In order to get the string in so that translation can proceed, I've gone ahead and committed the patch to the gnome-3-14 branch. Surely the Release Team will not object to an i18n-approved tiny addition to a hidden GUI that facilitates the switch away from non-Free software to GNU/Linux. ;) But if I'm wrong, I can always comment out the lines which actually add it to the GUI. --joanie On 09/13/2014 06:07 AM, Daniel Mustieles García wrote: 2/2 from i18n Cheers! 2014-09-13 10:13 GMT+02:00 Alexandre Franke alexandre.fra...@gmail.com mailto:alexandre.fra...@gmail.com: On Sat, Sep 13, 2014 at 12:33 AM, Joanmarie Diggs jdi...@igalia.com mailto:jdi...@igalia.com wrote: Hey all. Hi Joanmarie! I've just committed a change to Orca master that I'd like to also commit to Orca's gnome-3-14 branch and include in the approaching release. […] Well, it's getting late, but your explanation seems reasonable and there's only one string with a nice comment for translators, so here's my +1 for i18n. Cheers. -- Alexandre Franke ___ gnome-i18n mailing list gnome-i18n@gnome.org mailto:gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Orca: String-freeze break request
On 09/08/2014 06:31 AM, Frederic Peters wrote: Piñeiro wrote: On 09/07/2014 12:07 PM, Alexandre Franke wrote: On Sun, Sep 7, 2014 at 3:43 AM, Piotr Drąg piotrd...@gmail.com wrote: 2014-09-07 2:45 GMT+02:00 Joanmarie Diggs jdi...@igalia.com: TL;DR: No good deed goes unpunished. Please, please grant this request. https://bugzilla.gnome.org/show_bug.cgi?id=736214 1/2 from i18n. 2/2. 1/2 from release-team For the record approval from the i18n coordination team is enough for string breaks; a notification to the release team is enough. Oops. sheepish grin In that case, consider this notice that I've pushed the change. ;) Thanks guys! And sorry this wasn't caught before the freeze. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Orca: String-freeze break request
TL;DR: No good deed goes unpunished. Please, please grant this request. https://bugzilla.gnome.org/show_bug.cgi?id=736214 Proposed strings (3): +# Translators: Orca's verbosity levels control how much (or how little) +# Orca will speak when presenting objects as the user navigates within +# applications and reads content. The levels can be toggled via command. +# This string describes that command. +TOGGLE_SPEECH_VERBOSITY = _(Toggles speech verbosity level.) +# Translators: Orca's verbosity levels control how much (or how little) +# Orca will speak when presenting objects as the user navigates within +# applications and reads content. The two levels are brief and verbose. +# The following string is a message spoken to the user upon toggling +# this setting via command. +SPEECH_VERBOSITY_BRIEF = C_(Speech, Verbosity level: brief) +# Translators: Orca's verbosity levels control how much (or how little) +# Orca will speak when presenting objects as the user navigates within +# applications and reads content. The two levels are brief and verbose. +# The following string is a message spoken to the user upon toggling +# this setting via command. +SPEECH_VERBOSITY_VERBOSE = C_(Speech, Verbosity level: verbose) Detailed explanation: Clickable elements are those which have an onClick handler. Sadly, these elements tend to be text spans that are not focusable, not discoverable, and thus inaccessible. Orca now announces their presence and provides means to navigate to them and activate them. As a result, these formerly inaccessible elements are now accessible. This new feature was added during the 3.13/3.14 release cycle. And there was much rejoicing. Until From user testing, I've recently learned that certain sites, see Voice of America's learn english content as an example, makes pretty much EVERY word clickable so that (sighted, mouse-using) learners can click on a word and have that word's definition pop up. This unfortunately makes the content unreadable at Orca's verbose level of speech verbosity. (This clickable makes clickable the content clickable unreadable clickable at Orca clickable 's level clickable of speech clickable verbosity clickable .). :( Such sites indicate that it is no longer the case that there is a single verbosity level that should JustWork(tm) for the user. It needs to be toggle-able. I've made this change and committed it to master. I'd really (really, really, really) like to commit it to the 3.14 branch. Please and thank you. :) --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-14
The branch 'gnome-3-14' was created pointing to: a8d9eff... Updated Spanish Translation ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Bug 728557 - Wrong German translation for some ATK role names
Hey guys. Could someone from the German team take a look at bug 728557 and fix it if the filer is correct, or comment on the bug if he is not? Thanks in advance!! --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
All clear (was Re: Documentation updates being made to Orca)
Hi again. We (Attila Hammer and I) have finally completed the Great Orca Documentation review and update. Phew! It is safe for you to proceed. I'm going back to localized-string-free coding. :) Thanks again (and again and again)! --joanie On 03/27/2014 06:52 PM, Joanmarie Diggs wrote: Hey all. I just wanted to give you a heads-up that Orca's documentation is getting a full review to be sure that it is 100% current with respect to content. I don't anticipate there being that many changes, but I plan to commit them as we go. And I have learned by experience that some of you translate changes I make in Orca within mere hours of my committing them. huge, grateful smile In this particular case, since I know there will be some more commits to come, I encourage you to take a very-well-deserved rest now that 3.12 is out the door. When we're done with the Orca documentation review and changes, I'll give y'all the all-clear. Please let me know if you have any questions. And thank you, as always, for all the work you do!!! --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Documentation updates being made to Orca
Hey all. I just wanted to give you a heads-up that Orca's documentation is getting a full review to be sure that it is 100% current with respect to content. I don't anticipate there being that many changes, but I plan to commit them as we go. And I have learned by experience that some of you translate changes I make in Orca within mere hours of my committing them. huge, grateful smile In this particular case, since I know there will be some more commits to come, I encourage you to take a very-well-deserved rest now that 3.12 is out the door. When we're done with the Orca documentation review and changes, I'll give y'all the all-clear. Please let me know if you have any questions. And thank you, as always, for all the work you do!!! --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Two strings added to Orca
Hey all. I just added two strings to Orca's gnome-3-12 branch: # Translators: this is for navigating among links in a document. +LINK_PREV = _(Goes to previous link.) + +# Translators: this is for navigating among links in a document. +LINK_NEXT = _(Goes to next link.) + +# Translators: this is for navigating among links in a document. LINK_LIST = _(Displays a list of links.) Sorry for not getting it in before the announcement period began and, as always, thank you for all your work!! --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-12
The branch 'gnome-3-12' was created pointing to: a49b816... Post-release version bump ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-10
The branch 'gnome-3-10' was created pointing to: 722035f... Updated Indonesian translation ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-8
The branch 'gnome-3-8' was created pointing to: ace8ad6... Updated Russian translation ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Orca string changes (1 new; 2 changed)
Hi Translators! Below are my string changes (sorry!). In the first case, it's a new string (because we had the wrong string before, duh!). In the other two, the phrase to use when speaking calc cells was removed as that feature (and associated strings) applies to more than just Calc. Thanks as always for all you do!! --joanie ~ #. Translators: this is a command for a button on a refreshable braille display #. (an external hardware device used by people who are blind). When pressing the #. button, the display scrolls to the bottom left of the window. #: ../src/orca/cmdnames.py:570 msgid Bottom Left msgstr #. Translators: Orca allows you to dynamically define which row of a spreadsheet #. or table should be treated as containing column headers. This string refers to #. the command to set the row. #: ../src/orca/cmdnames.py:709 msgid Set the row to use as dynamic column headers. msgstr #. Translators: Orca allows you to dynamically define which column of a #. spreadsheet or table should be treated as containing row headers. This #. string refers to the command to set the column. #: ../src/orca/cmdnames.py:720 msgid Set the column to use as dynamic row headers. msgstr ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Error pushing files to gnome-calculator module
On 12/23/2012 07:50 PM, Fran Dieguez wrote: On Dom 23 Dec 2012 19:07:11 CET, Daniel Mustieles García wrote: Still with this problem, can't believe nobody has been able to say something. Could somebody please help me with this issue? [...] Same problem here: $ git push Counting objects: 7, done. Delta compression using up to 8 threads. Compressing objects: 100% (4/4), done. Writing objects: 100% (4/4), 4.17 KiB, done. Total 4 (delta 3), reused 0 (delta 0) error: insufficient permission for adding an object to repository database ./objects fatal: failed to write object error: unpack failed: unpack-objects abnormal exit To ssh://frandieg...@git.gnome.org/git/gnome-calculator ! [remote rejected] master - master (n/a (unpacker error)) error: failed to push some refs to 'ssh://frandieg...@git.gnome.org/git/gnome-calculator' I don't know myself how to solve this problem, but I'm guessing that those who do are not seeing your messages here. If you have not already done so and if the problem persists, you might want to wander over to #sysadmin and see if Andrea Veri or another of the guys can look into it. Sorry, good luck, and thanks again for everything you do! Take care. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
You can remove Orca's xdesktop branch from damned lies
Hey translators! :) Back in the early days of GNOME 3, which was really not at all accessible, I was faced with an unfortunate dilemma: How to provide Orca users features and fixes compatible with GNOME 2.x and still have Orca compatible with GNOME 3.x (introspection, deprecations, etc.). The only thing I could come up with is to have multiple unstable branches. And thus Orca's xdesktop branch was born -- and added to damned lies for translation goodness. (Thank you, thank you, thank you!) Things happily have progressed considerably since then. GNOME 3, while it still has some accessibility issues, is now being used by Orca users. As a result, I am no longer maintaining the xdesktop branch and you can remove it from damned lies. Please let me know if you have any questions. Take care. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Dinner for GNOME i18n/l10n team at GUADEC
On 07/26/2012 04:47 PM, Petr Kovar wrote: Hi all, Joanmarie's suggested time is Sunday 29th July in the evening, hopefully this works for everybody who RSVPed. Joanmarie also asked whether we have a preference w.r.t. restaurant types, cuisine, etc.? Speaking for myself, I don't and we should probably try to reduce items on Joanmarie's to-do list, No worries. My theory is that the winner is the one with the biggest to-do list. And I want to be a winner. :) :) :) I checked with a couple of my colleagues. They suggested: * http://www.restauranteartabria.com * http://www.adegaobebedeiro.com * http://www.miradordesanpedro.es * http://www.nove.biz/en/domus Pick the one which appeals to you and we shall go there. If no one has any idea, the first two were mentioned by both of my colleagues so that could narrow it down. We'll get reservations and taxis, so no need to worry about those sorts of logistics. Big thanks to Joanmarie, the Board and the local team for organizing this! We wish we could do a lot more, because you all do a tremendous amount for us. Take care. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-6
The branch 'gnome-3-6' was created pointing to: 092b1d3... Fix for bug 677748 - Launcher icon needs 256x256 variant ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Strings winding up in the pot file without their translator notes??
After looking at the intltool code and goggling a bit more, seems the problem is: * https://bugs.launchpad.net/intltool/+bug/547073 * https://bugs.launchpad.net/intltool/+bug/377872 Thanks and take care. --joanie On 05/19/2012 02:52 PM, Joanmarie Diggs wrote: On 05/19/2012 03:11 AM, Claude Paroz wrote: You should at least published your temporary work to a branch anywhere, so as we can see and reproduce your issue. It is difficult to answer without even knowing the structure of your orca.in file. Yeah, that would make sense, wouldn't it? ;) Sorry. I was tired and frustrated. I have committed to master one dummy string. What I see in the pot file is: #: ../src/orca/orca.in:72 msgid Why won't the translator note appear like it normally does? msgstr What's in the code is: from orca.orca_i18n import _ # Translators: This is a test string which you should not actually # translate. It is here so we can sort out whatever silly mistake # I am making which is preventing this translator note from showing # up in the .pot file. Sorry and thanks for your help! # https://mail.gnome.org/archives/gnome-i18n/2012-May/msg00085.html string = _(Why won't the translator note appear like it normally does?) Thanks and take care. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Strings winding up in the pot file without their translator notes??
On 05/19/2012 03:11 AM, Claude Paroz wrote: You should at least published your temporary work to a branch anywhere, so as we can see and reproduce your issue. It is difficult to answer without even knowing the structure of your orca.in file. Yeah, that would make sense, wouldn't it? ;) Sorry. I was tired and frustrated. I have committed to master one dummy string. What I see in the pot file is: #: ../src/orca/orca.in:72 msgid Why won't the translator note appear like it normally does? msgstr What's in the code is: from orca.orca_i18n import _ # Translators: This is a test string which you should not actually # translate. It is here so we can sort out whatever silly mistake # I am making which is preventing this translator note from showing # up in the .pot file. Sorry and thanks for your help! # https://mail.gnome.org/archives/gnome-i18n/2012-May/msg00085.html string = _(Why won't the translator note appear like it normally does?) Thanks and take care. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Strings winding up in the pot file without their translator notes??
Hey all. As part of some refactoring I am doing, some code with strings is being moved into Orca's orca.in file. When I run intltool-update -p I get an 'unknown.pot' file which DOES have the strings I'd expect from orca.in. This is not surprising to me because orca.in is in POTFILES.in and NOT in POTFILES.skip. :) The weird thing is that the translator notes which are present in orca.in are not making it along with their strings. I googled some, and I'll google some more after I rest. But in the meantime Am I missing something really obvious?? BTW, I've not committed these changes yet because of the missing translator notes. Thanks in advance! Take care. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: gnome goals for 3.6
Hey Matthias. On 05/15/2012 12:31 AM, Matthias Clasen wrote: At the release team meeting last weekend, we've discussed that we want to revitalize the Gnome Goals [1] effort by adopting a few goals for this cycle. We've chosen the following goals: GSettingsMigration XDGConfigFolders PortToGtkApplication PortToGMenu RemoveMarkupInMessages [...] The last one was included because we want to include our translators, and make their life easier by improving the quality of our strings. +1 I'm doing Orca's right now. I suspect, however, what would make the lives of our translators even easier than the elimination of markup is NoUnexplainedStrings. :) In other words, all strings which we expect translated should have a translator note explaining what that string is and means. Whether or not that can be done in time for 3.6 is not for me to say. But I think it is worthy of consideration as a GNOME Goal. Take care. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-3-4
The branch 'gnome-3-4' was created pointing to: 6dd3aeb... Marking as v3.4.1pre ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Handful of string changes in Orca
Hey all. In my excitement (and desperation) to get Orca's introspection port completed, I'm afraid I forgot to announce a handful of small string changes. (A few new labels in the Orca GUI, updated copyright listing.) :-/ I'm really sorry about that. Tonight I made one minor additional string change Voice Type - Voice type to be consistent with the rest of the GUI's capitalization. Whilst correcting that error, I added a couple of translator notes to define what we mean by voice type. Lastly, due to some pre-GUI-freeze GUI changes, I will need to update Orca's documentation. Today I did the bulk of the string removals. But I still have a bit to write and, mostly, a handful of existing strings to move around. Shaun tells me that String Freeze doesn't apply to documentation strings. Nonetheless, I will do my best to keep the changes to a minimum, finish this work ASAP, and let you all know when it's completed. In the meantime, I wanted to give you the heads up so that you don't update your translations only to find they need re-updating. And for those who like to throw caution to the wind and proceed, the areas to avoid are: * orca/help/C/preferences_general.page * orca/help/C/preferences_speech.page Everything else should be safe. Thanks guys! As always, the Orca team is extremely grateful for all the work you do. Take care. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Orca now has two 'unstable' branches
Hey all. Due the current state of accessibility in GNOME 3.x, the Orca team had a tough decision to make: * Insist that Orca users must use GNOME 3.x to get the latest Orca fixes and features, but have a less accessible GNOME experience. or * Try to maintain two 'unstable' branches, which is a pain for the Orca and i18n teams, but makes it possible for the users to still have the latest Orca fixes and features while some of these GNOME a11y issues get worked out. The Orca team does its work for the users. So Are we thrilled at the prospect of having two unstable branches? Gosh no. Is that what we wound up deciding to do, so that we do the right thing by our users? Yeah. It is. As a result the branches are: master and orca-xdesktop. The plan is this: Any string changes, UI changes, new docs, etc. will go into both branches, so that aspect should remain in sync. What will not be in sync are more under-the-hood, non-translatable things (e.g. gconf versus gsettings, gtk2 versus gtk3, and so on). Given that the strings will remain the same, I am hoping that this will not suck too badly for us. (We'll find out, eh? ;-) ) I also plan to do the releases at the same time, mainly for my own sanity. But also because the act of writing up the translation-updates sections should help me stay on top of any updates that went into master but did not make it into orca-xdesktop. And we'll probably have to cross that bridge when we get to it. But what I was thinking is that if the strings are identical, hopefully I can apply your commits made in Orca master to orca-xdesktop as-is/unchanged. And if that fails, I'll stop by #i18n and/or ping the team in question. This won't be fun, but I think if we work together on this, we can pull it off. Lastly, I stopped by #i18n and explained this turn of events. Claude updated Damned Lies: http://l10n.gnome.org/module/orca/ (Thanks again!!) So that's what the strange, new branch is. ;-) And for anyone who can work this new branch into their routine without much hassle, it will be very much appreciated. On behalf of the Orca team and its users, thanks again for all the work you do! Take care. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Requesting Freeze Breaks for Orca 3.0.0
Hi Release Team (and i18n Team): The Orca team has three changes which we'd really like to include in the 3.0.0 release today: 1. Bug 646547 - typo in src/orca/orca_gui_prefs.py https://bugzilla.gnome.org/show_bug.cgi?id=646547 Silly typo and grammar mistake. I suspect the i18n team got it right in their languages. :-) We failed in English, however. 2. Bug 646475 - Traceback seen with gnome-speech https://bugzilla.gnome.org/show_bug.cgi?id=646475 It's a two-line, safe change. And while gnome-speech is deprecated you still find it out there in the distros. 3. Bug 646288 - Orca needs to set and respond to the appropriate gsettings keys https://bugzilla.gnome.org/show_bug.cgi?id=646288 This will cause Orca to shut itself off when the UAP screen reader off-switch is turned off as well as to change the appropriate gsettings key so that the aforementioned switch displays the right thing when users launch Orca via some other means. In addition, we caught a couple of instances where we were still checking/setting gconf keys. While this is a bigger change, it's not huge. And while it will not solve all the current accessibility issues, it will make them somewhat less pronounced. ;-) Thank you very much in advance for your consideration of the above! --joanie, on behalf of the Orca Team ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Requesting Freeze Breaks for Orca 3.0.0
On Mon, 2011-04-04 at 14:24 -0400, Matthias Clasen wrote: On Mon, Apr 4, 2011 at 2:15 PM, Joanmarie Diggs joan...@gnome.org wrote: Hi Release Team (and i18n Team): The Orca team has three changes which we'd really like to include in the 3.0.0 release today: 1. Bug 646547 - typo in src/orca/orca_gui_prefs.py https://bugzilla.gnome.org/show_bug.cgi?id=646547 Silly typo and grammar mistake. I suspect the i18n team got it right in their languages. :-) We failed in English, however. For this change, you should do the necessary .po file gymnastics to update all msgids, to keep translations from breaking. Okay, if I get my +2 I will check with the i18n team to be sure I know what those gymnastics are. 2. Bug 646475 - Traceback seen with gnome-speech https://bugzilla.gnome.org/show_bug.cgi?id=646475 It's a two-line, safe change. And while gnome-speech is deprecated you still find it out there in the distros. This one I cannot really judge without knowing what ACSS is or does. But I will point out that Cosimo reported orca tracebacks after I removed the gnome-speech dependency from our package - is that the same issue ? Dunno. I'd have to see what the tracebacks are. ACSS is just a voice definition. http://git.gnome.org/browse/orca/tree/src/orca/acss.py 3. Bug 646288 - Orca needs to set and respond to the appropriate gsettings keys https://bugzilla.gnome.org/show_bug.cgi?id=646288 This will cause Orca to shut itself off when the UAP screen reader off-switch is turned off as well as to change the appropriate gsettings key so that the aforementioned switch displays the right thing when users launch Orca via some other means. In addition, we caught a couple of instances where we were still checking/setting gconf keys. While this is a bigger change, it's not huge. And while it will not solve all the current accessibility issues, it will make them somewhat less pronounced. ;-) I must say this one should have landed shortly after we added the switch back. But better late than never. I'm willing to accept this one, since it makes the switch work properly. Understood. Apologies for that. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Requesting Freeze Breaks for Orca 3.0.0
3. Bug 646288 - Orca needs to set and respond to the appropriate gsettings keys https://bugzilla.gnome.org/show_bug.cgi?id=646288 I'm not sure I understand well: in init(), you are changing the screen-reader-enabled key to True. I'd expect init() to work only if screen-reader-enabled is set to True, not init() to set the key. Is this really right? Most Orca users who are blind will not be using the UAP to toggle the screen reader on: In order to access the switch to turn the screen reader on, a user who is blind must have a screen reader on already. Bit of a cart/horse chicken/egg situation at the moment. When the switch is turned on by other users in the UAP, an autostart file launches Orca. When the user launches Orca via terminal window or run dialog, should we fail to set the key, the UAP switch will say 'off' even though the screen reader is 'on'. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Requesting Freeze Breaks for Orca 3.0.0
Sorry to be so spammy today. On Mon, 2011-04-04 at 14:24 -0400, Matthias Clasen wrote: On Mon, Apr 4, 2011 at 2:15 PM, Joanmarie Diggs joan...@gnome.org wrote: [...] 1. Bug 646547 - typo in src/orca/orca_gui_prefs.py https://bugzilla.gnome.org/show_bug.cgi?id=646547 Silly typo and grammar mistake. I suspect the i18n team got it right in their languages. :-) We failed in English, however. For this change, you should do the necessary .po file gymnastics to update all msgids, to keep translations from breaking. I believe I have done so thanks to the advice of the wonderful people in #i18n: http://bugzilla-attachments.gnome.org/attachment.cgi?id=185150 As I read the freeze break rules for strings, I need one more approval from the i18n team (correct?) Thanks again! --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
[orca] Created branch gnome-2-32
The branch 'gnome-2-32' was created pointing to: ab750f5... Marking as Orca v2.32.0pre ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
(Approved) string change in Orca
Hi all. As discussed [1] on the gnome-18n list, we had been told [2] that one of the strings in Orca is too long and needed to be changed. I have received the requisite two responses. [3][4] Therefore, the following change has just been committed to master: -_(Enable notification message list mode. \ - Press Escape to exit or h for help)) +_(Present notification messages list)) Sorry for any inconvenience. --joanie [1] http://mail.gnome.org/archives/gnome-i18n/2010-September/msg00027.html [2] https://bugzilla.gnome.org/show_bug.cgi?id=628589 [3] http://mail.gnome.org/archives/gnome-i18n/2010-September/msg00060.html [4] http://mail.gnome.org/archives/gnome-i18n/2010-September/msg00064.html ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
FWIW Orca has NOT broken string freeze
Hey all. I saw this in the list digest. For the record, we have not added any new strings to Orca since the string freeze. In fact, we haven't touched magnification strings in a couple of years if memory serves me. (And, yes, I see that it's an automatic message. I'm merely responding to the might be worth investigating bit.) HTH. Take care. --joanie (who always tries to follow the rules :-) ) This is an automatic notification from status generation scripts on: http://l10n.gnome.org. There have been following string additions to module 'orca.master': + Magnification::bBorder/b + Magnification::bColor/b + Magnification::bCross-hair/b + Magnification::bCursor/b + Magnification::bZoomer/b + Magnification::Advanced... + ProgressBar::Frequency (secs): + ProgressBarUpdates::Enable_d 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 freeze break request for Orca
Hi all. I'm afraid we've been told that one of the strings in Orca is too long, at least in Hungarian. [1] The person reporting it is both a translator and an Orca user. The proposed solution is the removal of the long string in favor of a shorter one: -_(Enable notification message list mode. \ - Press Escape to exit or h for help)) +_(Present notification messages list)) I am requesting permission to break string freeze to address this issue. Thanks in advance. With apologies, --joanie. [1] https://bugzilla.gnome.org/show_bug.cgi?id=628589 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
New strings in Orca
Hey all. This is the last of 'em. For real this time... :-) Bug 628275 - Orca should be more forgiving when invalid options and arguments are specified #. Translators: This message is displayed when the user #. tries to enable or disable a feature via an argument, #. but specified an invalid feature. Valid features are: #. speech, braille, braille-monitor, magnifier, main-window, #. and splash-window. These items are not localized and are #. presented in a list after this message. #. #: ../src/orca/orca.py:2145 msgid The following items can be enabled or disabled: msgstr #. Translators: This message is displayed when the user tries #. to start Orca and includes an invalid option as an argument. #. After the message, the list of arguments, as typed by the #. user, is displayed. #. #: ../src/orca/orca.py:2089 msgid The following arguments are not valid: msgstr Bug 627451 - Orca needs a way to repeat the latest notification messages #. Translators: Orca can present the last notification message #. to the user when the user presses a shortcut key. #. #: ../src/orca/notification_messages.py:82 msgid Present last notification message. msgstr #. Translators: Orca can present the previous notification message #. to the user when the user presses a shortcut key. #. #: ../src/orca/notification_messages.py:90 msgid Present previous notification message. msgstr #. Translators: Orca can enable the notification messages #. list mode when the user presses a shortcut key. #. #: ../src/orca/notification_messages.py:98 msgid Enable notification message list mode. Press Escape to exit or h for help msgstr #. Translators: This is a brief message presented to the user #. the list of notifications is empty. #. #: ../src/orca/notification_messages.py:129 msgid No notification messages msgstr #. Translators: This is a brief message presented to the user when #. when the top of a list of notifications is reached. #. #: ../src/orca/notification_messages.py:160 msgctxt notification msgid Top msgstr #. Translators: This is a brief message presented to the user when #. when the bottom of a list of notifications is reached. #. #: ../src/orca/notification_messages.py:167 msgctxt notification msgid Bottom msgstr #. Translators: Orca has a List notification messages Mode that allows #. the user to list the latest notification messages received. #. Escape exits this mode. #. This string is the prompt which will be presented to the user #. in both speech and braille upon exiting this mode. #. #: ../src/orca/notification_messages.py:190 msgid Exiting list notification messages mode. msgstr #. Translators: This message inform to the user the number of #. messages in the list. #: ../src/orca/notification_messages.py:244 #, python-format msgid %d message.\n msgid_plural %d messages.\n msgstr[0] msgstr[1] #. Translators: This is a help message. #: ../src/orca/notification_messages.py:246 msgid Press h for help.\n msgstr #. Translators: The following string instructs the user how to navigate #. amongst the list of commands presented in list notification #. messages mode as well as how to exit the list. #. #: ../src/orca/notification_messages.py:253 msgid Use Up, Down, Home or End to navigate in the list.\n Press Escape to exit.\n Press Space to repeat the last message read.\n Press one digit to read a specific message.\n msgstr Thanks very much! Y'all rock!! Take care. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
UI Changes and new strings in Orca
Hey all. We have a handful of new strings and UI changes in Orca: * Bug 577705 - When Orca starts, it doesn't get to the component with focus A splash screen was added. Yeah, yeah, I know. A splash screen is *exactly* what blind users need. ;-) But it causes an accessible window:activate event to be triggered when it goes away -- which is indeed exactly what our users need. Plus it's pretty. :-) * Bug 543157 - It is not always possible to distinguish on-screen text from Orca's system messages We added a configurable 'system' voice. It is an option (not immediately visible; simply available) in the Voice Settings: combo box of the Speech page of the Orca Preferences dialog. Which of course required a new string: #. Translators: This refers to the voice used by Orca when #. presenting information which is not displayed on the screen #. as text, but is still being communicated by the system in #. some visual fashion. For instance, Orca says misspelled #. to indicate the presence of the red squiggly line found #. under a spelling error; Orca might say 3 of 6 when a #. user Tabs into a list of six items and the third item is #. selected. And so on. #. #: ../src/orca/orca_gui_prefs.py:773 msgctxt VoiceType msgid System msgstr * Bug 520595 - Orca is far too chatty for persons with learning disabilities Turns out that users who happen to have a print-related learning disability would like us to stop speaking system messages. So we added a new checkbox to the Speech page of the Orca Preferences dialog whereby users could disable this. We also changed the order of other checkboxes on that page so as to group systemy things together. The new checkbox, of course, required a new string: #. Translators: If this setting is enabled, Orca will only speak text which is actually displayed on the screen. It will NOT speak things like the role of an item (e.g. 'checkbox') or its state (e.g. 'not checked') or say 'misspelled' to indicate the presence of red squiggly spelling error lines -- things which Orca normally speaks. This setting is primarily intended for low vision users and sighted users with a learning disability. #: ../src/orca/orca-setup.ui.h:101 msgid Only speak displayed text msgstr My apologies for not getting this announcement to you sooner. And I do realize that, technically, it is being made 1.5 hours after the start of UI Freeze. I would ask that you be forgiving of me as I needed some last-minute rescuing from my co-maintainer related to make distcheck. This announcement tardiness will not happen again. Thanks very much! As always, we really appreciate the work y'all do! Take care. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Modified strings in Orca
Hi all. Bug 626272 brought to our attention that a handful of strings lacked the plural forms required for correct localization. Our apologies. The change has just been committed to master. Thanks for all your work! --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
New strings in Orca
Hey all. We've had to add some additional strings as part of the fixes for the following bugs: * bug 625729 - Orca does not present superscripted and subscripted numbers in gcalctool * bug 625737 - Orca should attempt to clump superscripted and subscripted numbers together #. Translators: This string is part of the presentation of an #. item that includes one or several consequtive superscripted #. characters, e.g. 'X' followed by 'superscript 2' followed by #. 'superscript 3' should be presented as 'X superscript 23'. #. #: ../src/orca/script_utilities.py:2523 #, python-format msgid superscript %s msgstr #. Translators: This string is part of the presentation of an #. item that includes one or several consequtive subscripted #. characters, e.g. 'X' followed by 'subscript 2' followed by #. 'subscript 3', should be presented as 'X subscript 23.' #. #: ../src/orca/script_utilities.py:2533 #, python-format msgid subscript %s msgstr #. Translators: this is the spoken word for the character '⁰' (U +2070) #. #: ../src/orca/chnames.py:733 msgid superscript 0 msgstr [...] #. Translators: this is the spoken word for the character '₉' (U +2089) #. #: ../src/orca/chnames.py:821 msgid subscript 9 msgstr Sorry we didn't get these in sooner. And thanks, as always, for all your work! Take care. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Do enabled, disabled, and not found need to be qualified per instance?
Hey all.
Silly question: Do enabled, disabled, and not found need to be
qualified per instance?
More context: Orca speaks and brailles various confirmation messages
when the user changes a setting on the fly or executes certain commands.
Examples:
User: enables/disables speech temporarily
Orca: speech {enabled,disabled}
User: enables/disables indentation and justification info temporarily
Orca: Speaking of indentation and justification {enabled,disabled}
User: Attempts to move to the next heading, but there isn't a next one
Orca: No more headings found
User: Attempts to move to the next list, but there isn't a next one
Orca: No more lists found
Etc., etc.
Some users like a lot of detail. But for experienced users and/or users
with really small braille displays, some of these strings are
unnecessarily long. Therefore, we're going to start providing optional,
brief messages.
User: enables/disables whatever by giving the command to do so
Orca: {enabled,disabled}
User: Attempts to move to the next whatever, but there isn't a next one
Orca: not found
Will the translation of enabled, disabled, and not found vary in
some languages depending on what was enabled, disabled, or not found?
Apologies for being a stereotypical, monolingual American. And thanks in
advance for your help!
--joanie
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Do enabled, disabled, and not found need to be qualified per instance?
Hey Petr. Thanks so much for the info! However, as long as those adjectives like enabled or disabled aren't incorporated into a sentence or sentence fragment, but are placed in a string of their own, it's often the case in i18n not to qualify per instance and respect various gender and declension forms, but to use a general, one-gender, one-case term that refers to all strings with the appropriate meaning. (In my West Slavic language [Czech], we often make use of the neuter gender singular nominative case for that purpose.) Right. These words won't be part of a sentence or fragment. So the gender and number (if required in a particular language) would be for an object which is understood by the user, but not explicitly stated/included in the string. Nevertheless, I wouldn't count that in best i18n/l10n practices, really. The Orca team aims to do what's best practice. Therefore we will qualify each instance. Thanks! Follow-up question w.r.t. not found: There are (at least) a couple of general categories of things for which we might want to say not found: 1. Performing a search for text displayed on screen (e.g. in a widget that wouldn't otherwise be searchable by the user) 2. Looking for a 'structural navigation' object. As stated above, we will qualify each. Something like: C_(text, not found) C_(structural navigation, not found) with each having the appropriate, context-specific translator note explaining exactly what that not found string is all about. The thing is, there are a bunch of structural navigation objects in Orca which can be not found. In particular: * Anchors * Blockquotes * Buttons * Check boxes * Chunks/Large Objects * Combo boxes * Entries * Form fields * Headings (regardless of level) * Headings at a particular level * Landmarks * Lists * List items * Radio buttons * Separators * Tables * Table cells * Unvisited links * Visited links What those items have in common is that they're all things in a document (most often a web page) that a user attempted to move to using Orca's structural navigation feature. With that in mind, which is best practice: C_(structural navigation, not found) or: C_(anchor, not found) C_(blockquote, not found) C_(button, not found) [...] And/or is there a certain point at which best practice loses out to there are already a bazillion strings in Orca. Please stop with the new strings already. silly grin Either way, let us know what you prefer and we'll be happy to do it. (For what it's worth, structural navigation is the most extreme example. I'm not anticipating that there will be that many additional, short strings resulting from this new setting.) In the end, a context is what counts the most for translators. Also, I think that Orca is the excellent example of providing a good portion of useful context information to their translators, so thanks for that. No need to thank us. We do it out of gratitude and appreciation for your work. You guys make it possible for blind computer users around the world to have independent access to software and information in their preferred language. I think that's amazing. --joanie ___ 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
New string in Orca
Sorry for this last-minute one: #. Translators: Orca has had to implement its own caret navigation #. model to work around issues in Gecko/Firefox. In certain versions #. of Firefox, we must perform a focus grab on each object being #. navigated in order for things to work as expected; in other #. versions of Firefox, we must avoid doing so in order for things #. to work as expected. We cannot identify with certainty which #. situation the user is in, so we must provide this as an option #. within Orca. #. #: ../src/orca/scripts/toolkits/Gecko/script.py:855 msgid _Grab focus on objects when navigating msgstr Thanks again (and again, and again, and ...) for all your work! --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
New string in Orca
Hi all. Yesterday a critical Atk bug was fixed (bug #591105). Phew! As a result, however, there is a new string which Orca users may come across. Therefore, I'm afraid we have another new string: #. Translators: this is one of the text attribute values for the following #. text attributes: wrap mode. It corresponds to GTK_WRAP_WORD_CHAR, #. defined in the Gtk documentation as Wrap text, breaking lines in #. between words, or if that is not enough, also between graphemes. #. See: #. http://library.gnome.org/devel/atk/1.27/AtkText.html#AtkTextAttribute #. http://library.gnome.org/devel/gtk/stable/GtkTextTag.html#GtkWrapMode #. #: ../src/orca/text_attribute_names.py:443 msgctxt textattr msgid word char msgstr As always, we really appreciate all you do! Thanks and take care. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
New strings and a UI change in Orca
The fix for bgo#574344 required some new strings and a UI change. Regarding the UI change, the Orca team maintains the docs and will be updating them soon. As for the new strings: #. Translators: Orca has a setting which determines which progress #. bar updates should be announced. The options are all progress #. bars, only progress bars in the active application, or only #. progress bars in the current window. #. #: ../src/orca/orca_gui_prefs.py:1559 ../src/orca/orca-setup.ui.h:93 msgid Restrict progress bar updates to: msgstr #. Translators: Orca has a setting which determines which progress #. bar updates should be announced. Choosing All means that Orca #. will present progress bar updates regardless of what application #. and window they happen to be in. #. #: ../src/orca/orca_gui_prefs.py:1571 ../src/orca/orca_gui_prefs.py:3008 msgctxt ProgressBar msgid All msgstr #. Translators: Orca has a setting which determines which progress #. bar updates should be announced. Choosing Application means #. that Orca will present progress bar updates as long as the #. progress bar is in the active application (but not necessarily #. in the current window). #. #: ../src/orca/orca_gui_prefs.py:1578 msgctxt ProgressBar msgid Application msgstr #. Translators: Orca has a setting which determines which progress #. bar updates should be announced. Choosing Window means that #. Orca will present progress bar updates as long as the progress #. bar is in the active window. #. #: ../src/orca/orca_gui_prefs.py:1584 ../src/orca/orca_gui_prefs.py:3016 msgctxt ProgressBar msgid Window msgstr Thanks for all your work! Take care. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
New string in Orca
Hi all. Just... one... more string. (I just jinxed myself didn't I?) :-) As part of the fix for bgo bug #590382: #. Translators: This is the tutorial string associated with a #. specific search field in the Packagemanager application. #. It is designed to inform the user how to move directly to #. the search results after the search has been completed. #. #: ../src/orca/scripts/apps/packagemanager/tutorialgenerator.py:60 msgid Use Ctrl+L to move focus to the results. msgstr Thanks again for all your work! Take care. --joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
New strings in Orca
Hi all. I didn't realize that the string announcement period had already begun. Sorry! There are a number of string changes in Orca since the 13th: From bgo bug #588403: #. Translators: this command will move the mouse pointer #. to the current item without clicking on it. #. #: ../src/orca/default.py:151 msgid Routes the pointer to the current item. msgstr #. Translators: Orca has a command that allows the user #. to move the mouse pointer to the current object. If #. for some reason Orca cannot identify the current #. location, it will speak this message. #. #: ../src/orca/default.py:5181 ../src/orca/default.py:5202 #: ../src/orca/default.py:5222 msgid Could not find current location. msgstr From bgo bug #582506 (Use GtkBuilder instead of libglade): These are technically not new strings. But in the process of the conversion, I concluded that merely marking such generic words for translation wasn't ideal. So I gave them context. #. Translators: This refers to the default/typical voice used #. by Orca when presenting the content of the screen and other #. messages. #. #: ../src/orca/orca_gui_prefs.py:721 msgctxt VoiceType msgid Default msgstr #. Translators: This refers to the voice used by Orca when #. presenting one or more characters which is in uppercase. #. #: ../src/orca/orca_gui_prefs.py:725 msgctxt VoiceType msgid Uppercase msgstr #. Translators: This refers to the voice used by Orca when #. presenting one or more characters which is part of a #. hyperlink. #. #: ../src/orca/orca_gui_prefs.py:730 msgctxt VoiceType msgid Hyperlink msgstr From bgo bug #585417: #. Translators: different speech systems and speech engines work #. differently when it comes to handling pauses (e.g., sentence #. boundaries). This property allows the user to specify whether #. speech should be sent to the speech synthesis system immediately #. when a pause directive is enountered or if it should be queued #. up and sent to the speech synthesis system once the entire set #. of utterances has been calculated. #. #: ../src/orca/orca_gui_prefs.py:1529 ../src/orca/orca-setup.ui.h:26 msgid Break speech into ch_unks between pauses msgstr From bgo bug #585049: #. Translators: when the user selects (highlights) text in #. a document, Orca will speak information about what they #. have selected. #. #: ../src/orca/default.py:7774 msgid paragraph selected down from cursor position msgstr #: ../src/orca/default.py:7775 msgid paragraph unselected down from cursor position msgstr #: ../src/orca/default.py:7776 msgid paragraph selected up from cursor position msgstr #: ../src/orca/default.py: msgid paragraph unselected up from cursor position msgstr From bgo bug #588910: #. Translators: this is to inform the user of the presence #. of the red squiggly line which indicates that a given #. word is not spelled correctly. #. #: ../src/orca/default.py:4084 ../src/orca/default.py:8301 msgid misspelled msgstr #. Translators: this attribute specifies there is something wrong with #. the text, such as it being a misspelled word. See: #. https://developer.mozilla.org/en/Accessibility/AT-APIs/Gecko/TextAttrs #. #: ../src/orca/text_attribute_names.py:133 msgctxt textattr msgid mistake msgstr Note that the above mistake is a replacement for what used to be invalid which was removed as part of this bug. From bgo bug #575784: #. Translators: this is how someone would speak the name of the #. non-spacing diacritical key for the acute glyph #. #: ../src/orca/keynames.py:255 msgid acute msgstr #. Translators: this is how someone would speak the name of the #. non-spacing diacritical key for the circumflex glyph #. #: ../src/orca/keynames.py:260 msgid circumflex msgstr #. Translators: this is how someone would speak the name of the #. non-spacing diacritical key for the diaeresis glyph #. #: ../src/orca/keynames.py:270 msgid diaeresis msgstr #. Translators: this is how someone would speak the name of the #. non-spacing diacritical key for the ring glyph #. #: ../src/orca/keynames.py:275 msgid ring msgstr #. Translators: this is how someone would speak the name of the #. non-spacing diacritical key for the stroke glyph #. #: ../src/orca/keynames.py:285 msgid stroke msgstr #. Translators: When this option is enabled, dead keys will be #. announced when pressed. #. #: ../src/orca/orca_gui_prefs.py:1654 ../src/orca/orca-setup.ui.h:62 msgid Enable non-spacing _diacritical keys msgstr #. Translators: When this option is enabled, inserted text of length #. 1 is spoken. #. #: ../src/orca/orca_gui_prefs.py:1662 ../src/orca/orca-setup.ui.h:60 msgid Enable echo by cha_racter msgstr From bgo bug #586399: #. Translators: hovering the mouse over certain objects #. on
String change in Orca
Hi all. In the spirit of a more user-friendly Orca Preferences dialog, we've gotten rid of the string update interval:, replacing it with every. :-) ~~ #. Translators: Here 'every' labels a spin button through which a user can customize the frequency in seconds an announcement should be made. (The spin button is followed by the label 'seconds'.) Thus if a user chooses 5 in the spin button, the complete phrase would be 'every 5 seconds'. #: ../src/orca/orca-setup.glade.h:178 msgid every msgstr ~~ As always, the Orca team is very grateful for all the work y'all do! Take care. --Joanie ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
