[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Fix portuguese in all copies of utf-8.ly (issue 571640044 by address
From: |
lemzwerg |
Subject: |
Re: Fix portuguese in all copies of utf-8.ly (issue 571640044 by address@hidden) |
Date: |
Tue, 18 Feb 2020 01:29:02 -0800 |
> à vo -- cê uma can -- ção legal
>
> I don't know how to change it, so that
> http://lsr.di.unimi.it/LSR/Snippet?id=600
> shows the same as in Han-Wen's patch here.
This seems to be a bug on LSR webpage: What you see is double-encoded
UTF-8 (see
https://stackoverflow.com/questions/11436594/how-to-fix-double-encoded-utf8-characters-in-an-utf-8-table
for a similar mysql issue) – UTF-8 encoded characters get interpreted as
Latin-1, which in turn get re-interpreted as UTF-8.
Note that in the LSR database itself the problem doesn't happen.
Please contact Sebastiano so that he can comment and probably implement
a fix.
https://codereview.appspot.com/571640044/
- Fix portuguese in all copies of utf-8.ly (issue 571640044 by address@hidden), lemzwerg, 2020/02/15
- Re: Fix portuguese in all copies of utf-8.ly (issue 571640044 by address@hidden), thomasmorley65, 2020/02/15
- Re: Fix portuguese in all copies of utf-8.ly (issue 571640044 by address@hidden), thomasmorley65, 2020/02/17
- Re: Fix portuguese in all copies of utf-8.ly (issue 571640044 by address@hidden), lemzwerg, 2020/02/18
- Re: Fix portuguese in all copies of utf-8.ly (issue 571640044 by address@hidden), thomasmorley65, 2020/02/18
- Re: Fix portuguese in all copies of utf-8.ly (issue 571640044 by address@hidden),
lemzwerg <=
- Re: Fix portuguese in all copies of utf-8.ly (issue 571640044 by address@hidden), hanwenn, 2020/02/19