Hi :)
I am wondering if anyone here has been able to have a go to find out
which way they prefer to try to help Niklas with his really good work
in this area.
Regards from
Tom :)
On 16 January 2015 at 18:06, Niklas Johansson sleeping.pil...@gmail.com wrote:
So the change is in the daily builds
So the change is in the daily builds of LibreOffice. I would like to
encourage you to try it out and see what you think. I will not push it
backwards towards LibreOffice 4.4 or earlier at this point, since I
think it might be good to discuss if this really is what we want.
Exposing the
Hi :)
Ok, so posting the bug report sounds like a great idea to me. I think just
go for it! There is a drop-down in the bug reporting system that lets you
mark it as a feature request. I think marking it that way would make
more sense to devs.
Stuart's posts might be useful, or might give you
Hi,
Who reports the bug? Does someone want to try? Should I do?
Regards,
Le 17/12/2014 13:05, Tom Davies a écrit :
Hi :)
Ok, so posting the bug report sounds like a great idea to me. I think just
go for it! There is a drop-down in the bug reporting system that lets you
mark it as a feature
Hi :)
Ok, so best left for a couple of months.
I have a feeling we might have managed to stay on topic, or at least get
back to the original problem! However that is so rare i can't quite
believe it!
@ Niklas, does that address the issue at all?
Regards from
Tom :)
On 15 December 2014 at
Hi Tom, all,
Le 14/12/2014 22:53, Tom Davies a écrit :
Hi :)
L10n lists are currently having a massive argument/discussion (discussion
is more accurate tbh) right now about the disruptive effect of minor
changes.
The problem is minor changes, like capital letters in menu entries, that
Hi :)
L10n lists are currently having a massive argument/discussion (discussion
is more accurate tbh) right now about the disruptive effect of minor
changes.
I'm not sure but i suspect that getting such a UI change within the next
couple of days might play out ok and catch the translators before
Hi
I still believe there is a bug or maybe we should call it an enhancement
request. It is true that accelerators are exposed properly through
IAccessible::get_accKeyboardShortcut, as they should. But reading
Microsoft notes [1] on the matter suggests that one should expose the
keyboard
Hi :)
Errr, excluding Stuart and others who work on Accessibility Issues and the
ones working on Base who are all total stars. Especially Stuart imo
Regards from
Tom :)
On 12 December 2014 at 14:07, Tom Davies tomc...@gmail.com wrote:
Hi :)
I suspect that calling it an Enhancement Request
Hi :)
If it's trivial and makes it more consistent with other apps then it sounds
like a really good option. Such a good option that it worries me why it
hasn't been done already. Maybe there is a good reason?
There have been a lot of positive changes in LibreOffice accessibility over
the last
Hi :)
Errr, in my questions i am not looking for certainties. I'm just trying to
get a rough idea of what might be.
I often find that things which initially seem quite easy have some lurking
bug-bear waiting to bite me. So i'm trying to guess at things that might
have been problems in the past,
Hi,
So if I understood all this thread:
1. Yes, LibreOffice presents to Iaccessible2, thus NVDA, the
accelerator checking on the box Reading objects shortcuts.
2. No, LibreOffice doesn't send to Iaccessible2 the shortcut of the
objects which have one, such as ctrl-o, ctrl-p, ctrl-x, etc.
Hi
I'd say that it is a LibreOffice bug. To sighted users the key combination
is displayed in the menus of LibreOffice but only the name is exposed to
screen readers etc. Could you please file a bug and send me a note with the
bug number so I can fill it with some more detailed information on the
13 matches
Mail list logo
