Niklas, No, I got that wrong. Sorry! It is not completely under ALv2, some key code is still LPGLv3.
Most of the AOO ia2 branch has ALv2 license applied, but some of the key IAccessibile2 code, e.g. the winaccessibility directory, bears LPGLv3 license (with an IBM copyright). Makes sense as the primary development is being handled by IBM Beijing. Adjusting the headers with ALv2 license seems to be done in bulk from time to time, but has not yet been applied to the core IAccessible2 elements of the branch. But at least it is all licensed as open source, and believe TDF ESC review feasibility of using its implementation of IAccessible2 can at least be started. Hopefully it will not mean waiting until the ia2 branch is merged into the AOO trunk (in preparation for an 4.1.0 release) for assignment of the obligitory ALv2 license. The IAccessible2 native bridge looks to require considerable changes to the entire UNO Accdessibility API, and that has potential to impact the OS X (NX) and Linux (ATK AT-SPI) bridges. Better sooner than later to resolve any adverse impact. Stuart -- View this message in context: http://nabble.documentfoundation.org/libreoffice-accessibility-Libreoffice-4-1-2-with-NVDA-Issues-with-using-pgup-and-pgdn-Keys-within-a-t-tp4076503p4077115.html Sent from the Accessibility mailing list archive at Nabble.com. -- To unsubscribe e-mail to: [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/accessibility/ All messages sent to this list will be publicly archived and cannot be deleted
