"I'm going to write out a log entry every time I see this sort of packet, and put it at WARNING level. This will help me solve a serious problem!"
    -- Anonymous Developer

1,000 packets/second later on N devices…

Since a new version of the free-as-in-fork LibreOffice package was just released, I thought I’d take a look and see if it’s gotten any easier to import formatted text.

The answer: “kinda”.

Good: It imports simple HTML and CSS.

Bad: …into a special “HTML” document type that must be exported to disk in ODT format, and then reopened. Otherwise, all formatting not available for web use will either disappear from all menus and dialog boxes, silently fail, or be deleted when you save (generally the result of pasting from another document).

[note that the Mac version crashed half a dozen times as I was exploring these behaviors, but it usually managed to open the documents on the second try]

Sadly, furigana are not considered compatible with HTML, so they’re stripped on import, making it rather a moot point that you can’t edit them in HTML mode. The only way to import text marked up with furigana is to generate a real XML-formatted, Zip-archived ODT file.

I am not as impressed with your clever prose as you are:

"Fukagawa is a neighborhood in Tokyo’s Koto ward, just 3km east of the Imperial Palace and Tokyo Station, and across the Sumida River. Like most wards in the east of the city, it is not a place where wealth is overly evident, but neither is want. While by no means a sleepy hollow, it has none of the pent-up-ness of the central business districts, or the brittle proud-of-itself chic of the city’s shopping meccas only a few stops west."

One of these sentences contains information. The rest say a lot about the writer, but nothing at all about Tokyo.

Just spent a merry, no wait, hellish few hours fighting to get a LaTeX distribution up and running for the sole purpose of running a single script that uses it to convert marked-up Japanese text to PDF in convenient ebook sizes.

I failed. Or, more precisely, I got all the way to a DVI file that could be displayed quite nicely on screen, with all the kanji and furigana intact, but then the PDF converter that was part of the same TeX package that had generated it started barfing all over my screen, and I refused to spend more time on the project. I simply have no desire to navigate the layers and layers and layers of crap that TeX has acquired in its hacked-together support for modern fonts and encodings.

Honestly, if I want to generate cleanly-formatted Japanese text as a PDF, with furigana and vertical layout and custom page sizes, it takes 10,000 times less effort to spit out bog-standard HTML+CSS and feed it to Microsoft Word.

[Note to the MS-allergic: performing the equivalent import into OpenOffice is possible, but not reasonable. Getting basic unstyled plaintext+furigana wasn’t too bad, but anything more complicated would be an exercise in tedious XML debugging.]

[Update: gave it another go, and eventually discovered that running dvipdfmx with KPATHSEA_DEBUG=-1 in the environment returned a completely different search path than the kpsewhich tool used. Copying share/texmf/web2c/texmf.cnf.ptex to etc/texmf/texmf.cnf made all the problems go away. At least until the next time I upgrade something in MacPorts that recursively depends on something that obsoletes a recursive dependency of pTeX and hoses half my tools.

And, no, I can’t use the self-contained and centrally-managed TeX Live distribution (or the matching GUI-enabled MacTeX). That was the first hour I wasted. Its version of pTeX is apparently incompatible with one of the style files I needed.]

When evaluating submissions to the Mac App store, you really should check to see if a limited-functionality app also happens to include a limited-creativity ripoff of one of your own icons. Like Screen Grabber, which made a few light edits to your Grab app icon.

Note that this was not one of those “let’s stuff the store with crap on opening day” apps. No, this one was approved two days ago.

Just a quick FYI, but you might want to have a chat with the folks who supply your Kindle wireless coverage map.

First, yet another update to the collage-making Perl script. I added a number of tweaks so that I could reduce blank spots and overlap. If my interest holds up, I may add code to search for the largest empty areas more intelligently, but the current version works pretty well, and only took 13 seconds to generate a 1024x4096 collage of 481 naughty-book covers at 36% of their original size.

Warning! Clicking on the thumbnail loads a 1 megabyte JPEG that is unlikely to be work-safe:

Yes, I’m up to 481 covers. Some of them are second-rate, and some of the titles reflect subject matter less innocent than the cover images, but there’s a lot of terrific cheesecake in there. I’m probably going to track down the names of several of the artists so I can look for collections of their work.

One thing I didn’t do as I was idly gathering covers was keep track of the original pages on Amazon, so if I want to do something with the book titles, I have to type them back in by hand. This isn’t too bad, since I can sketch most unfamiliar kanji on my laptop’s trackpad, and find most of the remaining oddballs with Ben Bullock’s Multi-radical search tool, but it turns out that for many of the books, the really spicy bits are in the sub-titles, which are often too small to read. In some cases, the large title is just the series name.

Still, I’ve done enough to confidently state that at least one of the following words appears on the cover of almost every naughty novel in Japan. Sometimes three at once, with three at once. Cut out and save this handy guide!

more...

While reading the comments over at Chizumatic (yes, dream-eating is the correct way to interpret yumekui, given that hitokui = cannibalism), I belatedly realized another bit of kanji wordplay in my expanding collection of naughty-novel cover art: 蜜楽.

I didn’t think much of it the first time I saw it, on the cover of Welcome to Honeyfun Island, but then I saw it again on Honeyfun-hunting and made a mental note to see if it was a common genre term. When I saw the comments on Yumekui, it snapped into place.

The word on the covers is mitsuraku. Compare these two characters:

蜜 密

The first one means honey, the second one means secret, and they’re both read as mitsu. There’s also a word itsuraku that means pleasure. So, adding an initial consonant sound and substituting a suggestive kanji converts simple “pleasure” into “secret honey pleasure”, which certainly sounds like something you’d look for in a naughty novel.

I found a less wholesome example on another cover, 蠢（うごめく）, whose main title is a rarely-used character for the verb “to squirm; to crawl like a worm”. The subtitle is 姦獄美姉妹, which is read as kangoku bi-shimai, “prison beautiful sisters”. Or, rather, the first word would mean prison if it were written 監獄, but the first kanji has been replaced with another one that is also read as kan, but has various meanings including “wicked” and “boisterous”. And, unfortunately, “rape”, which is probably the intended meaning in this context. (supported by the people-also-bought list including a number of books with prison bars and tied-up women)

Note to self: do not browse for cover art in a session where you have confirmed to Amazon Japan that you’re over 18. This opens up the search results to include material that’s been flagged adults-only in their database, such as bondage, rape, and lolicon. These really don’t fit my cheesecake-pin-up theme, and the cover art on the lolicon novels is seriously creepy.