From 5fe8ae8f871ddb8fccd0908962ccc075e3b14458 Mon Sep 17 00:00:00 2001 From: Mowgli Date: Mon, 29 May 2023 22:42:13 +0000 Subject: [PATCH] Added a comment: Use locales for that porpose --- ...mment_2_323f1be80e2422e73ebd99b702a28e80._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/views_do_use_utf8_for_chars_that_does_not_need_to/comment_2_323f1be80e2422e73ebd99b702a28e80._comment diff --git a/doc/bugs/views_do_use_utf8_for_chars_that_does_not_need_to/comment_2_323f1be80e2422e73ebd99b702a28e80._comment b/doc/bugs/views_do_use_utf8_for_chars_that_does_not_need_to/comment_2_323f1be80e2422e73ebd99b702a28e80._comment new file mode 100644 index 0000000000..345414088e --- /dev/null +++ b/doc/bugs/views_do_use_utf8_for_chars_that_does_not_need_to/comment_2_323f1be80e2422e73ebd99b702a28e80._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="Mowgli" + avatar="http://cdn.libravatar.org/avatar/17ab194dddf7b7da59ec039cbb3ac252" + subject="Use locales for that porpose" + date="2023-05-29T22:42:13Z" + content=""" +That is what locales are for. + +Why not use them just correctly? It is just wrong to use utf8 characters in non-utf8 environments. + +I think, the correct handling would be to stay with the user choice (locales and the raw text, a user used for the metadata) and mangle that chars just on such broken systems like windows. +"""]]