[Libreoffice-ux-advise] [Bug 101442] Hyperlink is terribly dated vocabulary

[bugzilla-daemon at bugs.documentfoundation.org]

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

--- Comment #17 from Björn Michaelsen <bjoern.michaelsen at canonical.com> ---
(In reply to Andras Timar from comment #7)
> The word "link" is overloaded already, you can link Writer text frames so
> that their contents automatically flow from one frame to another, you can
> link images instead of embedding them, now we'll introduce a 3rd meaning.

So in common english language, "link" is already understood to mean "hyperlink"
-- they are used synonymously by the public. Someone reading "link" these days
will assume it to be a hyperlink and be confused if it is not.

Along those lines, if we want to have specific vocabulary, we should have good
consistent and specific names for links that are NOT hyperlinks. Namely "linked
text frames" should have a explicit name making clear they are _not_
hyperlinks. As for linked (not embedded) images: Those are hyperlinked images,
so they are _not_ a different concept at all.

> Federico, you changed 5 occurrences, 243 to go... Don't forget the help.
> 
> timar at timar-x230:~/libreoffice-master/translations/source/hu> git grep -i
> hyperlink | grep msgid | wc -l
> 248

Thats not a valid comparison: Localizations might have their own interpretation
of vocabulary (e.g. german uses the Pseudo-Anglicism "Handy" for a mobile
phone, while there is no such thing in the source language.

> In the end 100+ people will spend hours because of this (translators,
> documentation writers).

This is why we are a project: to improve LibreOffice.

As such:
1/ This is about the default en-US l10n only, vocabulary of other locales is a
decision to be left to the local maintainers. I assume this is fixed with this?
2/ Other locals are out-of-scope for this issue.
3/ As a follow-up using a more specific wording than "link" for links that are
not hyperlinks (like the linked text frames) might be considered.

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