On Tue, 2003-11-25 at 22:28, James Harlow wrote: > On Tue, Nov 25, 2003 at 10:08:28PM +0800, Mike Gardiner wrote: > > I would like to add support for accessibility > > under a USE flag named either, > > > > o accessibility, or > > o a11y > > > > I prefer the former, but would like opinions on which word to choose > > before it gets added. > > accessibility - the only benefit of 'a11y' is that it takes less time > to type, and as it will only be set once (in make.conf), this is drowned > out by the fact that 'a11y' is pretty meaningless (as shown by the fact > you decided to spell it out in the top of the email).
Some of us like to set use variables more flexibly than once in make.conf (where 4 letters really is easier to type, saves my soon-to-be RSI). And my 'spelling out' was merely as an explanation. This notation is commonly used for i18n and m17n, but not everyone knows that. For most devs, they'll find accessibility support under a configure flag like '--enable-a11y'. Since I was discussing accessibility as an option, it seemed like a timely introduction. My arguments are simply 'accessibility' makes more sense, is more readable, whereas 'a11y' is shorter. 2 for the former at this stage. Regards, Mike -- [EMAIL PROTECTED] mailing list
