mirror of
https://git.lyx.org/repos/lyx.git
synced 2024-11-29 05:01:49 +00:00
This string composition badly fails on some languages since as a translator
you have no clue about the context for the proper grammatical case. I'm not particularly happy about the fix, but didn't see much better alternatives. git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@36532 a592a061-630c-0410-9148-cb99ea01b6c8
This commit is contained in:
parent
f5ad7f949e
commit
8435660410
@ -272,23 +272,23 @@ docstring getQuestionString(FindAndReplaceOptions const & opt)
|
|||||||
docstring scope;
|
docstring scope;
|
||||||
switch (opt.scope) {
|
switch (opt.scope) {
|
||||||
case FindAndReplaceOptions::S_BUFFER:
|
case FindAndReplaceOptions::S_BUFFER:
|
||||||
scope = _("file[[scope]]");
|
scope = _("File");
|
||||||
break;
|
break;
|
||||||
case FindAndReplaceOptions::S_DOCUMENT:
|
case FindAndReplaceOptions::S_DOCUMENT:
|
||||||
scope = _("master document[[scope]]");
|
scope = _("Master document");
|
||||||
break;
|
break;
|
||||||
case FindAndReplaceOptions::S_OPEN_BUFFERS:
|
case FindAndReplaceOptions::S_OPEN_BUFFERS:
|
||||||
scope = _("open files[[scope]]");
|
scope = _("Open files");
|
||||||
break;
|
break;
|
||||||
case FindAndReplaceOptions::S_ALL_MANUALS:
|
case FindAndReplaceOptions::S_ALL_MANUALS:
|
||||||
scope = _("manuals[[scope]]");
|
scope = _("Manuals");
|
||||||
break;
|
break;
|
||||||
}
|
}
|
||||||
docstring message = opt.forward ?
|
docstring message = opt.forward ?
|
||||||
bformat(_("End of %1$s reached while searching forward.\n"
|
bformat(_("%1$s: the end was reached while searching forward.\n"
|
||||||
"Continue searching from the beginning?"),
|
"Continue searching from the beginning?"),
|
||||||
scope) :
|
scope) :
|
||||||
bformat(_("Beginning of %1$s reached while searching backward.\n"
|
bformat(_("%1$s: the beginning was reached while searching backward.\n"
|
||||||
"Continue searching from the end?"),
|
"Continue searching from the end?"),
|
||||||
scope);
|
scope);
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user