Thanks for the new expression!

The English equivalent is "Get off [my|your] ass." Maybe "hips" is a euphemism, but "raising your hips" also seems more descriptive of how one stands from a kneeling posture. And if your legs have stiffened or cramped, in trying to rise, the body seems very heavy indeed.

Looks all right :)

I can see the Japanese (I'm looking at your site on Mac OS X (Jaguar), running the Safari browser.)

Yep, can see the characters (looks good!)

And I agree with M - raising heavy hips means "Get off your bum" to me!

i see all the japanese well.

nice to know that expression, i should get off my omoi koshi myself!

I knew the expression "I can get my ass up and go to lunch!" from my freimd's mail, I thought What a direct expression. AND SOMETIMES I say "Haa, OMOI OSHIRI". Sorry my comments may confuse everyboday.

Hi Kiyo! Please can you pass on this information about entering Japanese script on web pages? I am interested to know the details - so far I haven't used any Japanese on my web site. Thanks!

It's just two minor tweaks to the Movable Type config file (mt.cfg). First, set the PublishCharset line to a character set that can handle Japanese. I'd recommend Unicode (UTF-8), but if you're stuck with a large user base on outmoded operating systems, that will cause difficulties and you might want to go for one of the more established charsets (EUC-JP or Shift_JIS). Here's what the line looks like:

#
PublishCharset UTF-8
#

Then, the NoHTMLEntities line needs to be set to 1. This line is commented out of the default file. To un-comment it, remove the hash character in front, like this:

#
NoHTMLEntities 1
#

That's it. Upload the file in ASCII mode.

Thanks again, Rudolf. It worked like a charm. So, Darren, that's it. I guess you have collected a lot of Japanese expressions. ;)

And thanks, folks, for the feedback.

Oh, thanks a lot for the info. I might give it a try! Out of interest what impacts/effects does noHTMLEntities 1 produce?

Html entities are little bits of code that can be used on web pages to represent characters that aren't part of the basic ASCII chart. If you create web pages in languages that use the alphabet (like English) but in addition have "special" characters (like French, Spanish, Italian, German etc.) it's generally a good idea to use html entities for these characters. Here's a list of these things:

http://www.evolt.org/article/ala/17/21234/

Across browsers, the "numeric" entitites are generally the safer bet.

This is what the mt.cfg file says about the NoHTMLEntities line:

# By default Movable Type uses the Perl module HTML::Entities to encode
# characters into HTML entities, provided that you have this Perl module.
# However, in some circumstances, even if you have this module, you may
# not wish to use it for encoding; for example, if you are using a language
# that uses a different character encoding (Polish, Russian, etc). In that
# case, you should set the value of NoHTMLEntities to 1.

This means that if you allow the Perl module to convert "special" characters, it will try to convert non-alphabetic characers into ISO 8859-1 character entities and create a mess in the process.

I'm not sure that's the whole explanation though, since when I was first struggling with this issue I found that some Japanese posts got stuck somewhere in the program and never made it through to an html page.

But at least I haven't noticed any negative effects. At first I feared the NoHTMLEntities line would disable html entities altogether, so you couldn't use them for "typographically correct" quotation marks and apostrophes any more, but this fear was unfounded.