translating file type extensions

[Frederik Schwarzer]

On Tuesday, June 13, 2023 7:15:50 PM CEST Yaron Shahrabani wrote:
> On Tue, Jun 13, 2023, 13:31 Adrian Chaves <adrian at chaves.io> wrote:

Hi,

> > As a translator I have always found it weird that something like (3) was
> > not used. I feel like (2) still has some of the same issues as (1).

> From RTL point of view we need the first option to make sure we are
> terminating the unicode RTL algorithm correctly.
> Otherwise we're seeing things like po.* instead of the correct order.


Well, now we know why it is important to use 1) :)

Thanks for your inputs.

Cheers,
Frederik



> > On 2023-06-13 12:14, Frederik Schwarzer wrote:
> >
> > Hi,
> >
> > from a developer's point of view, what would be the best approach for file
> > types in type selectors in file dialogs?
> >
> > 1) Have them translatable:
> >     i18n("All supported files (*.po *.pot *.xlf *.xliff *.ts)")
> >
> > 2) Have them mentioned:
> >     i18n("All supported files (%1)", "*.po *.pot *.xlf *.xliff *.ts")
> >
> > 3) Hide them completely from translators:
> >     i18n("All supported files", " (*.po *.pot *.xlf *.xliff *.ts)")
> >
> > Currently I see a lot of 1) but am thinking about using 2) since it seems
> > to reduce translation work and is also less prone to errors (translator
> > getting the extensions wrong).
> >
> > Note that in the dialog, the user only sees the "All supported files"
> > string, so one could even argue that the rest is not a user-visible string
> > ... But that could as well be only on my system or it might change in the
> > future.
> >
> > Anyway, is there a problem with 2) that I am currently missing?
> >
> > Thanks.
> >
> > Cheers,
> > Frederik
> >
> >
> >
> >
>