Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15371 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2019-09-16 09:37 -0400 |
| Last post | 2019-09-16 09:37 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Untranslatable string in help.def Chet Ramey <chet.ramey@case.edu> - 2019-09-16 09:37 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2019-09-16 09:37 -0400 |
| Subject | Re: Untranslatable string in help.def |
| Message-ID | <mailman.347.1568641074.2190.bug-bash@gnu.org> |
On 9/15/19 12:50 PM, Roland Illig wrote:
> Hi,
>
> in help.def, the code reads:
>
> if (glob_pattern_p (list->word->word))
> {
> printf ("%s", ngettext ("Shell commands matching keyword `",
> "Shell commands matching keywords `", (list->next ? 2 : 1)));
> print_word_list (list, ", ");
> printf ("'\n\n");
> }
>
> The strings for translations should always be a complete sentence since
> in some languages the word order can differ.
It's difficult to provide a translation for a string whose contents are
determined at runtime based on user input. That's why we're using
ngettext here, so we can try to get the appropriate plural form. I can
certainly change the single quote to be translatable, so that might
provide the desired flexibility.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to top | Article view | gnu.bash.bug
csiph-web