

Might there be efforts to address some of the issues surrounding the Hepburn romanization when it comes information loss especially when there’s a kana → romanization → kana roundtrip?
For example:
- ジ ⇒ ji
- ヂ ⇒ ji
- ji ⇒ ジ (?)
Just an ordinary myopic internet enjoyer.
Can also be found at lemm.ee (until 2025 June 30), lemmy.dbzer0, lemmy.world, and piefed.social.
Formerly found at Kbin.social.
Might there be efforts to address some of the issues surrounding the Hepburn romanization when it comes information loss especially when there’s a kana → romanization → kana roundtrip?
For example:
Huh, that’s not a browser, but I’ll take a look at it nonetheless. I am currently using Alexandrite as a browser frontend though. But thanks!
(In terms of this survey, IDK where browser frontends should be placed, I am not sure if it should be here or its own top-level category)
Floorp
I am confused about the inclusion of Linux as an OS in this survey. Does a Lemmy package exist for desktop Linux? Or is the Linux option for Linux phones?
I try to reach from different directions:
For the regions I missed, I have a soapy mesh/loofah thing held by some kind of rope on both ends and with both hands, I use it to reach the unreachable areas:
\
)/
)—
)I suppose that should be enough, but I only do that once a week. For the rest of the week, I just reach as far as I can and let the soapy water do what it can.
Thanks for the information.
I am not so much concerned as the usability of the Hepburn romanization as it’s survived the test of time, but if I am remembering it correctly, Kunrei-shiki was chosen because of this one-to-one lossless transcription between the Japanese kana and the transcription. Hence, I was wondering if this is still a concern, and whether or not there are steps to address this if ever this is still a concern.