Hi Chris, I'm afraid I'm not that familiar with the technical details (of the saving process) to understand what do you mean.
This test causes corruption of the whole non-latin content, not just of the part which was edited, so I don't understand what do you mean by > treating all content as UTF-8 encoded and _nothing_ else and don't bother to check before decoding or encoding what encoding might already be present The stored (non-edited) content should probably be in UTF-8 as TW edited it with its own engines, shouldn't it? Best regards, Yakov. четверг, 14 марта 2013 г., 15:42:59 UTC+4 пользователь Chris Dent написал: > > On Wed, 13 Mar 2013, Yakov wrote: > > > Hi Jeremy, > > > > I think I have bad news. Today I edited couple of my TWs (fortunately > minor > > ones) via FF (with TiddlyFox) and they got badly corrupted. Those wikis > > contain text in cyrillics, and seem to be wrongly encoded. Auto-decoding > > via some online survice shows that the encoding is partially CP1163, > > partially ISO-8859-1 (and sometimes even that is not 100% correct). > > Fortunately, I've restored everything via decoding. > > > Not Jeremy, but I have a guess about what's going on. I would guess > that both TiddlyWiki and TiddlyFox are predisposed to treating all > content as UTF-8 encoded and _nothing_ else and don't bother to > check before decoding or encoding what encoding might already be > present. > > TiddlyWeb certainly takes this tactic. It minimizes complexity while > maximizing possible character representations. > -- > Chris Dent http://burningchrome.com/ > [...] > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
