Missing fullstops at the end of a help messages #4321
Comments
|
Comment 1 by jteh on 2014-07-28 07:49 That said, while it's annoying that it's inconsistent, changing this for older messages would be a huge burden on translators, as they'd have to re-translate all affected messages just because of the added full stop. |
nvaccessAuto
added
task
component/i18n
|
Jamie wrote in #4321 (comment) "That said, while it's annoying that it's inconsistent, changing this for older messages would be a huge burden on translators, as they'd have to re-translate all affected messages just because of the added full stop." |
|
Hi, I would strive for consistency, but can see the burden it’ll be for us to translate them again. One way is for translators to not mark messages as fuzzy. Thanks.
From: bhavyashah [mailto:notifications@github.com]
Sent: Tuesday, August 29, 2017 8:47 AM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Joseph Lee <joseph.lee22590@gmail.com>; Mention <mention@noreply.github.com>
Subject: Re: [nvaccess/nvda] Missing fullstops at the end of a help messages (#4321)
Jamie wrote in #4321 (comment) <#4321 (comment)> "That said, while it's annoying that it's inconsistent, changing this for older messages would be a huge burden on translators, as they'd have to re-translate all affected messages just because of the added full stop."
Hmm, this might be a valid showstopper for this issue to be taken any further. Thoughts? CC @josephsl <https://github.com/josephsl> and other translators
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#4321 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkA0_iWscQ8G5XprUW_ZQwCX8gYOgks5sdDJWgaJpZM4PGKVd> .
|
|
Wouldn't there be a possibility to undo marking all these cases as fuzzy for every language by means of a script? |
|
Hi, If so, we run into a state where a translator may modify the Gettext file while this is processing, leading to confused Gettext as to what to do. Thanks.
From: Leonard de Ruijter [mailto:notifications@github.com]
Sent: Tuesday, August 29, 2017 10:02 PM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Joseph Lee <joseph.lee22590@gmail.com>; Mention <mention@noreply.github.com>
Subject: Re: [nvaccess/nvda] Missing fullstops at the end of a help messages (#4321)
Wouldn't there be a possibility to undo marking all these cases as fuzzy for every language by means of a script?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#4321 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkLgUzNdgwVPAnF4NhNmhup6Km_CHks5sdOzDgaJpZM4PGKVd> .
|
|
@josephsl commented on 30 aug. 2017 08:13 CEST:
I'm not sure whether I follow this. Processing these case won't take more than a few seconds, and processed gettext files should be pushed to the translation repository instantly. People should always make sure that they are up to date with the current state of the translation repo before doing any work. And still, if they mark messages fuzzy again by accident, they are likely to be able to fix this by hand, since they already seem to work on translation. |
|
Hi, unfortunately, some translators will commit their po files prior to getting later updates (a downside of strictly client/server model employed by Subversion). We can ask translators (via the new mailing list) about this. Thanks.
From: Leonard de Ruijter [mailto:notifications@github.com]
Sent: Tuesday, August 29, 2017 11:31 PM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Joseph Lee <joseph.lee22590@gmail.com>; Mention <mention@noreply.github.com>
Subject: Re: [nvaccess/nvda] Missing fullstops at the end of a help messages (#4321)
<https://github.com/josephsl> @josephsl commented on 30 aug. 2017 08:13 CEST <#4321 (comment)> :
Hi, If so, we run into a state where a translator may modify the Gettext file while this is processing, leading to confused Gettext as to what to do. Thanks.
I'm not sure whether I follow this. Processing these case won't take more than a few seconds, and processed gettext files should be pushed to the translation repository instantly. People should always make sure that they are up to date with the current state of the translation repo before doing any work. And still, if they mark messages fuzzy again by accident, they are likely to be able to fix this by hand, since they already seem to work on translation.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#4321 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkC0BSjU22hNtvANyKycoNnOFMpWwks5sdQGQgaJpZM4PGKVd> .
|
|
May be we should just park this issue until the translation workflow has been moved to github. |
|
Even once the translation workflow moves to GitHub, most translators will
probably still be using svn (via the GitHub svn bridge). The ability to use
svn was a requirement of the switch to avoid translators having to learn
git.
|
Reported by ondrosik on 2014-07-22 10:28
I noticed this during translation. Some help messages have full stop (.) at the end but some don't.
For example:
Reports the comment on the current cell
but
Reports the text of the comment where the System caret is located.
Seems that this is inconsistent in older messages too, for example
Shows the NVDA menu
Shows the long description at this position if one is found.
Reports the current navigator object. Pressing twice spells this information,and pressing three times Copies name and value of this object to the clipboard
I know that this is lov priority, but maybe we should make this consistent later and negotiate, if there should be fullstop at the end of help messages or not.
The text was updated successfully, but these errors were encountered: