[...] > > No, I said something completely different, you didn't read anything I > > wrote, did you? :) > > I did read it, but I mostly saw a lot of frustration in an area that I > don't have a lot of familiarity with, and which is -- in the absence of > standardization -- a matter of preference. > > > Anyway, forget about the issue. I see you don't have time to think > > about it and would rather follow blindly a standard or upstream. > > If I don't have enough information about, or experience with, a subject > to make an informed decision, then I don't make one. > > If I am going to break with a standard, or with upstream, I need a damn > good reason. Frankly, you weren't offering one. You were just angry > and impatient. (You appear to still be the latter.)
I thought I was giving four good reasons :). The first one, about rendering us_intl unable to produce a quotedbl maybe even merited a serious bug by itself. You don't seem to question upstream modifications to config files, but seeing the CVS logs, I don't see them being too careful when commiting changes. You had the bad luck of picking up the file between the blunder and the correction :). See, I was angry and impatient because the changes to /etc/X11/xkb/* broke my keyboard configuration. They changed rules/xfree86 and I couldn't configure correctly the keyboard, until, after much struggle, I learned to use the keycodes/types/symbol system and bypassed the rules/layout/variant one. And then, when I finally managed to build a good configuration, saw that <dead_diaresis> <space> was broken too... :) You don't want to break with standards or upstream, but what about breaking with your users? Changes in configuration files, should, IMHO, be carefully thought and justified... I think you will have a lot of bug reports related to the keyboard as more people upgrade. [...] > > I suppose it will be more productive for me to report further bugs > > directly to upstream, and then wait some months for you to pick the > > patches, is that right? > > You can do whichever you like; if you can work productively with the > Debian package maintainers, make a good case for including a patch, and > that patch doesn't cause problems, you may find it gets applied. Ok, I'll try to be clear and cool when reporting further bugs :). Thanks for your explanatory response. Bye.