On 2020/03/08 12:16:55, thomasmorley651 wrote: > On 2020/03/08 12:11:43, Be-3 wrote: > > On 2020/03/08 11:38:29, dak wrote: > > > We don't really document bug fixes as a rule in changes.tely. It's pretty > > long > > > already... > > > > Yes, certainly. > > But I think this is a special case. Speaking for myself, I'm taking it for > > granted that UTF-8 filenames just can't be handled by the Windows version of > > LilyPond and so I'm not using them, thus never having a chance to discover > that > > all of a sudden, the problem has vanished. > > > > To me, this feels rather like an enhancement/new feature than a bugfix, as in > > "LilyPond for Windows can handle UTF-8 filenames now". > > Although never been a windows-user, I second Torsten in this case. > > > I was just suggesting.
Fine with me. I am a bit afraid that this kind of change is a bit fragile and/or dependent on build environments, and once we promise this in Changes, we may be held to that promise, and personally I am not involved with Windows to any degree where I could contribute to keeping that promise. And I am a defensive file namer myself from times predating not just UTF-8 but also Latin-1. But that is more an explanation about why I am thinking up excuses about this not being put in Changes rather than an explanation about why this should not be in Changes. So basically, after reconsideration I think you are right: that would make a good point for Changes. https://codereview.appspot.com/551580044/
