Halfagain IM Forums
May 22, 2012, 21:20 *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Due to increasing spam we are forced to make this forum "Read Only". If you have an issue, most likely was discussed here. Use the Search function and try to find related discussions. If you can't find any helpful information, just email support at halfagain dot com"
 
   Home   Help Login Register  
Pages: [1]
  Print  
Author Topic: Support for non-English characters and localized Google-searches  (Read 686 times)
0 Members and 1 Guest are viewing this topic.
mapdaddy
Newbie
*

Karma: 10
Offline Offline

Posts: 12


« on: October 08, 2007, 09:21 »

I'm a Norwegian Content Solution 2 user, and in general I'm impressed with the product.

However, I'm struggling a little bit with one minor and one major issue:

1) The minor issue first: When scraping from Google, I get American search results. It would have been great to be able to localize the search result to for instance Norway, Sweden, Denmark or whatever country you're working from.

2) ... so, to the major issue, which causes me some grief: Content Solution 2 doesn't seem to support national characters like, ñ, ø, å, æ, ü, etc. This error makes the software virtually useless for use with another language than English. Is there a workaround here?
Logged
mapdaddy
Newbie
*

Karma: 10
Offline Offline

Posts: 12


« Reply #1 on: October 10, 2007, 08:58 »

Quote from: mapdaddy
[...]2) ... so, to the major issue, which causes me some grief: Content Solution 2 doesn't seem to support national characters like, ñ, ø, å, æ, ü, etc. This error makes the software virtually useless for use with another language than English. Is there a workaround here?
I have to reply to my own post here, since I've managed to find a workaround:

The solution is to enter the unicode instead of the character itself in Content Solution. This actually work!

One example: Don't enter "México", enter "M & # 2 3 3 ; x i c o" (without the spaces) in Content Solution's editor. This will output "México" in the RSS feed. The same goes for the variables. Avoid unicode in the variable names -- there is no need for that.

To replace ordinary characters with unicode, you need a conversion table:
http://plato.stanford.edu/symbols/entities.html
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.8 | SMF © 2006-2008, Simple Machines LLC Valid XHTML 1.0! Valid CSS!