Such things are necessary for proper localization, since there are not only alphabetic scripts and, as Richard mentions, not only LTR scripts. The fact that none of our translations uses this opportunity (yet) does not mean that it is not necessary. We do not have very much (complete) non-alphabetic and non-LTR localizations, unfortunately.
In this case, however, you can probably commit your patch, since the qt file dialog probably expects this very format structure for the filter items. Jürgen 2013/10/10 Pavel Sanda <sa...@lyx.org> > Richard Heck wrote: > > On 10/10/2013 01:20 AM, Pavel Sanda wrote: > >> Hi, > >> > >> I don't see any reason for translating the following construct and will > >> commit it soon unless someone screems. > > > > I won't scream, but I think this kind of thing usually gets done for RTL > > sorts of reasons, or because different languages have different > conventions > > with parentheses, etc. > > I can understand this plays role when you have some sentence with bunch > of parameters but I'm somewhat sceptic that translators seeing > > #: src/frontends/qt4/GuiView.cpp:2403 > #, fuzzy, c-format > msgid "%1$s (*.%2$s)" > msgstr "%1$s (*.%2$s)" > > have idea in which context will be the string used. > > Greping through .po files I don't see single translation doing anything > reasonable except of sk.po where there is a typo (missing *). > Not particularly convincing. > > Pavel >
