<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 10:37 PM, Peter Zaal <<a href="mailto:peter.zaal@gmail.com" class="">peter.zaal@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-US" class="">Regarding the diacritic characters, I noticed that when you use the literal diacritics in the translated text, this does not show correctly on the website.<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-US" class="">E.g. in the translated text ‘Bühlmann’ shows as ‘Bühlmann’ on the website, or ‘geïntegreerd’ in Transifex shows as ‘geïntegreerd’ on the website.<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-US" class="">Using encoded text in Transifex shows correctly on the website (although not encoded there), e.g. ‘één’ shows as ‘één’. ‘&’ shows as ‘&’.<o:p class=""></o:p></span></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-US" class="">So I guess this means we should use html encoding for the ‘special’ characters.<o:p class=""></o:p></span></div></div></div></div></blockquote><br class=""></div><div>I don't think that is the case. There is still something "off" here. But I'm not sure where in the (way too many step) pipeline it is going wrong.</div><div>But no, we should definitely use UTF-8 correct text in Transifex. And I need to figure out how to do the other steps without mangling the encoding.</div><div><br class=""></div><div>/D</div><br class=""></body></html>