Bug 489296 - Improve out-of-box experience for non-english locales
Summary: Improve out-of-box experience for non-english locales
Status: NEW
Alias: None
Product: EPP
Classification: Technology
Component: Releng (show other bugs)
Version: unspecified   Edit
Hardware: Other other
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-09 10:29 EST by Antônio Diego CLA
Modified: 2020-06-03 07:46 EDT (History)
9 users (show)

See Also:


Attachments
"Eclipse in Your Language" on Welcome (94.94 KB, image/png)
2016-03-16 16:46 EDT, Wayne Beaton CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Antônio Diego CLA 2016-03-09 10:29:40 EST
Eu sugiro um forma de mudar de idioma que já viesse integrada no programa, ao invés de ter que baixar dados do projeto Babel.


-- Configuration Details --
Product: Eclipse 4.5.1.20150917-1200 (org.eclipse.epp.package.java.product)
Installed Features:
 org.eclipse.platform 4.5.1.v20150904-0015
Comment 1 Brian de Alwis CLA 2016-03-15 23:44:46 EDT
The out-of-the-box experience for developers who do not speak english is difficult: they may not even be able to discover the Babel project.

Moving to EPP as this issue is beyond the Platform.
Comment 2 Gunnar Wagenknecht CLA 2016-03-16 06:54:22 EDT
Brian, I disagree. A language switcher sounds like a fundamental feature a platform should provide. :)

Anyway, anyone with some options what we could do? Is this a documentation issue, i.e. do we need additional information on the downloads page how to retrieve/install language packs?
Comment 3 Markus Knauer CLA 2016-03-16 07:29:54 EDT
Would it be an option to provide some information/description, or even some kind of automation/guidance, on the new Welcome page? And who could do the work?

Would it help to add a Babel p2 repository URL to the packages?

How would we mitigate the problem that (A) the Babel project is independent from the Simultaneous Release and delivers its language packs at a later time, and (B) the quality of the translations varies extremely from project to project.
Comment 4 Brian de Alwis CLA 2016-03-16 07:54:25 EDT
I wonder if this might be better handled by the Eclipse Installer. It could host a small number of translations for its own UI and prompt the user to install the Babel packs.

Or we could bundle the Babel packs with the standard packages? How big are they?

(This ignores the website side.)
Comment 5 Wayne Beaton CLA 2016-03-16 13:35:54 EDT
I tinkered with this a bit a few months ago.

I created a view that forces itself to the top if there is something interesting to report or suggest. One of the "something interesting" was noticing that the language pack for the current locale was not installed. I had something working for German, but then got hung up in the process of generalizing the process of querying Babel.

I tinkered a bit with creating a welcome screen item for the language as well.

The very experimental code is here:

https://github.com/waynebeaton/WorkbenchWizard

In the process, I created an experimental Marketplace item for the German language pack:

http://marketplace.eclipse.org/content/eclipse-ide-language-pack-deutsche

This doesn't need to be in Platform. It may be a good fit in Babel.
Comment 6 Gunnar Wagenknecht CLA 2016-03-16 15:36:49 EDT
What about bringing it to the welcome page? A single click could bring up a dialog to select and install a language pack.
Comment 7 Brian de Alwis CLA 2016-03-16 16:25:05 EDT
That's definitely an option.  But getting to the point that they have the Welcome page can be problem.
Comment 8 Wayne Beaton CLA 2016-03-16 16:46:18 EDT
Created attachment 260366 [details]
"Eclipse in Your Language" on Welcome

I played with the idea of putting a link on the welcome page. This was before the improvements that Brian has made, so I recall having some challenges making it dynamic.

Obviously, it should only appear if the Locale setting is mismatched with the languages currently installed and the text should probably be in the target language.

The implementation actually works; it invokes the p2 installer against the Babel repository.

There are some open challenges, but I think the concept works. At least if you let the user get as far as the welcome screen before trying to be helpful.

I wonder how hard it would be to create an Oomph task that detects the language setting mismatch and adds the language pack installation.
Comment 9 Dani Megert CLA 2016-03-17 03:22:23 EDT
(In reply to Wayne Beaton from comment #8)
> I wonder how hard it would be to create an Oomph task that detects the
> language setting mismatch and adds the language pack installation.

Better would be to ask the user (with the OS language being the pre-selected choice).
Comment 10 Wayne Beaton CLA 2016-03-17 10:15:11 EDT
(In reply to Dani Megert from comment #9)
> (In reply to Wayne Beaton from comment #8)
> > I wonder how hard it would be to create an Oomph task that detects the
> > language setting mismatch and adds the language pack installation.
> 
> Better would be to ask the user (with the OS language being the pre-selected
> choice).

I wonder if we can do both.
Comment 11 Antônio Diego CLA 2016-04-09 18:10:17 EDT
Good Luck.
Comment 12 Alexander Kurtakov CLA 2020-06-03 07:46:26 EDT
Moving to releng as it's generic issue not specific to the java package.