[Bug 168080] Presentation/template shows placeholder text in creator's (?) locale rather than in the UI locale

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Mon Aug 25 08:46:40 UTC 2025


https://bugs.documentfoundation.org/show_bug.cgi?id=168080

Eyal Rozenberg <eyalroz1 at gmx.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|enhancement                 |minor

--- Comment #2 from Eyal Rozenberg <eyalroz1 at gmx.com> ---
(In reply to Heiko Tietze from comment #1)

> I agree with the use case. Sometimes you might want to configure a template
> for a certain language but often it should be using the setting from the
> workstation.

Let us think about the first part of that statement. When we're talking about
placeholder text - which the user has not even entered themselves and was just
generated by LO - when is it ever the case that the creator of the template
wants to force other people to see the placeholder text in the creator's
language? I can't think of such a situation, or of the benefit. (If it were the
creator providing the placeholder text, that would be something else.)

> Text boxes take the language defined for new documents in tools > options >
> language & locales.

1. I am reminded of bug 144814 ...
2. Which language exactly, within that part of the options dialog?
3. Isn't it the case that _no_ language is taken, because of the language
trichotomy? i.e. what's taken is only the choice of language within each group
4. Is this is true for the choice of language in placeholder text as well?

> We could either not store resp. remove the locale
> settings (as Laurent did manually for the shipped templates). In this case
> you cannot create a template for a certain language, which is odd.

... although it's already actually the case, because of the language
trichotomy, IIANM.

> Or we
> introduce some "Automatic" language option (or some other flag), and do not
> store the attributes then.

Do you mean introduce a property for objects?

But - why should placeholder text respect the language/locale of the object in
which it's rendered? And what if that language doesn't support freestyle text,
e.g. it's music, or a programming language?

---

Finally, I believe this counts as a bug: This behavior is not something the
creator intended; nor something the user of the template or presentation wants.
It might not be a coding bug, but a planning/feature design bug - and still, a
bug.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Libreoffice-ux-advise mailing list