| User | Post |
|
6:32 am
30 Jan 2008
|
Egria
Guest
| | | |
|
| |
|
|
Hello, I love your plugin.
However I recently discovered that Japanese signatures don’t work in Simple Forum. After doing some searches in google I think it has something to do with enctype="multipart/form-data" and something about ASCII characters and encoding… Since I’m no scripter I cannot tell whether my random search was in the right direction or not…
By the way my WordPress is currently using UTF-8
Egria,
January 30, 2008
|
|
|
11:28 am
30 Jan 2008
|
-Radio-
Moderator
| | Florida - USA | |
|
| posts 558 |
|
|
This is my attempt to verify…
|
|
|
11:33 am
30 Jan 2008
|
-Radio-
Moderator
| | Florida - USA | |
|
| posts 558 |
|
|
it seems you are correct, the kanji characters in my signature do not display…
My suspicion is it has something to do with how the signature is stored in wp_usermeta in the database. if the sql functions do not store the utf-16 high character calls for kanji, then there will be issues…
All in All this should be a simple issue and easily researched, however finding a fix may be a bit more complex.
|
|
|
11:37 am
30 Jan 2008
|
-Radio-
Moderator
| | Florida - USA | |
|
| posts 558 |
|
|
DOAH!
the feild is stored as raw html… if the kanji is urlencoded, it should display just fine…
Testing again…
|
|
|
|
|
I will await your instuction and enlightenment Radio…
|
|
|
12:26 pm
30 Jan 2008
|
-Radio-
Moderator
| | Florida - USA | |
|
| posts 558 |
|
|
Geek Speak
UTF-8
Unicode and ISO/IEC 10646 standards define transformation formats for
the universal character set. For the most part, the following UCS
transformation formats (UTFs) exist to transform UCS values into
sequences of bytes for handling by various byte-oriented protocols:
- UTF-8, the standard method for transforming UCS-4 or UCS-2 data
into a sequence of 8-bit bytes and ensuring interchange transparency
for characters from the ASCII character set (code positions 0 through
127).UTF-7, the standard interchange format for environments that strip the eighth bit from each byte.
- UTF-16, a transformation format that allows systems that can process
only 16-bit units (specified by UCS-2 encoding) to support the extended
character definition space that is included in UCS-4.
The current version of the DIGITAL UNIX operating system supports UTF-8
and UTF-16 but not UTF-1, UTF-7. UTF-8 can be used in codeset
conversion and in the universal.utf8 locale.
The question is: can we convert characters from kanji or katakana in the ISO-2022-JP code base, into useable UTF-8 or UTF-16(unix) for storage in that one feild in the wp_usermeta using a standard HTML encoding method?
I have always used direct encoding and utf-16 transmition over the internet when dealling with japanese, chinese or korean business associates… although I now also build web sites, I have to admit I have never built one in any of the asian languages that I am familiar with.
this string should display properly across platforms [ 私はそれらとマニア、私ちょうど住んでいるでない。] the same should also be true in the signature block.
when I look at the Code values to see if TinyMCE alters the codeing of the Kanji characters all I see are Kanji … when I save this post will be the true test…
|
|
|
12:31 pm
30 Jan 2008
|
-Radio-
Moderator
| | Florida - USA | |
|
| posts 558 |
|
|
I guess the difference now is, why is the encoding of the post data any different than the encoding of the signature block in the profile?
|
|
|
1:01 pm
30 Jan 2008
|
-Radio-
Moderator
| | Florida - USA | |
|
| posts 558 |
|
|
Andy,
I guess the simple solution is to follow the path that the post takes to be placed into the database; and verify that the signature data uses the same encoding/decoding as it’s placed into wp_usermeta. The signature is, after all, a string variable exactly like a post in it’s content.
I can imagine that a change in the way the signature block is saved would be a one line edit in your code, modifying the way the signature data is stored.
|
|
|
|
|
Radio: I tried using your example above (私はそれらとマニア、私ちょうど住んでいるでない。) in Version 3 and it seemed fine. Could you have a go at that as well and see if we have the same problem in 3 or not?
|
|
|
4:11 am
31 Jan 2008
|
Mr Papa
Moderator
| | Arizona, USA | |
|
| posts 1602 |
|
|
okay, gonna feel stupid I am sure, but what are you guys looking at? All I see is a bunch of ????.. Do I need to add some sort of language pack to my browser?
|
|
|
|
|
Ah. So you don’t see the string of Japanese characters in my post above yours that I pasted from radio’s above that? Gosh - I need to get a better understanding of this. I need a tutorial….
|
|
|
2:47 pm
31 Jan 2008
|
Mr Papa
Moderator
| | Arizona, USA | |
|
| posts 1602 |
|
|
nope, just a bunch of ????… and same for some sites Radio has listed… not that I would understand what I see, but sure there is something I have to do to my browers/pc to see those characters… just dont know what…
|
|
|
4:02 pm
31 Jan 2008
|
-Radio-
Moderator
| | Florida - USA | |
|
| posts 558 |
|
|
Andy,
The visualization on idividual PC’s is a font thing. MrPapa simply doesn’t have forigne language fonts.
It’s the difference between Mac and PC, Mac installs the foreign language fots by default.
Mr. Papa,
As far as the characters go, it’s an escaped string of high ascii characters, so yes, without the font to display those characters, it will appear as ???????, installing the Kanji and Katakana language packs for windows (linux) you will see the characters… if I had time I would explain what each one means, but the whole string translated is basically the same as my signature line, in Japanese kanji.
I’m not a tech head, I just hang out with them.
|
|
|
5:18 pm
31 Jan 2008
|
Mr Papa
Moderator
| | Arizona, USA | |
|
| posts 1602 |
|
|
This forum is currently locked - access is read only
Forums
