Re: Android design?
Hi, At 15:55 8-2-2012, Michael Meeks wrote: On Wed, 2012-02-08 at 13:43 +0100, Stefan Knorr (Astron) wrote: Hehe. Take a look at the amazing mock-up and ideas that Mirek has been working on for a while now: http://clickortap.wordpress.com/frivl/ They look nice :-) (No, none of this is perfectly specced out yet, but there's some pretty cool stuff there.) So - one thing that I (personally) rather dislike is this bold / italic / underline meme that still lurks heavily in new UI designs. IMHO these need to be firmly held underwater until they expire ;-) Thanks a lot for highlighting this Michael. I also wish this wicked witch were dead. Good mockups around making styles more visible and manageable, creating (and customizing) new styles [ which can indeed include the bold/italic/underline elements ;-] much appreciated for that. Last month there was a short thread on the LibreOffice-design list about how the UI of LibreOffice could be modified to encourage the correct use of styles (as opposed to ad-hoc styling). (The thread started at http://listarchives.libreoffice.org/global/design/msg03586.html.) We should continue thinking about this. Otherwise, some good ideas there. Do we have excitable people wanting to do UI work in Java - that we can plug together with the core in due course ? it'd be great to parallelise that work. Best regards, Christophe -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
likely cancellation of my presentations at FOSDEM
Hi, I have a presentation and a lightning talk scheduled at tomorrow's LibreOffice devroom. Unfortunately, it looks very unlikely that I will be able to make it to the conference. I hope someone reads this before the start of the devroom tomorrow. I apologise for the inconvenience. Christophe -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 www.docarch.be Twitter: @RabelaisA11y ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [PUSHED-3-4][PUSHED[3-5][REVIEW] 3-5, 3-5-0, 3-4 corrupted Indic characters and crash under Windows fdo#44208, fdo#45107
At 17:59 26-1-2012, Andras Timar wrote: Hi Caolan, 2012/1/26 Caolán McNamara http://lists.freedesktop.org/mailman/listinfo/libreofficecaolanm at redhat.com: We should in master generally shrink the rest of the tags down to the minimum correct lang-tag , e.g. hu-HU to hu, but zh-CN remains as zh-CN. And I'm confident that the zh-CN/zh-TW/pa-IN font entries currently should work for the windows UI fallback lists seeing as those langpacks are language_Territory. In fact hu-HU � and other European languages with country code � seem to be unnecessary there. They have not been working under Windows for ages (or ever), yet nobody complained. :) Some of them look identical to English node. I think we should list only those locales in VCL.xcu that require special fonts. Even empty nodes seem to be unnecessary, eg. node oor:name=af oor:op=replace /node We have zh-cn, zh-tw, zh-hk, and zh-sg, but zh-mo is missing, that is also a supported locale. I think we need to add it, LibreOffice tried to read zh-MO node when I selected Chinese (Macau) as default locale and/or default document language. Hong Kong was transferred to the PRC in 1997 and Macau in 1999. Cantonese (as spoken language) and Traditional Chinese characters are still the de facto standards in both places, as far as I know. Singapore apparently uses Singaporean Mandarin and switched to simplified Chinese characters in 1976. If there are differences between the zh-hk, zh-mo and zh-tw localisations, is this due to different translators or to differences between computing terminology in these three geographic areas? (I'm sure there are differences in vocabulary in these three areas, but I don't know if they affect computing terminology.) Best regards, Christophe -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] About Same expression on both sides of '||' in LockEntrySequence.cxx
At 17:15 16-1-2012, Caol�n McNamara wrote: On Sun, 2012-01-15 at 09:04 -0800, julien2412 wrote: First, I thought about just replacing the above line by this one : if ( !pCtx-hasType || !pCtx-hasScope ) I have no idea, but http://rfc-ref.org/RFC-TEXTS/2518/chapter23.html has... !ELEMENT lockentry (lockscope, locktype) !ELEMENT lockscope (exclusive | shared) !ELEMENT locktype (write) and this is LockEntrySequence_endelement_callback presumably to be called on processing the close tag, so I would expect that at the end of a lockentry tag we should have both a locktype and a lockscope case STATE_LOCKENTRY: - if ( !pCtx-hasType || !pCtx-hasType ) + if ( !pCtx-hasType || !pCtx-hasScope ) return 1; // abort on the basis that presumably if either the type or scope of the lock is missing then its busted assuming (a big ask) I read the dtd correctly. That's a correct reading. A lockentry element must contain both a lockscope element and a locktype element (in that sequence!). Best regards, Christophe (just commenting on the DTD part) C. -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] FOSDEM: LibreOffice dev-toom talks ...
Hi Michael, All, At 14:41 15-11-2011, Michael Meeks wrote: Hi guys, The FOSDEM organisers have kindly agreed to dedicate a developer room to LibreOffice development at the conference ( book now for 4-5 Feb 2012: http://fosdem.org/2012/ :-) So - that means we're eager to get -technical- talks (FOSDEM really is a true hackers conference), about LibreOffice its development, code structure, how to get involved with easy hacks, QA tooling, l10n improvements, etc. (...) http://wiki.documentfoundation.org/Marketing/Events/Fosdem2012 And the TSC will decide on the program closer to the time. (...) Is there another mailing list to find out what the status of the program is, i.e. which talks have been accepted, how long they can be, etc? I have not seen this on the TDF-discuss list. When I put all the submissions in a schedule with just a one-hour lunch break in between, I get a very packed day...: (I just used the order from the wiki; I assume there will be some reshuffling, but that is not up to me.) 09.00 - 09.45: Fridrich Strba - 'Import filters for LibreOffice: Join the journey' 09.45 - 10.30: Thorsten Behrens - 'Impress Hacking - The What The Where' 10.30 - 11.15: C�dric Bosdonnat - 'Hacking Writer: what to know to get started' 11.15 - 12.00: Miklos Vajna C�dric Bosdonnat - 'LPSP' 13.00 - 13.30: Italo Vignoli - 'LibreOffice Development Directions' 13.30 - 14.00: Italo Vignoli - 'Hacking LibreOffice Help for Tech Illiterates' 14.00 - 14.45: Christophe Strobbe - 'Accessibility in LibreOffice: The Way Forward' 14.45 - 15.30: Markus Mohrhard - 'Test concepts for automated Libreoffice testing' 15.30 - 16.00: Jan Holesovsky / Kendy - 'LibreOffice debugging tricks' 16.00 - 16.30: Andreas Mantke - 'Improving LibreOffice Extensions- and Template-Center' 16.30 - 17.00: Michael Meeks - 'Easy Hacks - how to become a key LibreOffice contributor' 17.00 - 17.45: Stephan Bergmann - 'Analyzing LibreOffice through Compiler Plugins' Lightning talks: * Christophe Strobbe - 'AccessODF, An Accessibility Evaluation and Repair Extension for LibreOffice Writer' (Apparently, the LibreOffice devroom has not been scheduled yet: http://fosdem.org/2012/schedule/devrooms.) Best regards, Christophe Strobbe -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [PATCH] If there's no java, don't do the java stuff
Hi Korrawit, At 18:24 8-1-2012, Korrawit Pruegsanusak wrote: Hello all, This attached patch fixes build on windows / cygwin. I'm building --without-java, and it breaks because not found java_uno_accessbridge, which seems java-related. I noticed on the mailing list that David Tardon has already pushed your patch, but I'm still curious to know: did you have the Java Access Bridge [1] installed when you tested this patch (I assume you didn't have it because the build broke)? [1] http://www.oracle.com/technetwork/java/javase/tech/index-jsp-136191.html So, I add a check whether we have SOLAR_JAVA before doing this thing. So java_uno_accessbridge is only added when SOLAR_JAVA is set to TRUE, which AFAICT is something that happens at compile time. I assume this patch is part of the work to (locate and) reduce Java dependencies in order to (1) make it easier for developers to build LibreOffice (e.g. when working on patches that have nothing to do with Java), and (2) eventually transition to a LibreOffice without any Java (i.e. for everybody, not just developers). So when the Java Accessibility API has been replaced by the IAccessible2 API, and when the Java-dependent wizards have been replaced, SOLAR_JAVA will become irrelevant. I'm basically trying to increase my understanding of what's going on, so feel free to correct me of I get it wrong :-) Best regards, Christophe My incremental build went fine after this patch, and the program started well :-) Please feel free to comment :-) Best Regards, -- Korrawit Pruegsanusak -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Question about IAccessibility2
Hi Regina, At 15:31 24-11-2011, Regina Henschel wrote: Hi Christophe, Christophe Strobbe schrieb: (...) I come across IAccessibility2 (...) Such string resources are used in method SetAccessibleName in /core/cui/source/tabpages/tpline.cxx SetAccessibleName is a method that exists in several accessibility APIs, e.g. * ATK: atk_object_set_name: http://developer.gnome.org/atk/stable/AtkObject.html#atk-object-set-name * Java: http://download.oracle.com/javase/6/docs/api/javax/accessibility/AccessibleContext.html#setAccessibleName%28java.lang.String%29 * Microsoft: http://msdn.microsoft.com/en-us/library/bb776383.aspx: IAccessibleObject::SetAccessibleName method So it is a comprehensive concept. (...) if you are referring to a list box where an author can choose between different stroke-linecap styles, I would definitely give those options an accessible name (e.g. butt cap, round cap and square cap, which I found in the SVG spec). Those are already strings, which will be localized. I have no application to test, whether this is sufficient. But I guess it will, because otherwise people would have complained in a lot of other places where list boxes are used. Just in case you would like to test this: there are two free options on Windows: * NVDA: an open-source screen reader: http://www.nvda-project.org/. (The portable version can be run from a USB key if you don't want to install it.) When testing with a screen reader, you first need to installe the Java Access Bridge: http://www.oracle.com/technetwork/java/javase/tech/index-jsp-136191.html. * The Java Accessibility Utilities, which you can (still) find at http://java.sun.com/javase/technologies/accessibility/downloads.jsphttp://java.sun.com/javase/technologies/accessibility/downloads.jsp. Because LibreOffice on Windows uses the Java Accessibility API, you can these inspection tools. The Java Accessibility Utilities include Java Monitor, Ferret, Monkey and AccessibilityMonitor. To use, for example, Java Monitor, one should go through the following steps: 1. Add the jar files jaccess.jar and jaccess-examples.jar in the CLASSPATH. 2. Modify the file lib/accessibility.properties in the JDKHOME directory to include the following line: assistive_technologies=JavaMonitor Note that the README.txt claims that this line should be AWT.assistive_technologies=JavaMonitor, but this is not correct. 3. When you start LibreOffice (or a pure Java application), Java Monitor will start automatically. For checking accessible name, description, role, value and state(s) in menus, Ferret is the appropriate tool. (Oh, and alway close LibreOffice if you want to close the accessibility utility; if you try to close the accessibility utility first, it will also close LibreOffice.) I think I postpone this special detail until the rest is finished and there is a product that can be tested in connection with an accessibility application. OK. And thanks for asking questions about accessibility :-) Best regards, Christophe -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Question about IAccessibility2
Hi Regina, At 23:11 21-11-2011, Regina Henschel wrote: Hi all, I have started to implement the attribute stroke-linecap. I assume this refers to svg:stroke-linecap (§20.164 in the ODF 1.2 spec, which refers to stroke properties in the SVG spec: http://www.w3.org/TR/SVG11/painting.html#StrokeProperties). I come across IAccessibility2 in files /core/cui/source/tabpages/tabline.hrc /core/cui/source/tabpages/tabline.src There are some string resources defined like #define STR_END_LENGTH 41 Some are commented out in lines 125 to 134 in tabline.hrc. Such string resources are used in method SetAccessibleName in /core/cui/source/tabpages/tpline.cxx SetAccessibleName is a method that exists in several accessibility APIs, e.g. * ATK: atk_object_set_name: http://developer.gnome.org/atk/stable/AtkObject.html#atk-object-set-name * Java: http://download.oracle.com/javase/6/docs/api/javax/accessibility/AccessibleContext.html#setAccessibleName%28java.lang.String%29 * Microsoft: http://msdn.microsoft.com/en-us/library/bb776383.aspx: IAccessibleObject::SetAccessibleName method I see them for some controls but not for all, especially not for maLBEdgeStyle. (1) What they are used for? (2) Why they are set for some controls but not for all? (3) Do I have to define such a string for my new linecap style list box? I don't know what the accessible name for a stroke-linecap would be (i.e. when it is present in ODF content). However, if you are referring to a list box where an author can choose between different stroke-linecap styles, I would definitely give those options an accessible name (e.g. butt cap, round cap and square cap, which I found in the SVG spec). I hope this helps. Best regards, Christophe -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] how to print into .ps
At 13:02 22-11-2011, Petr Mladek wrote: if you select Print to File check box in the Print dialog, it generates .pdf file. IMHO, if you debug printing bugs, it would be great to see the .ps file that is send to the printer. Is there any easy way how to get it? My Ubuntu installation under VirtualBox has no printers installed. When I select File Print in LibreOffice, the Options tab in the Print dialog contains a checkbox for Print to file. Checking this checkbox changes the Print button into a Print to File ... button. The Print to File ... button opens a Save dialog; this dialog contains a File type option where I can choose PostScript, and options to choose a file name and a folder. After that, I get a file that looks like PostScript to me. (It starts with %!PS-Adobe-3.0 when I open it in gedit.) But maybe what you really want to know is how to select the printer driver through which the PostScript is generated? Best regards, Christophe -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Extension dependencies
, it becomes much easier to match that extension against a given product's capabilities, regardless of brand. I'd tend to give the fine-grained dependencies a try. That would require cooperation from extension developers (they would need to voice their demand for dependencies for specific features, and they would need to make accurate use of those dependencies in their extensions). To achieve cross-product extension compatibility, it would also require some sort of advertising of LO's newly introduced fine-grained dependencies (so that other products---where possible---would pick them up together with the corresponding features), but we would need a place to document any newly introduced dependencies, anyway. What do other people think here? ** What happens when LO 4 becomes incompatible? In that case, any OpenOffice.org-minimal-version dependency, regardless of version value, should be considered as not satisfied by LO 4. Similarly, if we did introduce a LibreOffice.org-minimal-version dependency, any version value of that dependency less than 4 should be considered as not satisfied. On the other hand, treatment of any fine-grained dependencies would have to be handled on a case-by-case basis. Stephan -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Extension dependencies
Hi Stephan, Thanks for the additional guidance. At 15:48 15-11-2011, Stephan Bergmann wrote: On 11/15/2011 01:39 PM, Christophe Strobbe wrote: At 09:59 4-11-2011, Stephan Bergmann wrote: Each .oxt extension can carry any number of dependencies, specifying conditions that need to be met by the hosting LO installation for the extension to be successfully deployable (see http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Dependencies). This page links to http://openoffice.org/extensions/description/2006, which returns an ERROR 404, so even if an extension developer wanted to document more detailed dependencies, they would not know what syntax or elements to use in their description.xml file. http://openoffice.org/extensions/description/2006; is only used as an XML namespace name on that page. URLs used as XML namespace names are not generally expected to be dereferencable (and are often not). (That the wiki software used for that page displays that string as a browsable link appears to be an unfortunate mis-feature.) Ah, yes. I was hoping to find some information on the Others item in the list of child elements at http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Description_of_XML_Elements#Element_.2Fdescription.2Fdependencies. My hope got the better of my XML knowledge :-( The general syntax for dependencies within description.xml is described on that page, in the second-last paragraph (that also contains the mis-links). For the description of individual dependencies, follow the link to http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Description_of_XML_Elements#Element_.2Fdescription.2Fdependencies labelled XML description for description.xml in the See also section at the bottom of the page. (And for the description of individual dependencies relative to LO instead of OOo, https://wiki.documentfoundation.org/Development/Extension_Development is the new starting point.) I was confronted with this problem just today because a new Java-based extension cannot be installed on some Ubuntu systems even though it installs without problems on Windows and some other Ubuntu systems. The extension manager displayed the following error dialog: (...) It turns out that this issue can be solved with sudo apt-get install libreoffice-java-common So I thought about how to document that dependency in description.xml, but I couldn't ... (And libreoffice-java-common or openoffice.org-java-common may be rather broad.) Yes, extension dependencies are currently only able to express dependencies on a complete LO installation. Dependencies that are not fulfilled because only a subset of LO functionality is installed are not supported. (And note that what those available subsets are is typically also specific to each LO distribution, even if the optional module structure in scp2 sets some common ground.) OK. I have put a warning about sudo apt-get install libreoffice-java-common on the extension's download page. The error caused by the missing dependency was fairly serious; it caused my Ubuntu-inside-VirtualBox installation to completely freeze in some cases. Best regards, Christophe -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Extension dependencies
Hi Stephan, At 17:18 15-11-2011, Stephan Bergmann wrote: On 11/15/2011 04:53 PM, Christophe Strobbe wrote: (...) OK. I have put a warning about sudo apt-get install libreoffice-java-common on the extension's download page. The error caused by the missing dependency was fairly serious; it caused my Ubuntu-inside-VirtualBox installation to completely freeze in some cases. So it froze up when it displayed that inscrutable (com.sun.star.deployment.DeploymentException) ... dialog? Actually, the first times I tried to install the extension, I got an empty error dialog (I assumed it was an error dialog), and the system froze. More recently, I tried a more recent version of the extension, and this time I got the error dialog with the puzzling DeploymentException. I opened a command line and did ps -ax and killed one of the processes (I can't remember which one). However, this only worked because I had not wasted time copying the text in a text editor - which is what I did the first time. Apparently, it was important to kill the process that spawned the error dialog before it froze up the complete OS. This all happened in LibreOffice 3.3.4 [OOO330m19 (Build:401)] on Ubuntu 11.04 (Natty Narwhal) inside VirtualBox. Best regards, Christophe -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Extension dependencies
At 13:02 4-11-2011, Thorsten Behrens wrote: Stephan Bergmann wrote: As already mentioned briefly in my talk at LOCon, we need to make up our mind how to handle LO extension dependencies. Skipping most of this - I'd tend to give the fine-grained dependencies a try. That won't work in practice, unless those can be (semi-)automatically generated. Experience shows that all programmers are lazy, and seldomly go extra miles. And all generalisations are true ;-) Even those who would be willing to use fine-grained metadata for dependencies would benefit from an automated check on these data. It is easy to modify the source code in the extension and then to forget to update the dependency metadata. Best regards, Christophe Having a simple version string, and some volunteers testing uploaded extensions on the extension repo sounds much more workable - and useful in practice, since no syntactic compatibility one could come up with would ensure semantic equality... Cheers, -- Thorsten -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [Libreoffice-ux-advise] [REVIEW] text orientation, not text direction
Hi Lior, All, At 18:13 31-10-2011, Lior Kaplan wrote: On Mon, Oct 31, 2011 at 6:41 PM, Christophe Strobbe christophe.stro...@esat.kuleuven.be wrote: Hi, At 16:48 31-10-2011, Jan Holesovsky wrote: (...) UX guys - please have a look at Lior's suggestion; for a screenshot of what he means, see his original mail in the ML archive: http://lists.freedesktop.org/archives/libreoffice/2011-October/019944.html Just to make sure that everyone involved in the discussion knows how to use this feature: 1. Create a table; set text direction to right-to-left (vertical) 2. Enter some Chinese (or Japanese) text into the table. (In my case, the text appeared rotated.) 3. Change the font to one that was developed for Chinese (or Japanese, as the case may be) text. You will now see the characters in vertical columns that should be read right-to-left. Just a small notice - although the option says right to left (vertical), it only changes the horizontal/vertical part. The text directionality is kept as is (usually left to right), which causes the text to be written top to bottom (that is LRT rotates 90 clock wise). Another issue: when you select the table again and go to Table Properties, the text direction value appears empty instead of showing the value Right-to-left (vertical). You can set this value as many times as you want, when you reopen the Table Properties dialog, you always get an empty value for Text direction. Best regards, Christophe So text direction is about horizontal vs vertical (i.e. vertical, then right-to-left), rather than the direction of the writing system (left-to-right vs right-to-left/bidirectional). I have attached a sample document and a screenshot to this mail. The text below the table is identical to the text inside the table - in fact I copied it from the table. Also notice the change in quotation marks and the direction of 2012. (See also this Wordpad screenshot from Wikipedia: http://en.wikipedia.org/wiki/File:Wordpad_vertical_text_support.png .) Best regards, Christophe mainly: http://lists.freedesktop.org/archives/libreoffice/attachments/20111030/9a4f3746/attachment-0001.png http://lists.freedesktop.org/archives/libreoffice/attachments/20111030/9a4f3746/attachment-0002.obj How does that sound? Thank you, Kendy On 2011-10-31 at 17:03 +0200, Lior Kaplan wrote: On Mon, Oct 31, 2011 at 4:50 PM, Christian Lohmaier lohmaier + libreoff...@googlemail.com wrote:     Hi Lior, *,     On Sun, Oct 30, 2011 at 9:26 PM, Lior Kaplan     kaplanl...@gmail.com wrote:         In my RTL bugs talk during the conference, I showed a weird     option in the     tables options - text flow tab which refers to RTL text as     vertical     (guessing a feature for Japanese). See attached screen shot.         I'm attaching to patches to fix this:     1. A string change (trivial).     But that change doesn't improve anything at all. I immediately     understand what the difference between left-to-right and     right-to-left (vertical) means, but what the heck is     horizontal?     that could also be right-to-left, and more importantly:     Vertical could     also be left-to-right written vertically. These options doesn't touch the text directionality (RTL/LTR) but only decide whether it goes horizontally or vertically.     So I don't see any benefit in changing those. (on the     contrary, it     would replace clear labels with need to try them to figure     out what     they do ones.     As for Text direction vs Text orientation - I don't really     care,     although I'd associate left-aligned vs right-aligned more with     orientation, and the overall writing layout with direction,     but then     again I'm not a native speaker... I've changed this text for two reason: 1. To diffrenciate from the Text direction on the table tab (the previous tab in the same window). There the options are RTL and LTR which is right. 2. To use the same terminology as other word processing software. I hope this better explains the reasons for the patch. Kaplan -- Christophe Strobbe -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [PATCH] Export blinking text attribute to HTML in all HTML export modes
Hi Harri, At 18:40 27-10-2011, Harri Pitk�nen wrote: Previously blinking was not exported in IE mode. IE still does not support blinking (neither does Chrome or Safari) Lacking browser support for the blink element is a good thing from an accessibility point of view :-) For some persons, blinking can be so distracting that it prevents them from interacting with the rest of the web page: http://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits-pause.html. (In Firefox and Seamonkey, you can disable blinking by setting browser.blink_allowed to false under about:config. In Opera, you need to activate the Accessibility Layout under View - Style.) but the extra tag does not make things any worse That depends on the reader (see above). But export blink anyway. Accessibility issues in content need to be addressed in the source document, and an extension to evaluate accessibility will be released soon-ish. Best regards, Christophe and allows importing the HTML back to LibreOffice without loss of formatting. Code is also simplified by removing conditionals for options that no longer need to be (or can be) disabled. Harri -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [PATCH] vcl: Printing UI page range autofocus
Hi, At 06:50 22-10-2011, Maxim Iorsh wrote: When the user selects Pages radio button in the Range section, it is very reasonable to expect that she would now want to specify the range. Thus moving the focus automatically to the page range edit box would save the user a mouse click. Unrequested focus changes that are not announced in advance are not good practice for accessibility reasons. 1. When a screen reader user (typically a blind user) encounters a set of radio buttons, the only way to find out what the buttons are, is going through them with the up/down arrow. If the focus changes to the page range input field when she puts the focus on the Pages radio button, the label for the radio button will either not be read by the screen reader or the labels for the radio button and the edit field will be run together, which might lead to confusion. 2. Keyboard users (not only blind users) move through dialogs like the Print dialog with the Tab key and the Shift+Tab key. The latter is for navigating backwards. With this patch, what happens when the user presses Shift+Tab from the Page Range field in order to move back to the radio buttons? Does the focus immediately get pushed back to the edit field, making backwards navigation impossible? Best regards, Christophe Code is contributed under the LGPLv3+ / MPL. Signed-off-by: Maxim Iorsh io...@users.sourceforge.net --- vcl/source/window/printdlg.cxx | 21 + 1 files changed, 21 insertions(+), 0 deletions(-) -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] LibreOffice documentation and extensions
Hi Kendy, At 16:06 17-10-2011, Jan Holesovsky wrote: (...) On 2011-10-12 at 18:50 +0200, Christophe Strobbe wrote: OpenOffice.org used to provide a way for extensions to provide documentation that would seamlessly integrate into the OOo.org Help system (see http://wiki.services.openoffice.org/wiki/Extensions_best_practices#Help_Content). LibreOffice, by contrast, has Help documentation online. Is there a way for extension documentation to get integrated into LibreOffice Help? It is actually a bug, that LibreOffice does not use the help provided by the extension, when it exists. Do you think you would be interested in helping to fix that? The code that decides whether the help is installed is here: http://cgit.freedesktop.org/libreoffice/core/tree/sfx2/source/appl/sfxhelp.cxx#n672 [and around that] Thanks for the bug identification and the pointer to the code. Unfortunately my knowledge of C++ is just as bad as my knowledge of Early Middle Japanese. I would like to learn it (C++ I mean) but have not yet found the time :-( so I don't know how to help fix this. I assume that fixing this bug would enable integration of extension help content into the LibO Help system from the installable help pack. Since users do not necessarily install this help pack, extension authors would also want their help documentation to be available online at http://help.libreoffice.org/Main_Page. After reading http://wiki.documentfoundation.org/Development/Wikihelp#Open_questions, it appears that I'll need to wait a bit. Best regards, Christophe It decides only on the availability of the main help, but does not do anything about extensions; might be worth extending so that when the help for an extension is installed (and asked for), the extension's help would be shown. Regards, Kendy -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] LibreOffice documentation and extensions
Hi, OpenOffice.org used to provide a way for extensions to provide documentation that would seamlessly integrate into the OOo.org Help system (see http://wiki.services.openoffice.org/wiki/Extensions_best_practices#Help_Content). LibreOffice, by contrast, has Help documentation online. Is there a way for extension documentation to get integrated into LibreOffice Help? Best regards, Christophe -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [EASY HACKS] machine translation of remaining german comments acceptable?
Hi, A few comments inline below. At 15:12 5-10-2011, Noel Grandin wrote: Hi I'm trying to write a machine translation program for the remaining german comments in the source code (using google-translate to do the heavy lifting). Is this acceptable? I'm not a german speaker, so I won't be able to vet the resulting translation for accuracy, but I've done this before for other applications, and the results were deemed reasonable. I have the basic process working already (see below), but still lots of tweaking to go. Thanks, Noel Grandin --- automation/source/simplecm/simplecm.cxx:417:CommunicationLinkRef rHold(pCL);// H?lt den Zeiger bis zum Ende des calls automation/source/simplecm/simplecm.cxx:417:CommunicationLinkRef rHold(pCL);// Keeps the pointer to the end of calls - ... to the end of the call --- automation/source/testtool/cmdstrm.cxx:375:/// #59513# nicht mehr ben?tigt ( siehe oben ) automation/source/testtool/cmdstrm.cxx:375:/// # 59 513 # bentigt not (see above) Should translate to no longer needed (see above). --REJECTED- automation/source/testtool/objtest.cxx:3107:// to prevent VorlagenLaden/UntergeordneteIniDatei/SpeichernDlg/OrdnerDlg/OeffnenDlg/MessageBox/LetzteVersion/GrafikEinfuegenDlg/FarbeDlg/ExportierenDlg/DruckerEinrichten/DruckenDlg/DateiEinfuegenDlg/Active automation/source/testtool/objtest.cxx:3107:// to preventable Not sure what to advise here... --- basctl/source/basicide/baside2.cxx:263:// Import von baside4.cxx basctl/source/basicide/baside2.cxx:263:// Import of baside4.cxx --- basctl/source/basicide/basidesh.cxx:257:// Damit bei einem Basic-Fehler beim Speichern die Shell nicht sofort basctl/source/basicide/basidesh.cxx:257:// This not a basic error when saving the shell immediately The German sentence is incomplete. I think the English translation should be something like: To prevent the shell from [missing end of sentence] when a Basic error occurs during saving. --- basic/source/app/textedit.cxx:260:if ( r.nStart r.nEnd )// Nur bis Bug von MD behoben basic/source/app/textedit.cxx:260:if ( r.nStart r.nEnd )// Fixed bug only to the MD I don't understand the German comment. --- basic/source/classes/sbunoobj.cxx:2721:// nicht als feste Property in das Object aufgenommen werden und basic/source/classes/sbunoobj.cxx:2721:// are not included as a fixed property in the Object The German source is an incomplete sentence, so it's hard to judge the translation. --- basic/source/runtime/props.cxx:93:// liefert eine leere Objekt-Variable. basic/source/runtime/props.cxx:93:// returns an empty object variable. --- basic/source/sbx/sbxvar.cxx:179:// Because the method could be called from outside, check the Da die Methode von aussen aufrufbar ist, hier noch einmal basic/source/sbx/sbxvar.cxx:179:// Because the method could be called from outside, check the outside, as the method is accessible from here again Ah, so Google alto translates Denglisch to English. ;-) I think the English translation should be something like: Since the method can be called from outside (outside what?), [missing verb/end of sentence] [needs to? / should be?] again here. Best regards, Christophe -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [PATCH] fdo#40373 - export xhtml parse error
Hi, At 11:13 29-9-2011, Michael Meeks wrote: Hi Regina, On Wed, 2011-09-28 at 15:50 +0200, Regina Henschel wrote: The patch fixes the following error: When you export a document via File-Export-XHTML it generates an invalid file, because the lang attribute gets a wrong namespace. Nice patch to fix it :-) I assume you have commit access to push that ? [1] I do not know, whether this will fix bug fdo#40373; but it fixes, that the currently exported file is invalid, as described above. Sounds like it fixes the issue to me, if it is a multi-issue bug it needs splitting up :-) The a11y issue is annoying, but I'm not sure we should generate bad output for that, although of course we should accept bad input gracefully wherever possible. OK, I'll work on the other issues (especially accessibility) separately, so there are no objections to push this patch. Best regards, Christophe Thanks, Michael. [1] - if not, please can you follow this flow: http://www.freedesktop.org/wiki/AccountRequests and mail me the bug number privately :-] -- michael.me...@suse.com , Pseudo Engineer, itinerant idiot -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [PATCH] fdo#40373 - export xhtml parse error
Hi Regina, At 15:50 28-9-2011, Regina Henschel wrote: Hi all, The patch fixes the following error: When you export a document via File-Export-XHTML it generates an invalid file, because the lang attribute gets a wrong namespace. How to proof it: Export any file and make sure, that the file extension is xhtml. Upload the file to http://validator.w3.org/#validate-by-upload to validate it. Do this with the current version to see the error. Do the same with a patched version, to see that it is OK then. Please don't throw away the lang attribute by replacing it with xml:lang, just add xml:lang. Language information is important for text-to-speech software, and last time I checked, screen readers only supported lang, not xml:lang. What is really needed to solve the namespace issue is replacing namespace=http://www.w3.org/XML/1998/namespace; with xmlns=http://www.w3.org/1999/xhtml; Best regards, Christophe I do not know, whether this will fix bug fdo#40373; but it fixes, that the currently exported file is invalid, as described above. Kind regard Regina -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [PATCH] fdo#40373 - export xhtml parse error
Hi, At 16:14 28-9-2011, Christophe Strobbe wrote: Hi Regina, At 15:50 28-9-2011, Regina Henschel wrote: Hi all, The patch fixes the following error: When you export a document via File-Export-XHTML it generates an invalid file, because the lang attribute gets a wrong namespace. How to proof it: Export any file and make sure, that the file extension is xhtml. Upload the file to http://validator.w3.org/#validate-by-upload to validate it. Do this with the current version to see the error. Do the same with a patched version, to see that it is OK then. Please don't throw away the lang attribute by replacing it with xml:lang, just add xml:lang. Language information is important for text-to-speech software, and last time I checked, screen readers only supported lang, not xml:lang. Correction: I now notice that the exported format is XHTML 1.1 plus MathML 2.0 (which does not support the lang attribute), not XHTML 1.0 (where lang was still allowed). From my point of view accessibility is more important than that little validation issue, so I would still argue in favour of keeping the lang attribute. What is really needed to solve the namespace issue is replacing namespace=http://www.w3.org/XML/1998/namespace; with xmlns=http://www.w3.org/1999/xhtml; Oops, sorry, I was comparing XSLT code with XHTML code. The XSLT code already outputs xmlns=http://www.w3.org/1999/xhtml; Best regards, Christophe Best regards, Christophe I do not know, whether this will fix bug fdo#40373; but it fixes, that the currently exported file is invalid, as described above. -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] IAccessible2 - Windows (from libreoffice-accessibility)
Hi, For those of you who are interested in the accessibility of LibreOffice (and OpenOffice.org) on Windows - i.e. replacing the Java Accessibility API with IAccessible2 - , I am forwarding a message that Malte Timmermann sent to the LibreOffice Accessibility list. It appears that the code is still only available in CWSes: http://hg.services.openoffice.org/. Malte Timmermann's message describes in what order the code from the CWSes was meant to be integrated. This is relevant to feature request/bug https://bugs.freedesktop.org/show_bug.cgi?id=39956. Best regards, Christophe Delivered-To: global.libreoffice.org--accessibil...@bilbo.documentfoundation.org Date: Mon, 12 Sep 2011 10:32:38 +0200 From: Malte Timmermann malte_timmerm...@gmx.com To: accessibil...@global.libreoffice.org Subject: Re: [libreoffice-accessibility] Re: OpenOffice.org code on Apache: IAccessible2 ? Archived-At: http://go.mail-archive.com/HCe2Qs3e9rxv6IRhaZd3IY2aqm0= Michael Stahl and Dennis Hamilton are right wrt IA2 CWSes listed below. accfixes2 is ready for QA, but was intended to be integrated _after_ 3.4 just to make sure we don't break Accessibility on some other platform short before the release. But feel free to integrate, and do some testing on Windows, GNOME and Mac. It will not introduce any IA2 stuff. accia2bridge is not critical to integrate, as this is Windows-only (UAA IA2 bridge) and can't break anything on other platforms. But it will remove the Java Accessibility stuff on Windows, so better do this as the last step. accfixes3 was intended to be the last CWS with IA2 stuff. All remaining changes where in accstuff, and my plan was to migrate (adapted) changes from accstuff to accfixes3, or delete not wanted stuff in accstuff, and never integrate accstuff itself. Unfortunately somebody already did it the other way round and moved a larger, not reviewed chunk of code from accstuff from accfixes3 (276449:e44059869aa9). accstuff (+accfixes3 with 276449:e44059869aa9) still contains changes made in a way I wouldn't integrate them in OOo, but now it's up to other people to decide whether or not to integrate stuff as it is. It's not up to me anymore to have an eye on OOo architecture. (But note that also the people responsible for the modules with remaining changes didn't want to integrate them as they are) Once stuff above is integrated, there is still some minor work missing. I might be able to help on that, but I don't plan to do the integration work for accfixes*, at least not for LibreOffice, because there will be many conflicts. Integration into AOOo should be quite smooth. For the remaining changes, I guess I would like to do it the same way like my old friend, the Pseudo Engineer and itinerant idiot ;) A little bit of poking around, hacking, and providing a patch compiled and tested only on my primary platform :) Malte. PS: I don't read the mailings lists regularly, and the accessibility list is the only one I really look into. But chances to miss something are high. If you have questions on the OOo IA2 stuff here, and I don't answer them in a timely manner, drop me a note w/o cc-ing a mailing list so it will make it to my inbox. On 09.09.2011 21:45, Michael Stahl wrote: On 02.09.2011 11:56, Christophe Strobbe wrote: Hi, The OpenOffice.org code is now available on Apache: http://incubator.apache.org/openofficeorg/source.html. Yesterday, the Apache OOo blog published an article on developer education, so the code should be ready for attempts to compile it on Linux: https://blogs.apache.org/OOo/entry/apache_openoffice_org_developer_education. Since we have a bug on IAccessible2 at https://bugs.freedesktop.org/show_bug.cgi?id=39956 I wanted to find out where the code relevant to IAccessible2 can be found in the repository at Apache and add some information about that to the bug. Can anybody help? (I have only browsed the repository in my web browser; I have not checked out the code from SVN.) the Apache SVN currently contains only the OOO340 head (i.e. everything that was integrated until OOO340_m1). apparently the IA2 stuff is in a not-yet-integrated CWS on the OOo HG server: http://hg.services.openoffice.org/cws/accia2bridge/ it currently looks like this (like most open CWSes) won't be integrated into ApacheOOo for quite some time, as it is not in scope for the 3.4 release, and there is unfortunately some work to do first to comply with Apache's annoying licensing policies etc. there are some more not-yet-integrated CWSes that look a11y related: http://hg.services.openoffice.org/cws/accfixes2/ http://hg.services.openoffice.org/cws/accfixes3/ http://hg.services.openoffice.org/cws/accstuff/ but i've never worked on a11y myself, so don't ask me what the status of any of this is. regards, michael -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document
Re: [Libreoffice] IAccessible2 - Windows (from libreoffice-accessibility)
Hi Michael, At 16:41 27-9-2011, Michael Meeks wrote: Hi Christophe, Thanks for forwarding this. On Tue, 2011-09-27 at 10:50 +0200, Christophe Strobbe wrote: It appears that the code is still only available in CWSes: http://hg.services.openoffice.org/. Malte Timmermann's message describes in what order the code from the CWSes was meant to be integrated. It is very useful for archiving understanding on the off chance that IBM don't meet their commitment to do the right thing and get this into Apache in a form that we can easily consume. The real question is - should we spend time continuing the (nice) work that Malte started, when we know that IBM have this done working in-house, and have committed to release it at some stage. I apologise in advance if I sound repetitive... My understanding was that IBM donated IAccessible2 code based on an OpenOffice.org version that was outdated by the time of their donation, and that Malte Timmermann was working on integrating the code when Oracle decided to give OOo to the community. As far as I know, what IBM has done working in-house and promised to release is Lotus Symphony code, i.e. with an SWT-based UI. SWT does not expose accessibility info through the Java Accessibility API but through the accessibility API of the target desktop operating system (at least Eclipse does that [1]). (Continued below...) AFAICS that is still not a great use of developer time, though we can help support a volunteer that wants to that I guess. It has the potential to make merging IBM's re-worked version of what they publicly released before even more painful though - so in fact this could potentially waste developer time twice. Ideally we'd have a commitment from whomever did the merging that they would then help unwind the consequences / merge the delta to IBM's work later. IMHO the best outcome is still for IBM to live up to their public commitments and release the IAcc2 integration code, and for us to merge it as/when that is done. As/when/until they do them - I suspect this space will stay as sterile - for which IBM bear a large responsibility. If IBM plans to release Lotus Symphony code that already supports IAccessible2, I have very little hope that they will first integrate the CWSes with IAccessible2 code into the current trunk of OpenOffice.org (see also Fridrich Strba's message). So I think that waiting for IAccessible2 will come down to waiting for the Lotus Symphony donation. LibreOffice would then have the choice between using the CWSes or integrating the UI from Lotus Symphony. Then again - it is a really nice feature that would be great to have, not least due to it dropping a Java dependency. Anyhow, that's my take, sorry if that's not the answer you want. [1] See http://www.ibm.com/developerworks/rational/library/dec05/pilgrim/ and http://www.eclipse.org/articles/article.php?file=Article-Accessibility351/index.html. Best regards, Christophe HTH, Michael. -- michael.me...@suse.com , Pseudo Engineer, itinerant idiot -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] [PATCH] Bug 39561 (XHTML export filter)
Hi, At 17:26 9-8-2011, Noel Power wrote: On 04/08/11 16:14, Christophe Strobbe wrote: Hi, Attached is a patch for Bug 39561 Use svg:title, not svg:desc for XHTML img alt attribute [accessibility] https://bugs.freedesktop.org/show_bug.cgi?id=39561. I am new to Git and LibreOffice development and generated this patch with git diff ... (I couldn't figure out how to use format-patch). the patch looks fine, but I am not at all sure about which attribute should be mapped into the 'alt' tag, to me the description seems like a better fit ( a more verbose image replacement is better ? ), svg:title should definitely be mapped to the alt attribute (based on my understanding of XHTML, ODF and SVG, and on 10 years of RD in accessibility). The user should be able to decide whether or not to get a long description after getting the short description. A long description is not required for every image. otoh it would seem that the html xhtml filters should be consistent. I've committed the patch to master in any case, thanks for the patch btw, can you confirm patch is LGPLv3+/MPL1.1, I confirm that I make this patch available under LGPLv3+/MPL1.1. By the way, I could not find the full process for fixing and closing bugs on http://www.libreoffice.org/get-involved/developers/ or http://wiki.documentfoundation.org/Development. I missed: * any mention of the need to confirm that you submit your patch under LGPLv3+/MPL1.1 (and that you can make a blanket statement like the one by Lionel Elie Mamane two days ago http://lists.freedesktop.org/archives/libreoffice/2011-August/016134.html; * Who closes the reported bug and when (presumably only after it has been committed). (Ah, I just noticed Noel closed the bug.) Who should I contact to update the Wikipage? Best regards, Christophe -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] [PATCH] Bug 39561 (XHTML export filter)
Hi, Attached is a patch for Bug 39561 Use svg:title, not svg:desc for XHTML img alt attribute [accessibility] https://bugs.freedesktop.org/show_bug.cgi?id=39561. I am new to Git and LibreOffice development and generated this patch with git diff ... (I couldn't figure out how to use format-patch). Best regards, Christophe Strobbe -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 http://www.docarch.be/ Twitter: @RabelaisA11y --- Open source for accessibility: results from the AEGIS project www.aegis-project.eu --- Please don't invite me to Facebook, Quechup or other social networks. You may have agreed to their privacy policy, but I haven't. Bug039561.patch Description: Binary data ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] LibreOffice / OpenOffice.org sniffing in extension
Hi Laurent, On Mon, 16 May 2011 16:53:05 +0200, Laurent Godard oooc...@free.fr wrote: Hi Christophe perharps not perfect (and in fact surely ;) ) here is how i quickly solved this using macros can be implemented in java Thanks a lot. I managed to create a Java version that I can use in an extension. btw, perharps not the right mailing list I thought it was a developer question... What is the right mailing list for this kind of question? Best regards, Christophe HTH laurent '- function isLibreOffice dim aSettings, nom aSettings = getConfigSetting(/org.openoffice.Setup/Product, false) nom = aSettings.ooName isLibreOffice = (nom = LibreOffice) end function function getConfigSetting(target as string, forUpdate as boolean) dim service as String ' nom du service d'acces à la configuration dim aSettings, aConfigProvider dim aParams(0) As new com.sun.star.beans.PropertyValue dim varEmpty if forUpdate then service = com.sun.star.configuration.ConfigurationUpdateAccess else service = com.sun.star.configuration.ConfigurationAccess endif aConfigProvider = createUnoService( com.sun.star.configuration.ConfigurationProvider ) aParams(0).Name = nodepath aParams(0).Value = target aSettings = aConfigProvider.createInstanceWithArguments(service, aParams() ) getConfigSetting = aSettings end function -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 www.docarch.be Twitter: @RabelaisA11y ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice] LibreOffice / OpenOffice.org sniffing in extension
Hi, I am involved in a project that develops a few extensions (mostly in Java) for OpenOffice.org and LibreOffice, and I would like to find a way to make an extension detect in which of these two office suites it is installed. I have not been able to find this in API documentation or elsewhere. Can you give me a hint? (Background: each of the extensions work in both OOo and LibO, but two of the extensions can't be used together in LibO 3.3.) Best regards, Christophe -- Christophe Strobbe K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on Document Architectures Kasteelpark Arenberg 10 bus 2442 B-3001 Leuven-Heverlee BELGIUM tel: +32 16 32 85 51 www.docarch.be Twitter: @RabelaisA11y ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
