User-1748007105 posted
Ive had the site placed in my lap, so here are the facts about the site as I know them:
- Indexes and searches on English content ran just fine (although the english content has now be totally replaced with japanese)
- All content pages are encoded utf-8 and declared encoding='utf-8'
- Globalization request and response encodings are utf-8
- localeid is 1041
- trace says catalogue and scope are all ok
- the following query (for a known character) returns no results ($CONTENTS 世) AND (#filename *.html OR #filename *.aspx)
- running same query on w2k3+iis6 server's MMC Indexing Servers Query Form returns no results (well acutally it returns the same 19 junk results that youd get ran an empty search) - running ($CONTENTS eye) AND (#filename *.html OR #filename *.aspx) on the MMC form shows all occurances of files with the word 'eye' (plus the 19 junk files)
I am not a regular .NET programmer, and am really stumped on this one. I will be happy to detail any code or configuration details upon request.
I am not sure but I think you need Unicode encoding in Visual studio and do Japanese collation in Windows because what you are getting is called character conversion. Try the links below for VS unicode encoding and to download the localization tool
kit. I will also post the Japanese Windows collation code. I usually help with SQL Server not Windows so use these to get started. Hope this helps.
