Project

General

Profile

Task #3265

Localized extension contents is not shown. Only EN version is.

Added by Jean-Francois Nifenecker 6 months ago. Updated 1 day ago.

Status:
New
Priority:
High
Target version:
Team - Q1/2021
Start date:
Due date:
% Done:

0%


Description

Hello,

when an extension maintainer enters 2 versions of the description text, only the EN one is visible, even if the browser and OS are in the localized language. The consequence is that a non-EN native browsing the extensions can't read the description in his/her language.

Or did I miss something?

Best

History

#1

Updated by Heiko Tietze 6 months ago

  • Assignee set to Christian Lohmaier

Do you have an example? Would be good to solve it with rdm##3260

#3

Updated by Heiko Tietze 6 months ago

  • Priority changed from Normal to High

English https://extensions.libreoffice.org/en/extensions/show/875
French https://extensions.libreoffice.org/fr/extensions/show/875
Switching the language in the admin area shows the localized description while the pages fr and en both are in English.

(Can we keep the page title and do the data exchange somehow internally?)

#4

Updated by Jean-Francois Nifenecker 6 months ago

I'm afraid I didn't understand what you mean. Whichever LibreOffice web site I use, I get the EN version and so would FR users.

I didn't find an obvious mean to associate the FR description with the fr LibreOffice website on the extension administration page.

Did I miss something?

#5

Updated by Sophie Gautier 6 months ago

Just for information, if you add Français and a tag, you got the FR parts as in https://extensions.libreoffice.org/?q=Fran%C3%A7ais&action_doExtensionSearch=Search

#6

Updated by Jean-Francois Nifenecker 6 months ago

Now, I'm lost, Sophie.

#7

Updated by Heiko Tietze 6 months ago

Sophie Gautier wrote:

Just for information, if you add Français and a tag, you got the FR parts as in https://extensions.libreoffice.org/?q=Fran%C3%A7ais&action_doExtensionSearch=Search

But in this case you run a query with "Français". And I guess it's not the same as translation, which should also show the respective description if available.
@JFN: Your links share the page while in edit mode. See the /en/... vs /fr/... in my comment. But I might be wrong, Cloph knows best what should happen.

#8

Updated by Christian Lohmaier 4 months ago

  • Target version set to Q3/2020
#9

Updated by Jean-Francois Nifenecker 2 months ago

Heiko Tietze wrote:

Sophie Gautier wrote:

Just for information, if you add Français and a tag, you got the FR parts as in https://extensions.libreoffice.org/?q=Fran%C3%A7ais&action_doExtensionSearch=Search

But in this case you run a query with "Français". And I guess it's not the same as translation, which should also show the respective description if available.
@JFN: Your links share the page while in edit mode. See the /en/... vs /fr/... in my comment. But I might be wrong, Cloph knows best what should happen.

Any progress here? I don't understand the way i18n works WRT extensions descriptions.

Thanks,

#10

Updated by Christian Lohmaier about 2 months ago

  • Target version changed from Q3/2020 to Q4/2020

We're still in a situation where most extensions are just having the imported content from the old site, and extensions with localized content are still the rare exception, that's why there's no global langauge selection dropdown, as that would then lead to "I selected <language>, but still everything is in English" comments.

So how localization works is by the URL prefix - if you use extensions.libreoffice.org/fr → you'd get French versions of the entries (if those exist, otherwise it will fallback to English, and this is what in effect happens for ~all entries - there just isn't localized entries for the vast majority of entries).
As for why your extensions don't appear in French: seems like there is no actual French translation?

for an example: https://extensions.libreoffice.org/pt-BR/extensions/show/1 → Portoguese (Brazil) translation of https://extensions.libreoffice.org/en/extensions/show/1

once there's a bigger number of translations we can enable browser auto-detection to have it redirect to the corresponding language URL, but at this point I don't think it makes much sense.

what I'll do as a short-time solution in the meantime is to add language links for individual extension entries if a translation is available.

#11

Updated by Jean-Francois Nifenecker about 1 month ago

Hi Christian,
strangely, in a given extension description, some contents appear in the localized language, while most of the text is EN.

This is visible here (to my FR Firefox and OS): see https://extensions.libreoffice.org/en/extensions/show/875
In the Release list, v0.7.0 comments appear in FR. The remainder is EN.

Best,

#12

Updated by Christian Lohmaier 1 day ago

  • Target version changed from Q4/2020 to Q1/2021

Also available in: Atom PDF