<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 16, 2018, at 1:15 PM, Dirk Hohndel <<a href="mailto:dirk@hohndel.org" class="">dirk@hohndel.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Thanks, I misunderstood what was supposed to be changed.<div class=""><br class=""></div><div class="">This was correctly transferred from Transifex to my intermediate format.</div><div class="">From there it went correctly into GitHub: <a href="https://github.com/Subsurface-divelog/Subsurface-website/blob/master/_pages/about.nl#L93" class="">https://github.com/Subsurface-divelog/Subsurface-website/blob/master/_pages/about.nl#L93</a></div><div class="">And the upload from there to WordPress showed no error. Yet it didn't get updated. That's even more frustrating as that makes it harder for me to know when to retry...</div><div class=""><br class=""></div><div class="">So I made a whitespace change and pushed it again.</div><div class="">This time I got a "could not update post in the database" error.</div><div class=""><br class=""></div><div class="">And digging through the logs it turns out that it is indeed the encoding of the "één" that's the problem. Wordpress rejects what I am sending to it. So now I need to figure out how to work around that...</div><div class=""><br class=""></div><div class="">THANKS for the eagle eyes and for making sure I catch this. That would have been rather embarrassing.</div></div></div></blockquote><br class=""></div><div>This is indeed very strange. Files from Transifex are supposed to arrive in UTF-8. Nothing in my processing should have changed things to ISO8859-1 - yet <a href="http://about.nl" class="">about.nl</a> is the one file that was incorrectly encoded.</div><div>Right now I have no explanation. Add this to the list of things that I'm worried about, I guess.</div><div><br class=""></div><div>Manually converted and re-uploaded, all good now. Please check the website if anything else got damaged - especially look at the non-ASCII letters in the text, please.</div><div><br class=""></div><div>/D</div><br class=""></body></html>