Feature Requests item #662176, was opened at 2003-01-04 08:26
Message generated for change (Comment added) made by shawnkhall
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=432069&aid=662176&group_id=42081

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Gregg Tavares (greggman)
Assigned to: Nobody/Anonymous (nobody)
Summary: make it region aware

Initial Comment:
It would be cool, I think, if it searched in the correct 
langauge based on the user's version of Windows or IE 
setting.

I'm not sure which and maybe this is not the place to 
discuss it but what I mean is, if I'm running Japanese 
windows, odds are 99.99% that I'd prefer searches be in 
Japanese not English.  Of course the user can edit 
gg.xml to fix that but most users would not be able to 
figure that out.

Is this a good thing do you think?

The only question is should be based on the user's 
installation of Windows.  (ie, Japanese windows = 
Japanese based search) OR should it be based on his 
IE preferences.  Meaning if she's set IE to show 
Japanese pages first if there is a choice then should it 
search in Japanese.  This also seems like for most 
people it would be the desired behavior.  For example a 
Chinese speaking person using an English copy of 
Windows probably has his browser set to show Chinese 
pages first.

Unfortunately I'm not sure if google's language codes 
match Windows' language codes but they appear to and 
google defaults to English if you give it a nonsense code 
so to make this work, the simplest way is to do edit 
gg.xml so it look like this


 <script><![CDATA[
    function gg(q)
    //by MLL: warning : news service is still in beta 
stage, so URLs below may change
    {
      var args = parseArgs(q, "ifl, advanced, groups, 
directory, images, news, since, cache, related, link, 
froogle, glossary, keys, local, canada, deutschland, 
france, italia, uk, language");
      var mode, local, local_meta = "", local_tld = "com", 
msglang = "";

      // set the google interface language
      var syslang = navigator.systemLanguage;
      if (syslang.length > 2)
      {
        syslang=syslang.substring(0,2);
      }
      msglang = syslang;

If the codes don't match then a table lookup or switch 
statement would be needed

----------------------------------------------------------------------

>Comment By: Shawn K. Hall (shawnkhall)
Date: 2008-08-06 01:12

Message:
Logged In: YES 
user_id=219805
Originator: NO

Google now uses UTF-8, and DQSD supports most UTF-8 characters.

While it's not yet perfect, I consider this feature supported, and any
instances you can find that do not work should be submitted as bugs (with
whatever information you can find to support it).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=432069&aid=662176&group_id=42081

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Archive: https://lists.sourceforge.net/lists/listinfo/dqsd-devel

Reply via email to