https://codereview.appspot.com/571640044/diff/571650043/Documentation/snippets/utf-8.ly File Documentation/snippets/utf-8.ly (right): https://codereview.appspot.com/571640044/diff/571650043/Documentation/snippets/utf-8.ly#newcode1 Documentation/snippets/utf-8.ly:1: % DO NOT EDIT this file manually; it is ...
5 years, 2 months ago
(2020-02-15 21:41:57 UTC)
#2
5 years, 2 months ago
(2020-02-17 22:55:34 UTC)
#4
On 2020/02/15 21:41:57, thomasmorley651 wrote:
>
https://codereview.appspot.com/571640044/diff/571650043/Documentation/snippet...
> File Documentation/snippets/utf-8.ly (right):
>
>
https://codereview.appspot.com/571640044/diff/571650043/Documentation/snippet...
> Documentation/snippets/utf-8.ly:1: % DO NOT EDIT this file manually; it is
> automatically
> Makes no sense to fix this snippet here.
> It is superseded by the snippet in Documentation/snippets/new.
> Furthermore next LSR-import would override it again.
> Thus the fix should be done in LSR.
>
> Alas, LSR seems down, atm...
LSR is up again.
Though, I'm puzzled how characters are displayed. I feel unable to fix it.
Werner, may I ask you to have a look?
> à vo -- cê uma can -- ção legal > > I don't know ...
5 years, 2 months ago
(2020-02-18 09:29:03 UTC)
#7
> à 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-c...
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.
Issue 571640044: Fix portuguese in all copies of utf-8.ly
(Closed)
Created 5 years, 2 months ago by hanwenn
Modified 5 years, 2 months ago
Reviewers: lemzwerg, thomasmorley651
Base URL:
Comments: 1