I'm not sure either how and why that happened. I'm afraid that I'm not able to fix it.

Curiously in few threads, Japanese text looks corrupted when seen from the board index, but are shown properly in the thread itself.

What a pity. I thought this would be a simple fix. Can you edit the text, maybe? I know what's suppose to be written there.
"Uploaded is a page from うつうつひでお日記." and the last sentence is 吾妻ひでお先生、本当にありがとうございました。

This info probably won't help but the Japanese text broke as soon as I posted there yesterday. I copied the last sentence from the OP, uploaded an img and posted. I noticed it had jumbled the Jp text but assumed it was my browser during reload or something like that and went to sleep. Unfortunately it's not the case.

Well, thank you for looking into it anyways.

>>6816
>Can you edit the text, maybe?
Unfortunately I cannot with my capabilities. One possibility is editing directly from the database, but it might be too invasive and I don't have access to it anyway.

>>6817
It's alright. Thanks for caring.

It's fixed! How did you do it?
Thank you!

>>6819
Simply by editing the database. I did say that I can't access it but guess, I was wrong. I also had an opportunity to test code someone wrote (>>/navi/2440).

There's plans to fix other garbled posts, but I'm not yet sure how I'm going to do it without going through every post by hand. Don't expect the fix coming anytime soon though.

>>6820
>but I'm not yet sure how I'm going to do it without going through every post by hand
You could use the ftfy python package in that thread you linked to go through and detect corrupted posts (pre-filter on text with non-ascii characters, and see if fixed text differs from original. There might be a few false positives but you could review those manually)

It's not just JP, it's anything non-ascii it seems. E.g. this post which used the accented a and emdash:

http://tohno-chan.com/an/res/34782.html#i34820

I don't know what caused this on the backend, whether it was a db migration or just some serving-side change. Hopefully it's the latter, in which case I think you just need to set content type to utf8 and let the browser take care of it? But then again new posts seem to work fine, so maybe it's the former. Idk hopefully one of the admins can chime in and we can come up with a solution

Found this amazing automated mojibake fixer: http://www.linestarve.com/tools/mojibake/

Which tells us this was the transformation:

>encode (string→bytes) as sloppy-windows-1252
>decode (bytes→string) as utf-8
>apply (string→string) fix_character_width


Looks like python's ftfy package can do this too, so you could just run it across the entire db.

>>6829
>fix_character_width
>Replace fullwidth Latin characters and halfwidth Katakana with their more standard widths.
I'd recommend against doing this. It would butcher any ｷﾀ━━━(ﾟ∀ﾟ)━━━!! posts and SJIS art and the like.

>>6815
>Curiously in few threads, Japanese text looks corrupted when seen from the board index, but are shown properly in the thread itself.
This year's annual /txt/ post >>/txt/276 made a few hours ago appears to have caused this to occur there too. The board index looked fine shortly before that post was made.

>>6829
I almost forgot about this. Thanks for reminding me.

It seemed simple to fix, but the problem might be more complicated than thought.
Namely, the encoding settings of MySQL may or may not be all fucked up. We don't exactly know what could happen when we import the fixed table back.

We're planning to do some testing in the near future.

It should be fixed now. Some threads need "refreshing" but I can assure it is fixed on the backbone.

>>6834
Yup, it seems to be fine now. Thanks for the fix, admin-sama.

Reusing this thread for bug report: I've noticed that sometimes posts will update the thread catalog but not the thread itself. As an example, at the time of writing >>/ot/39978 is visible in the thread catalog and the frontpage ticker, but when you go to the actual thread (http://tohno-chan.com/ot/res/31969.html#i39978) it's not there.

>>6852
This one is trickier to fix. I don't have any faintest idea what causes this in the first place. Considering Kusaba's old age, it could be anything.

>>6853
Happened again with >>/ot/40010

I assume that for some reason the thread isn't being regenerated, although I don't know what would cause that.

This bad styling on the homepage is bothering me. It's a simple fix, set background-repeat under .NewsMenu to repeat-x.

>>6862
Thanks for pointing this out. I've fixed the issue, and with the help of a mod who found some of the missing files, was able to fix some other themes with missing backgrounds.

Fixed themes:
-ttgl
-kino
-klk
-pink

>>6864
I don't know if it's supposed to be this way or not, but the girl from the pink background shows through posted pictures when clicked.

>>6865
I don't know if it's intentional, but the cause seems to be the !important on background-image of body.

While I"m reporting css things, can you do

.tablesub {
background-size: auto 200%;
}

.tabletop2 {
background-size: auto 200%;
}

to fix the issue in attached image? Note that for some reason the the image http://tohno-chan.com/images/themes/submenubgv2.png has a weird crease in the middle half, so we need to set the height as 200% in order for it to correctly work.

>>6870
Fixed, thanks.