Dan0042 (Daniel DeLorme) wrote in #note-3: > Indeed, but I believe "ＵＴＦ－八" would be a better alias here Fully agree. I was just too lazy to go figure out the full-width hyphen, sorry. duerst (Martin Dürst)
Thanks to @ko1 for this timely news. It looks like the current Japanese government is recently taking some steps that in some ways have felt long overdue. On December 22, 2025, they changed the Romanization used by the Government from 'K...duerst (Martin Dürst)
Here is another proposal: Why not count using administrative/fiscal years? The administrative/fiscal year (年度 ('nendo') in Japanese, as opposed to simply 年 for (calendar) year) starts on April 1st. As an example, 1993-02-24 to 1993-3-...duerst (Martin Dürst)
Using two or more overlapping Unicode properties may not be very frequent, but in most cases isn't a mistake. If a user writes `/[\p{Word}\p{S}]/`, that expression should just match all word characters and all symbol characters, because ...duerst (Martin Dürst)
nagachika (Tomoyuki Chikanaga) wrote in #note-1: > In my environment, removing `exts.mk` in build directory resolved the issue. This worked for me, too.duerst (Martin Dürst)
When I tried to compile Ruby with make up; make, I got the message in the Subject. This seems similar to bug #19481, but the various kinds of advice (`./config.status` or `./autogen.sh; ./configure; make`) given there didn't solve the p...duerst (Martin Dürst)
duerst (Martin Dürst)07:49 AM Ruby Bug #22010 (Open): Update to Unicode 18.0