Bug 1663 - The plugin with the link for facebook/twiter... doesn't use the selected language but it use the value of general.useragent.locale
Summary: The plugin with the link for facebook/twiter... doesn't use the selected lang...
Status: RESOLVED WONTFIX
Alias: None
Product: Websites
Classification: Unclassified
Component: blog.mageia.org (show other bugs)
Version: trunk
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Damien Lallement
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-07 15:04 CEST by mammig linux
Modified: 2011-10-20 09:28 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description mammig linux 2011-06-07 15:04:52 CEST
Description of problem:

When you are on a french message of the blog ( for exemple this one : http://blog.mageia.org/fr/2011/06/01/notre-bebe-est-ne-mageia-1/ ), after the message and before the comments, you have some little pictures for facebook/twitter/... when you put your mouse over thoses pictures, you have a small message. With some browser ( like firefox or epiphany ) the text is in english and for others ( like iceweasel or opera ) is in french. 
We don't see the images with Konqueror.

The browser take the language of a configuration value ( general.useragent.locale ) instead of the language select in the language menu. If you go to a german message, you will keep thoses messages in French ( or English )

the version of the web browsers for my test : 
 Iceweasel/3.0.6 
 Opera/9.80 (X11; Linux i686; U; fr) Presto/2.7.62 Version/11.01 - revision 1190
 epiphany : Navigateur Web(browser) 2.22.3 - Propulsé(propulsed) par gecko-1.9
 Konqueror 3.5.9 using KDE 3.5.10
 Firefox 4.0.1



How reproducible:
For each message of the blog.



Steps to Reproduce:
go to the blog with different web browser
Comment 1 Romain d'Alverny 2011-06-07 17:27:31 CEST
There's an easy patch involving adding a language setting to the plugin and bypassing the getBrowserLocale() function if this new setting is set.

We could patch on our own, with all the consequences (not necessarily the cleanest solution, breaking future updates) but the plugin license does not really allows for this (All rights reserved). 

So we can only report the problem and hint at a solution to the code owner (http://www.shareaholic.com/ ).

CC: (none) => rdalverny

Damien Lallement 2011-06-10 10:22:13 CEST

CC: (none) => mageia
Assignee: mageia-webteam => mageia

Comment 2 Marja Van Waes 2011-10-20 09:28:17 CEST
(In reply to comment #1)

> We could patch on our own, with all the consequences (not necessarily the
> cleanest solution, breaking future updates) but the plugin license does not
> really allows for this (All rights reserved). 


Therefore closing

> 
> So we can only report the problem and hint at a solution to the code owner
> (http://www.shareaholic.com/ ).

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => WONTFIX


Note You need to log in before you can comment on or make changes to this bug.