- User Since
- Aug 19 2018, 12:11 AM (16 w, 6 d)
Wed, Dec 12
@kevans are you OK with the test case added to libc/regex instead and using sed? :)
Sat, Dec 8
Oops, I didn't mean to add Ed back to this review :-)
Reading through the discussion, I do agree with @ed -- we should have just one version in UTF-8, and convert to current encoding on the fly, though I do agree with @AMDmi3 as well -- making sure we use only the characters that can be converted to the related single-byte locale shouldn't be that hard, we don't need to use the fancy unicode chars in messages.
Sorry for the delay. I have spent quite a bit more time on this, including testing. Summary and the change updated accordingly.
Thu, Dec 6
Wed, Dec 5
Mon, Dec 3
Add the comment for msi_tupelo (and cleanup whitespace issues introduced by the patch).
Sun, Dec 2
Now with full context...
Thu, Nov 29
Wed, Nov 28
diff with full context
Mon, Nov 26
Upstream PR: https://github.com/lichray/nvi2/pull/61
Fri, Nov 23
drop unrelated changes
After providing the quick fix, I have started wondering how GNU grep (or libgnuregex, more precisely) does the matching without providing any locale specific data; the answer is pretty simple, not sure why I didn't think about it from the start -- fold the case of *both* sides of comparison, and compare both-upper and/or both-lower.
Please submit diffs with full context.
Thu, Nov 22
There's a reply and action upstream, the patch integrated there is more complete (removing all "bits" stuff from mansearch), will use that one.
Wed, Nov 21
Sat, Nov 17
Thu, Nov 15
Nov 14 2018
Baptiste, anything else you want to see done/answered for this to proceed?
Nov 13 2018
Nov 11 2018
Nov 9 2018
Nov 8 2018
I think this makes perfect sense. You might want to update editline(3) as well so it doesn't say it only knows about UTF-8 and C locales.
Nov 7 2018
cleanup done separately; rebase
Nov 6 2018
Nov 5 2018
Nov 4 2018
Just for the note: perl bits here are only the helper tools for someone updating the locale sources in share/, and aren't run during the build, so even if something is broken there (and I tried not to as I used them), it's only bad until there's a need to update the data again where they will be fixed anyway :)