From kde-i18n-doc Sat May 09 13:06:40 2020 From: Karl Ove Hufthammer Date: Sat, 09 May 2020 13:06:40 +0000 To: kde-i18n-doc Subject: Re: RFC: New user interface context marker for notification titles: @title:notification/:message? Message-Id: <6e86637b-fdbe-abcd-9c08-8a41867d5a44 () huftis ! org> X-MARC-Message: https://marc.info/?l=kde-i18n-doc&m=158902962930611 Friedrich W. H. Kossebau skreiv 04.05.2020 14:53: > "@title:window" might come closest, given that this is also used usuall= y for > titles of dialog windows, which conceptually overlap a bit with notific= ation > popups, especially the interactive ones. Perhaps the definition of the = scope > could be just extended? "window" as minor term might be a bit off then,= but > possibly still works for coders & translators. > > Otherwise we might want a new dedicated minor category then, :notificat= ion (or > :message?): > :notification - Title of a notification. > > What do you think? A new category =E2=80=98@title:notification=E2=80=99 sounds fine. And =E2=80=98@title:window=E2=80=99 is incorrect. In the screenshot at=20 https://hig.kde.org/platform/notification.html the =E2=80=98@title:window= =E2=80=99=20 (i.e., the window title) is =E2=80=98Discover=E2=80=99, while the notific= ation title is=20 =E2=80=98Updated Available=E2=80=99. It=E2=80=99s very useful to have such UI markers. When I see a string lik= e=20 =E2=80=98Failed to create hotspot %1=E2=80=99, it looks like a normal err= or message=20 where the author has forgotten to add a full stop at the end (=E2=80=98Fa= iled to=20 create hotspot %1.=E2=80=99). So I might add one in the translation (the = English=20 source strings are hugely inconsistent when it comes to punctuation, so=20 I have to do this all the time). But if I see =E2=80=98@title:notificatio= n=E2=80=99, I=20 know that the message is a title, where a full stop at the end is not=20 appropriate (and I might remove it in the translation if it is present=20 in the source string). --=20 Karl Ove Hufthammer