|
we are currently use version 3.4.g, we have installed new server where are 9 languages, we have an issue with JPN. JPN server comes up , but all the screen Names are showing up as ??? marks however the data in the data bse shows up in Japaneese languageA glance at the screenshots tells me all I need to know. Where characters should be are boxes. Incompatible, non-compliant font. They never modified the templates to use "Arial Unicode MS". I sent him easy-to-follow instructions. It's nothing but search and replace in a few text files. We see your answer and making changes to all template file but see screenshot we are still have problem. We need solution because this is wrong with not seeing the texts.That's unpossible. There's only one thing that causes boxes to be displayed instead of characters: the wrong font. Either they don't have a font which can display the character (also unpossible since they're using a native Japanese OS) or they specified the wrong font. That's it. There are no other possibilities. If you see boxes instead of characters, you have one of these two simple font problems. Clearly search for 'Arial' and replace ALL with 'Arial Unicode MS' wasn't complicated enough for them and therefore couldn't possibly be the solution, and I'm betting they got clever. All I need is the font directory listing and templates. Nothing else unless they did something seriously fucknutted like changing the font substitution list in the registry. Still, they've already shown themselves to be thoroughly incapable of following simple instructions so it's time to put them to work and add eggs and milk. Along with what I actually needed I got server logs, screenshots, a registry export (just in case), a database extract... all in all about 600MB, of which I actually needed less than 14KB. And it was right there. { font-family: ‚l‚r ‚oƒSƒVƒbƒN, Arial Narrow,Helvetica,Sans-Serif; font-size: 8pt; } Mangled thanks to their editing it in fucking Notepad and saving it as an ANSI text file rather than Unicode. I recognised the mangled bit quickly: a Japanese font. Still, I had to unmangle it before I could properly chew them out.
Step 1: Open the file with a hex editor:
Step 2: Remove familiar and unnecessary crap which served to delimit the mangled garbage:
Step 3: String the useful hex together:
Step 4: Guess which encoding they're using
Step 5: String bytes pairs together and hope your endianness is correct:
Hmm... there's a space in there. I'm thinking this will be "MS Mincho" or "MS Gothic", typed by some halfwit in half-width.
Step 5: Character look-up:
Then there's that "20", a space. Which fucktard out there decided computer font names should have spaces? Working through it all I ended up with "MS Pゴシック", the "Gothic" font I expected. And right behind it, "Arial Narrow". Why? Because, well... maybe because Japanese people have some weird halfwidth font fetish. I thought about the time I'd spent on this ticket so far and how much more time I was likely to have to waste in explaining to them what they needed to do, namely, use the right fucking font, stop adding wrong ones, and save text files in the correct code page. Dear Sparky-san,"For analysis" prevents questions. Two days later they sent what I'd asked for. I fixed the dozen or so files which specified fonts inside 10 minutes. And as I finish writing this I'm confronted with the fuckwitted subject of tomorrow's entry if I manage to get out of bed. ファクヰト everywhere. ルウトコズ:十七
|