|
Thank you for answering my question.
I’m not even sure what I can productively say about someone interpreting being pro-accessibility as having a ‘huge chip’ on their shoulder.
There is inevitably a gulf between most developers and most end-users. It goes without saying that developers are free to do what they want, but even totally logical decisions may not seem to have any logic to the end-user or their workflow. Sometimes the effort of supporting what seems logical to the end-user is just too complicated or impossible, sometimes it’s possible, sometimes somewhere in between. Not necessarily a simple determination or easy to explain.
From your answer, I’m guessing that the clips.ini uses the same format as other configuration files, which could contain all the things you mention. Given that clips are text and epub files have very well-defined internal paths (which yes, people can change) I’m still not sure I get how those restrictions apply specifically to clips. Is it just simpler just to have one file format? I understand if you have better things to do than give me an example though.
Having an opinion or, as I said, a feeling about something is not making an accusation. I think you’re are 1) reading in, and 2) misunderstanding how change happens.
If no one ever said they felt excluded, then how would anything ever change? None of us are magically pure and free of the biases embedded in our cultures.
|