A reply (for those who have not already muted me) (short answer, I’m leaving for now.)
Thank you Daniel, yes correct, my suggestion was meant to be helpful and not flippant. I had no thoughts unfortunately that it would cause such a problem for anyone. I am probably not allowed to apologize anymore as it will annoy someone else so I won’t.
As an explanation, I have been involved in education, teaching, writing about, tech support (related to computers, tablets, software) for over 45 years.
On Helpdesk we usually have less than three sentences for each query coming in. We have to make a best guess about how to phrase and answer the question in a way that is tailored to who they could be, their background, just going by their wording, as opposed to giving them a link to the page in the manual or long lists of possible step-by-steps depending on what else they did not say. This is best (up to now) handled by a human not AI, which becomes obvious to them if they progress with further questions to us and much appreciated.
What we often find out during a few more email exchanges if they occur is they can be between 8 years old or 80 or over. Some are developers (of apps) and give us the code to fix the UI so it works better for them, others are using a tablet for the first time, either coming from a computer or not at all, (going into retirement or perhaps in to hospital.) Some are completely blind (we find this out if we send them a specific screenshot with an arrow to clarify) and not a text answer. Some do not know what a “reboot” is or what “swipe” means, or “Back” top left (as opposed to a left arrow). Some cannot get a tap to work (in the end we/they find out they have long fingernails and need to tap slightly differently or not poke at it, or for classical guitarists (long fingernails on one hand), they find using their other hand works better (this is what they report back to us!)
Specifically, our video demonstrations are either incomprehensible even though they know the language (we suggest the CC captions which help a lot for different regional accents), or it is not in their language (we suggest the CC and auto-translate) which they do not know about, or because of this now it is too fast to read (we suggest speed controls) or if there are key commands for these settings because they cannot use a mouse very easily (motor problems, Parkinson’s etc.) These kinds of replies are appreciated and often we are told no one else told them how.
It is difficult to turn all this experience off while here at the forum, my initial reply I gave was coming from where I am without any thought.
What I obviously did not factor in, was that what I had suggested was obvious to all and it simply did not require a workaround suggestion—that Dorico users here are probably more “normal” users (not blind, they are all computer savvy and competent in technology). This is obvious to me now.
While many queries here at the forum are obvious in the way to have answered, I can see there is a large gray area where I might get tripped up again and it offends someone. This is the first and only forum I have anything much to do with, so am unsure of etiquette, hence my second reply. I started posting because of the Finale thing last year to help the Dorico team and others here, but there are enough responding with help now.
There are a number of heated exchanges of annoyances going on in a few other threads, I do not want to be part of yet another one, so I exit.
For now, I will hope to use the forum for any Dorico problems I have and stay largely silent for now otherwise, perhaps reviewing it in a year or whenever.