search

google-code-export / glossword

Automatically exported from code.google.com/p/glossword
0 stars 0 forks source link

GW1.9.2 - Default language does not work #141

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Setting the default language in Manage > Translations has no effect on the
front end (I tried with Spanish)

I even installed the official front-end Spanish translation for the J1.5
installation, and made it the default language.

Suggestion: Perhaps GW should recognize which J1.5 language is "default"
and match it if it's available on GW

Original issue reported on code.google.com by el.guach...@gmail.com on 25 Mar 2010 at 1:32

Attachments:

GoogleCodeExporter commented 9 years ago 
It depends on browser settings. Set Spanish in browser.

Default language - it is language that will be selected when user's browser has 
a
language which is not listed in Glossword. Try with Hindi, for example.

Original comment by dmitry.s...@gmail.com on 25 Mar 2010 at 7:29

GoogleCodeExporter commented 9 years ago 
Excuse me Dmitry, but that makes not sense. In Joomla you do not depend on the
browser language (which is an external setting, unrelated to the website). You 
have a
way to make your entire website in Joomla in spanish, regardless of what 
browser,
location or operating system visitors use.  That is why you have default 
language in
Joomla, and once you set it, all dates, menus, and information notes are in 
spanish.

I believe this is a mistake.

Otherwise, I could create an entire website in Spanish, use the Joomla 
translation
for all the system messages, and then glossword would be in english?  How can I
ensure that all my visitors will visit from a spanish-language-browser.

I believe this is vital for a Joomla component. If this is not how it works, it
should, so I would like to request it as a feature.

Original comment by el.guach...@gmail.com on 25 Mar 2010 at 11:02

GoogleCodeExporter commented 9 years ago 
Let's see how it works:

First of all, preferred language is defined in browser`s settings.
For me it is Russian, for you it is Spanish.

Next, I'll open Glossword dictionary from browser and will see Russian 
interface (as
prefered), and you will see the same in Spanish. It is not depend on Joomla's
interface at all.
I strongly believe (I started to believe when I tried it 1st time) that any CMS 
should switch language automatically in the same way, like their popular 
internet
services do. 
However, I should notice that they provide a language selection if the current
selection mismatched. Personally, I haven’t met mismatched language selection.
Lasf.fm, YouTube - I see them in Russian by default.

When the user prefers language which is not presented in Glossword, for example,
Hindi, Glossword (and other mentioned services) could not select Hindi for 
interface
because Hindi does not exist, so they switch to English by default.

In Glossword, you may assign language what will be used by default, it could be 
not an English at all.

> I could create an entire website in Spanish, use the Joomla translation 
> for all the system messages, and then glossword would be in english?

It would be in Spanish 
1) when the user has Spanish in the preferences 
2) when no other languages are active, Spanish in only enabled language in 
Glossword

And finally, I could create additional option for Glossword which defines the
behavior for language selection: automatic (described above) and manual 
(described by
you).

Original comment by dmitry.s...@gmail.com on 26 Mar 2010 at 3:52

GoogleCodeExporter commented 9 years ago 
Hi Dmitry

I completely understand your reasoning, and the stand-along version of GW does 
behave 
like that and I think it's great. Unfortunately, the fact that GW1.9 behaves 
differently than that of the CMS where it resides does not seem very logical. 
It's 
already a problem when you install a component that does not have localization 
files, 
or is only available in english. GW is a lot more powerful than that and the 
fact that 
it does so well in localizations should be an advantage.

In a perfect world, I too believe that Joomla should be smart enough to 
recognize the 
locale of the browser and default to it, but until that happens, I think the 
components 
need to recognize the "umbrella" language of the platform, and then match it. 
This way, 
the creator of the site could accomplish a "seamless" website where all the 
components, 
modules and platform are speaking the same language.

By the way, I tried what you suggested and it worked (disabled all other 
languages), 
which essentially "forced" spanish to GW.

I think that adding the extra option would be a good idea, but I would add the 
following options: 

Set language by:

[X] match Joomla front-end default
[ ] match browser settings
[ ] manual (selection will be default independent of Joomla's settings)

and, if you think that in the future you would like to integrate fully with 
multi-
lingual websites (powered by components like JoomFish for example):

[ ] synchronize with third party localization components.

But, of course, I am not a programmer, so I have no idea of the difficulty of 
this 
options.

Thank you for your response, and I hope this is helpful!

Original comment by el.guach...@gmail.com on 26 Mar 2010 at 4:48

GoogleCodeExporter commented 9 years ago 
BTW, you changed the type of this ticket to "Enhancement", but left it closed..

Original comment by el.guach...@gmail.com on 26 Mar 2010 at 4:50

GoogleCodeExporter commented 9 years ago 
Dimitri this is very important, your component should take the default language 
from
Joomla, not from the browser. You should reopen this issue and try to implement 
it.

thank you.

Original comment by congo...@gmail.com on 23 Apr 2010 at 7:49