The document describes two OpenOffice.org/LibreOffice extensions called odt2daisy and odt2braille that allow generating accessible formats like DAISY digital talking books and Braille from OpenOffice/LibreOffice documents. The extensions were developed as part of the AEGIS project to improve accessibility. Odt2daisy can convert documents to the DAISY format with synchronized text and audio. Odt2braille is still in development but aims to allow embedding Braille codes and embossing directly from OpenOffice/LibreOffice.
The document discusses the NLP Interchange Format (NIF) 2.0, which aims to achieve interoperability between NLP tools, resources, and annotations. It notes that NIF 2.0 will be published within 6-8 weeks and is highly likely to become the de facto standard for modeling RDF tool output in NLP. The document analyzes problems in the current NLP landscape such as heterogeneity of technologies, formats, languages, and lack of open collaboration and standards. It presents NIF as a solution to these problems by defining text normalization, an RDF-based core ontology, modular ontologies, and infrastructure for validation, hosting, and adoption. Evaluation approaches and a positive impact and reception of N
The document discusses accessibility features and issues in LibreOffice. It describes LibreOffice's accessibility for blind, low vision, deaf, motor impaired, and cognitively impaired users. Key features covered include applying styles, alternative text for images, language identification, and exporting to accessible PDF. Issues mentioned include lost alternative text when images are modified and language identification issues in Impress and Calc exports. The presentation was given at FOSDEM to discuss the AEGIS project and accessible authoring.
One of the main advantages of the OpenDocument format for office documents is that it is very, very easy to generate or process automatically. Anybody who needs to generate many similar texts, spreadsheets and presentations and is willing to run some scripts can save countless hours of work with ODF. In this talk I have explained how to do this applying the general method I call ODF Scripting. Background and more info at http://mfioretti.com/2010/09/budapest-openoffice-org-conference-2010-odf-scripting-and-odf-future/
Kálmán “KAMI” Szalai presented on building community around and creating non-coding LibreOffice extensions. Key points include:
1) Non-coding extensions can contain templates, dictionaries, galleries, settings and other OpenDocument files. They are packaged and distributed as a single .oxt file.
2) Extensions can be installed for all users on a system or just for an individual user. They integrate content and functionality into LibreOffice.
3) The structure and components of an extension are defined, including required files like META-INF/manifest.xml and optional files like templates, descriptions and licenses.
4) Template categories, language support, and a
Andrei Zmievski gave a presentation on PHP 6 and Unicode at a PHP Meetup in July 2008. He discussed how PHP 6 includes support for Unicode that PHP 5 lacks, and explained what Unicode is and why it is important. Specifically, he defined Unicode as a standard that assigns a unique number to every character, allowing text to be reliably represented no matter the platform, program, or language. He also touched on mojibake, the phenomenon of corrupted text that can occur without proper Unicode support.
Presentation at DrupalCamp Kyiv (Sept.14-15, 2012) - an updated version of the presentation made for DrupalCafé Kyiv in April 2012.
http://camp12.drupal.ua
Best Practices with Zend Framework - Matthew Weier O'Phinneydpc
The document outlines best practices for PHP development including testing code, using coding standards, learning and applying design patterns, documenting code and applications with documentation generators and XML, using source control like Subversion, and providing documentation for end users. The key messages are to test code instead of debugging, use an established coding standard to minimize politics and ensure consistency, and learn from existing design patterns that have proven solutions to common problems.
The document discusses differences between software localization and documentation translation, and why SDL Passolo is better suited than SDL Trados Studio for software localization. It notes that documents are self-contained, sentence-based, and use surrounding context, while software uses non-self-contained string IDs as context. It also explains that developers and workflows differ between the two. The document then outlines SDL Passolo's features for internationalization, localization project management, and integration with development workflows and quality assurance. It positions SDL Passolo and SDL Trados Studio as distinct but complementary solutions.
SDL Passolo is a software localization solution that allows for optimal localization workflows between developers and localizers. It streamlines communication and controls linguistic quality in source and target languages. SDL Passolo is the right tool for software localization because it reduces friction between parties and allows sharing of translation assets between SDL products while accounting for the differences between software localization and documentation translation.
A very good presentation that has been used by a couple presenters of the SDPHP group, including myself. Takes you from the very basics of PHP to more advanced ideas like OOP.
The document presents the LPOD project, which aims to develop an OpenDocument library for Python, Perl, and Ruby. The objectives are to provide a common API for these languages for OpenDocument files and implement a high-level, business intelligence oriented API. The project is supported by French organizations and includes members from 4 companies and 4 public research laboratories. It takes a top-down, multilingual approach to strictly implement the ODF standard and extend its usage beyond traditional office documents.
How community software supports language documentation and data analysisPeter Bouda
Field linguists have increasingly adopted the latest technologies and tools for language documentation. Their needs have led to remarkable developments in software and archiving, exemplified by work at the MPI in Nijmegen, which leads the innovation cycles that take place in the digital working environments of field linguists. The next step in research is now the analysis and theoretical exploitation of the huge amount of data that has been collected in numerous language documentation projects that use these environments. This research will also rely on computer-based strategies, as data is instantly available in digital formats.
In this talk I will introduce some of the lesser known tools and software packages for annotation and analysis tasks. Some of these tools were created within DOBES projects and/or as community projects by small teams; they can be combined with well-known tools like ELAN or Toolbox to give researchers access to their data. I will focus on how a combination of simple, special purpose tools makes researchers more productive and how existing software libraries allow scientific projects to create their own, task-specific software tools that they can tailor to their own needs.
This document provides instructions for translating MOBOTIX software using the MOBOTIX TransPack translation package. It describes downloading and installing the required Qt Linguist software, setting up the TransPack project folder, using Qt Linguist to translate strings in the .ts files, and running a batch file to generate translated language files for use with the MOBOTIX software. The translation process involves opening the .ts files in Qt Linguist, translating strings, and generating translated files that can be copied to the MOBOTIX software folders to enable displayed text in the target language.
1) The VICON project aims to create a virtual user model to support the inclusive design of consumer products and user interfaces for people with sensory or physical impairments.
2) The virtual user model will provide recommendations throughout the design process and allow designers to virtually evaluate designs via linking to digital human models.
3) The goal is for mainstream manufacturers to better understand the needs of impaired users and design more accessible products and user interfaces from the beginning of the design process.
The document discusses odt2braille, an OpenOffice.org extension that generates Braille from word processing documents. It enables end-users to produce Braille natively in OpenOffice.org using existing Braille translation tools. An alpha version supports embossing to some braille embossers and exporting to braille formats. Future plans include adding spreadsheet and presentation support, more embosser compatibility, and accessibility checks.
This document summarizes an integration project called Guadalinfo Accesible. The project aims to improve accessibility in telecenters in Andalusia, Spain to promote digital inclusion of people with disabilities. It will invest over 4 million euros to supply assistive technologies like keyboards, mice and screens. It will also adapt software like screen readers and develop new tools. The project will train staff and raise public awareness on accessibility issues for people with disabilities.
This document summarizes the past, present, and future of open accessibility on the desktop according to Peter Korn. It discusses the history of accessibility standards and frameworks like GNOME and Java accessibility. It outlines key accessibility components in GNOME like Orca and applications like OpenOffice.org. It also envisions future improvements in areas like assistive technologies, applications, and developer tools to further accessibility.
Cloud4all cloud platforms lead to open and universal access for people with ...AEGIS-ACCESSIBLE Projects
The Global Public Inclusive Infrastructure (GPII) initiative aims to:
1) Simplify accessibility for users in various contexts through built-in accessibility and ubiquitous access.
2) Grow the assistive technology market to serve more people at lower costs.
3) Facilitate international collaboration to lower costs and accelerate innovation.
The Cloud4All project will focus on developing personal profiles, federated repositories of accessibility solutions, and auto-personalization of information and communication technologies to work toward some of the goals of the GPII initiative. It aims to create a new paradigm of accessibility by automatically personalizing mainstream products and services for each user based on their needs profile.
1 An ontological framework for the elderly to control their home environment AEGIS-ACCESSIBLE Projects
The document discusses an ontological framework for integrating home automation devices to help the elderly live independently. It proposes a three-layered ontology structure with an abstract generic layer, a middle categorization layer, and a lower device-specific layer provided by manufacturers. This modular structure allows different levels of functional integration depending on available data, and provides standardization to connect diverse existing devices to ambient assisted living services. A demonstration of the publicly available ontology and an authoring tool is referenced.
This document contains links to various images on Flickr related to disease. It does not provide any other context or information about the images. The links are to photos of different diseases, medical illustrations, and vaccine packaging.
Project number: 224348
Project acronym: AEGIS
Project title: Open Accessibility Everywhere: Groundwork, Infrastructure, Standards
Starting date: 1 September 2008
Duration: 48 Months
AEGIS is an Integrated Project (IP) within the ICT programme of FP7
The document discusses creating accessible documents with LibreOffice/OpenOffice Writer. It covers features for accessibility like styles, headings, alternative text for images. It also discusses exporting to accessible formats like DAISY and Braille. Issues are highlighted, such as accessibility checkers and bugs in Writer. Methods for checking and improving document accessibility are provided.
odt2daisy is a software tool that enables end users to generate DAISY digital talking books from OpenOffice documents for persons with print disabilities. It was developed to support the DAISY 3 format with or without audio, as well as the DAISY 2.02 format. The tool includes a Java library that converts OpenOffice documents to DAISY XML using XSLT and validates the output. It has been tested on Windows and supports multiple languages with text-to-speech in 27 languages.
odt2daisy is a software tool that enables end users to generate DAISY digital talking books from OpenOffice.org documents for persons with print disabilities. It was developed to support the DAISY 3 format with or without audio, as well as the DAISY 2.02 format. The tool includes a Java library that converts ODT files to DAISY XML using XSLT and validates the output. It has been tested on Windows and supports 27 languages for text-to-speech synthesis. While it supports many ODT features, some complex text layouts are not supported.
AccessODF is a tool that evaluates and repairs accessibility issues in LibreOffice/OpenOffice.org Writer documents. It identifies over 30 common errors and provides suggestions for fixing problems. The first version was released in November 2011 and checks documents for issues like missing image alt text, improper language identification, or tables created with tabs instead of proper coding. It also includes checks specific to creating accessible DAISY or Braille formats. The goal is to help users make documents more accessible for people with disabilities.
odt2braille is an open-source extension for LibreOffice Writer and OpenOffice.org Writer that allows the software to produce Braille documents. It converts standard office documents into Braille format files that can be printed on Braille embossers or exported to other Braille file types. The extension provides formatting and layout for both print and Braille output in a single file. It uses existing open-source libraries for Braille formatting and embosser communication. odt2braille enables authors to seamlessly create accessible documents for both sighted and visually impaired users.
The document discusses differences between software localization and documentation translation, and why SDL Passolo is better suited than SDL Trados Studio for software localization. It notes that documents are self-contained, sentence-based, and use surrounding context, while software uses non-self-contained string IDs as context. It also explains that developers and workflows differ between the two. The document then outlines SDL Passolo's features for internationalization, localization project management, and integration with development workflows and quality assurance. It positions SDL Passolo and SDL Trados Studio as distinct but complementary solutions.
SDL Passolo is a software localization solution that allows for optimal localization workflows between developers and localizers. It streamlines communication and controls linguistic quality in source and target languages. SDL Passolo is the right tool for software localization because it reduces friction between parties and allows sharing of translation assets between SDL products while accounting for the differences between software localization and documentation translation.
A very good presentation that has been used by a couple presenters of the SDPHP group, including myself. Takes you from the very basics of PHP to more advanced ideas like OOP.
The document presents the LPOD project, which aims to develop an OpenDocument library for Python, Perl, and Ruby. The objectives are to provide a common API for these languages for OpenDocument files and implement a high-level, business intelligence oriented API. The project is supported by French organizations and includes members from 4 companies and 4 public research laboratories. It takes a top-down, multilingual approach to strictly implement the ODF standard and extend its usage beyond traditional office documents.
How community software supports language documentation and data analysisPeter Bouda
Field linguists have increasingly adopted the latest technologies and tools for language documentation. Their needs have led to remarkable developments in software and archiving, exemplified by work at the MPI in Nijmegen, which leads the innovation cycles that take place in the digital working environments of field linguists. The next step in research is now the analysis and theoretical exploitation of the huge amount of data that has been collected in numerous language documentation projects that use these environments. This research will also rely on computer-based strategies, as data is instantly available in digital formats.
In this talk I will introduce some of the lesser known tools and software packages for annotation and analysis tasks. Some of these tools were created within DOBES projects and/or as community projects by small teams; they can be combined with well-known tools like ELAN or Toolbox to give researchers access to their data. I will focus on how a combination of simple, special purpose tools makes researchers more productive and how existing software libraries allow scientific projects to create their own, task-specific software tools that they can tailor to their own needs.
This document provides instructions for translating MOBOTIX software using the MOBOTIX TransPack translation package. It describes downloading and installing the required Qt Linguist software, setting up the TransPack project folder, using Qt Linguist to translate strings in the .ts files, and running a batch file to generate translated language files for use with the MOBOTIX software. The translation process involves opening the .ts files in Qt Linguist, translating strings, and generating translated files that can be copied to the MOBOTIX software folders to enable displayed text in the target language.
1) The VICON project aims to create a virtual user model to support the inclusive design of consumer products and user interfaces for people with sensory or physical impairments.
2) The virtual user model will provide recommendations throughout the design process and allow designers to virtually evaluate designs via linking to digital human models.
3) The goal is for mainstream manufacturers to better understand the needs of impaired users and design more accessible products and user interfaces from the beginning of the design process.
The document discusses odt2braille, an OpenOffice.org extension that generates Braille from word processing documents. It enables end-users to produce Braille natively in OpenOffice.org using existing Braille translation tools. An alpha version supports embossing to some braille embossers and exporting to braille formats. Future plans include adding spreadsheet and presentation support, more embosser compatibility, and accessibility checks.
This document summarizes an integration project called Guadalinfo Accesible. The project aims to improve accessibility in telecenters in Andalusia, Spain to promote digital inclusion of people with disabilities. It will invest over 4 million euros to supply assistive technologies like keyboards, mice and screens. It will also adapt software like screen readers and develop new tools. The project will train staff and raise public awareness on accessibility issues for people with disabilities.
This document summarizes the past, present, and future of open accessibility on the desktop according to Peter Korn. It discusses the history of accessibility standards and frameworks like GNOME and Java accessibility. It outlines key accessibility components in GNOME like Orca and applications like OpenOffice.org. It also envisions future improvements in areas like assistive technologies, applications, and developer tools to further accessibility.
Cloud4all cloud platforms lead to open and universal access for people with ...AEGIS-ACCESSIBLE Projects
The Global Public Inclusive Infrastructure (GPII) initiative aims to:
1) Simplify accessibility for users in various contexts through built-in accessibility and ubiquitous access.
2) Grow the assistive technology market to serve more people at lower costs.
3) Facilitate international collaboration to lower costs and accelerate innovation.
The Cloud4All project will focus on developing personal profiles, federated repositories of accessibility solutions, and auto-personalization of information and communication technologies to work toward some of the goals of the GPII initiative. It aims to create a new paradigm of accessibility by automatically personalizing mainstream products and services for each user based on their needs profile.
1 An ontological framework for the elderly to control their home environment AEGIS-ACCESSIBLE Projects
The document discusses an ontological framework for integrating home automation devices to help the elderly live independently. It proposes a three-layered ontology structure with an abstract generic layer, a middle categorization layer, and a lower device-specific layer provided by manufacturers. This modular structure allows different levels of functional integration depending on available data, and provides standardization to connect diverse existing devices to ambient assisted living services. A demonstration of the publicly available ontology and an authoring tool is referenced.
This document contains links to various images on Flickr related to disease. It does not provide any other context or information about the images. The links are to photos of different diseases, medical illustrations, and vaccine packaging.
Project number: 224348
Project acronym: AEGIS
Project title: Open Accessibility Everywhere: Groundwork, Infrastructure, Standards
Starting date: 1 September 2008
Duration: 48 Months
AEGIS is an Integrated Project (IP) within the ICT programme of FP7
The document discusses creating accessible documents with LibreOffice/OpenOffice Writer. It covers features for accessibility like styles, headings, alternative text for images. It also discusses exporting to accessible formats like DAISY and Braille. Issues are highlighted, such as accessibility checkers and bugs in Writer. Methods for checking and improving document accessibility are provided.
odt2daisy is a software tool that enables end users to generate DAISY digital talking books from OpenOffice documents for persons with print disabilities. It was developed to support the DAISY 3 format with or without audio, as well as the DAISY 2.02 format. The tool includes a Java library that converts OpenOffice documents to DAISY XML using XSLT and validates the output. It has been tested on Windows and supports multiple languages with text-to-speech in 27 languages.
odt2daisy is a software tool that enables end users to generate DAISY digital talking books from OpenOffice.org documents for persons with print disabilities. It was developed to support the DAISY 3 format with or without audio, as well as the DAISY 2.02 format. The tool includes a Java library that converts ODT files to DAISY XML using XSLT and validates the output. It has been tested on Windows and supports 27 languages for text-to-speech synthesis. While it supports many ODT features, some complex text layouts are not supported.
AccessODF is a tool that evaluates and repairs accessibility issues in LibreOffice/OpenOffice.org Writer documents. It identifies over 30 common errors and provides suggestions for fixing problems. The first version was released in November 2011 and checks documents for issues like missing image alt text, improper language identification, or tables created with tabs instead of proper coding. It also includes checks specific to creating accessible DAISY or Braille formats. The goal is to help users make documents more accessible for people with disabilities.
odt2braille is an open-source extension for LibreOffice Writer and OpenOffice.org Writer that allows the software to produce Braille documents. It converts standard office documents into Braille format files that can be printed on Braille embossers or exported to other Braille file types. The extension provides formatting and layout for both print and Braille output in a single file. It uses existing open-source libraries for Braille formatting and embosser communication. odt2braille enables authors to seamlessly create accessible documents for both sighted and visually impaired users.
1) The document discusses the development of a common media player for the Open University to address the problem of different sites using different player solutions with varying accessibility and user experiences.
2) An initial player was developed in 2011 based on Flowplayer but had design issues. A second version was then developed in 2012 based on MediaElement.js to be more compact and support fullscreen viewing.
3) The player is intended to be easy for content authors to use across different OU contexts like the VLE and OpenLearn. Accessibility testing and input is a priority in the development process.
Dr. Tanvi FOCP Unit-2 Session-1 PPT (Revised).pdfRahulSingh190790
This document outlines the agenda and objectives for a series of sessions on introducing Python programming. The sessions will cover Python features, environment setup, syntax, data types, operators, strings, and regular expressions. The goals are for students to understand why Python is useful, install Python correctly, configure their environment, and gain familiarity with Python's core concepts and fundamentals. Real-world uses of Python include web development, data science, machine learning, automation, and cross-platform software development.
[EclipseCon France 2017] Language Server Protocol in actionMickael Istria
The Language Server Protocol in a popular IDE-independent and Language-independent interface to provide and consume language edition services - such as code analysis, completion, hyperlinking... It basically lets the language providers implement the protocol as a server, and the IDEs consume the protocol as a client to have the IDEs presenting the language-specific data without having to know about the language.
This protocol already has multiple successful stories. In this talk we’ll demonstrate:
* How a C# language server can be used in Eclipse IDE (thanks to LSP4E) to provide rich C# edition capabilities
* How a Java language server implemented on top of JDT is integrated into VSCode to have VSCode supporting rich Java edition capabilities
* How you can easily write a language server in Java (with LSP4J) and plug it into Eclipse IDE (with LSP4E) and VSCode and demonstrate how easy it becomes to ship additional features for your language in all tools at once.
Presentation of lpOD (ODF automation platform) at FOSDEM 2010Itaapy
lpOD is a document automation platform : a high level API in different langages, to produce, consume or manipulate ODF documents, be it text, spreadsheets or presentations. This presentation by Jérôme Dumonteil took place at FOSDEM 2010.
Doxygen is a documentation generator for C/C++ and other languages that extracts documentation from source code comments to generate documentation files like HTML. It was created in 1997 and is free and open source. Doxygen supports many languages, is easy to update, runs smoothly, and stores documentation in source code comments.
A Technical Comparison: ISO/IEC 26300 vs Microsoft Office Open XML Alexandro Colorado
Two XML office file formats have been pressing upon our attention, the OASIS OpenDocument Format, recently standardized by ISO, and the Draft Ecma Office Open XML. This presentation will review history of each, the process that created them, and examine each format to compare and contrast how they deal with issues such extensibility, modularization, expressivity, performance, reuse of standards, programability, ease of use, and application/OS neutrality.
MWLUG 2011: The Never Ending Integration StoryJohn Head
This document outlines an agenda for a presentation on integrating Lotus Notes, Domino, and LotusLive applications with Microsoft Office, .NET, and Lotus Symphony. The presentation covers introductions, getting started with basic integration demos, advanced integration from the Notes client, other applications, and the web. It also discusses looking forward and taking questions. Integration history and tools are reviewed. Advanced demos include using the OpenNTF Contacts Experience template and document generation without a desktop app using OOXML, ODF and PDF standards.
The document summarizes updates to the Open Document Format (ODF) specification. ODF 1.2 was recently approved as an OASIS standard in September 2011. Key additions in ODF 1.2 include support for digital signatures, enhanced metadata, and the OpenFormula specification for spreadsheet functions. While progress has been made, full interoperability between implementations remains an issue, particularly for change tracking and signatures in spreadsheets. ODF plugfests help test interoperability between different software applications.
The Open Source Screen Reader SUE – Access for the Blind by means of Training...AEGIS-ACCESSIBLE Projects
The document discusses the SUE open source screen reader project. It aims to develop a free screen reader for Linux to support office tasks, and provide training materials for teachers and visually impaired students. SUE works with Ubuntu distributions and GNOME software. It supports applications like OpenOffice, Evolution and Firefox. Training materials are available in several languages to teach users how to operate SUE and accessibility software. Future work includes adapting SUE for new versions of Ubuntu and applications.
Gnumeric is a free, open-source spreadsheet program developed for the GNOME desktop environment. It can import/export a variety of file formats and has a native .gnm format. While it lacks some features of other programs, developers are working to improve accuracy and add features like pivot tables.
Lotus Symphony was an integrated software suite produced from 1984-1992 that included a spreadsheet, database, word processor and graphing functions. IBM later used the name for an OpenOffice-based office suite in 2007.
Google Docs allows online creation and collaboration on documents, spreadsheets and presentations through a web browser. Documents are automatically saved and version history is kept. It supports various proprietary and open formats.
The document discusses Office Open XML, the file format used in Microsoft Office 2007. It provides an overview of OOXML, including its structure as a zip file containing XML files for different content types like documents, spreadsheets, presentations. It also discusses OpenOffice.org's implementation of an OOXML importer through a native filter being developed jointly with Novell. The filter uses a fast SAX parser and works within OpenOffice.org's data model to handle the different OOXML document types.
The document discusses odt2braille, an open-source software that integrates Braille production into mainstream word processors like OpenOffice and LibreOffice. It does this by allowing documents to be authored once in the OpenDocument Format and then converted to Braille or other formats on demand using stylesheets. The odt2braille architecture utilizes Liblouisxml for Braille transcription and supports a wide range of Braille alphabets and languages. Future work may include expanded embosser support, more accurate translations, and availability on additional platforms.
Lotus Symphony has matured quite a bit the past year, but are you taking full...John Head
No matter your preference for OOXML, ODF, or PDF … the document standard requirements are going to become a fact of life for users of IBM Lotus Notes & IBM Lotus Domino in the next year. This sessoin will review the technical capabilities of all three formats and how they work with Lotus Software. We will check the format debate at the door and look at which format will provide you the functionality you need. We will then look at how you can generate all three documents from your applications using third-party tools and custom code. You will take home samples that allow you to export Lotus Notes data to OOXML, ODF, and PDF in LotusScript and Java – be prepared for a deep dive into code!
The document summarizes the final results and outcomes of the AEGIS project. It discusses:
1) How the final AEGIS solutions can be accessed on the project website, including descriptions, languages, and download links.
2) The development of the Open Accessibility Framework (OAF) which the solutions fall under, and a video explaining the six steps of the OAF.
3) The Open Accessibility Everywhere Group (OAEG) which maintains the solutions and clusters them according to the OAF, and includes an open source repository and standards references.
The newsletter provides updates on the VERITAS project, including information about pilots testing with beneficiaries and designers, upcoming events, and recently released deliverables. It discusses a workshop and special thematic session held at the 13th International Conference on Computers Helping People with Special Needs on virtual user models. It also announces the release of two new videos from the project and a discussion paper on standardization of virtual user models produced by the Virtual User Modelling and Simulations cluster.
The document summarizes identified synergies between the AEGIS project and other projects. It lists each project and potential synergies in areas such as personas, ontologies, user models, portals, pilots, development, integration, roadmaps, and standards. For each synergy, it identifies the relevant aspects and issues to be discussed further. The overall goal is to define specific actions and a roadmap to better fulfill synergies across projects.
The document discusses mobile apps being developed for the VIPI project to provide an accessible virtual portal and ICT training for people with disabilities. It describes apps for mobile social media on Android that will allow beneficiaries and content providers to access learning objects, articles, and search. It also outlines apps for educational games and basic ICT skills learning. The apps are being upgraded to be compatible with newer Android versions and devices, with a focus on improved accessibility and social capabilities.
The document discusses the VIPI curriculum which aims to provide basic ICT training for people with disabilities. It describes 3 tiers of modules covering computer basics, basic ICT skills, and higher basic skills. Each module contains learning objects on various computer and internet topics. The curriculum also incorporates assistive technologies and serious games developed by previous projects to improve skills. New games will be created over the next 6 months specifically targeting the ViPi stakeholders and focusing on basic ICT skills.
The document summarizes the findings of a survey conducted as part of the VIPI project. Over 200 stakeholders completed the survey, including people with disabilities, organizations, trainers, intermediaries, and policy makers. The survey found that people with disabilities prefer e-learning and virtual training methods but have less access to them. Respondents said virtual training could help address common problems with ICT and assistive technology training by making software free and self-paced. Trainers preferred teaching methods like presentations, tutorials and demonstrations that could be supported through a virtual portal. Most experts felt virtual ICT training would improve employment opportunities for people with disabilities.
The VIPI project aims to create an accessible online portal and learning environment to provide ICT training to people with disabilities. Run from 2011-2013 with EU funding, the project has partners in the UK, Belgium, Greece, Lithuania, and Cyprus. It seeks to address barriers people with disabilities face in accessing ICT training, such as a lack of suitable materials. The portal will provide learning objects, online courses, and social networking tools to help users develop digital skills and find employment opportunities using assistive technologies. Evaluation of ICT skills training needs has already begun across the partner countries.
This document summarizes a presentation given at the 2nd ViPi Workshop in Vilnius, Lithuania on semantic content management enhancements. The presentation describes how semantic tagging was applied to books in a bookstore to help the owner better assist customers in finding materials that matched their needs. It provides examples of how books were semantically tagged with properties like subject, and how this allowed the owner to locate books for customers based on their needs and preferences that were also stored semantically. The presentation then discusses how these concepts relate to utilizing semantic tagging in online repositories like ViPi to enhance searching and access to learning objects.
Gelijke kansen op informatie, toegankelijke documenten en communicatiekanalen...AEGIS-ACCESSIBLE Projects
Gelijke kansen op informatie, toegankelijke documenten
en communicatiekanalen (o.a. sociale media)
Presentatie op TOLBO symposium "Symposium toegankelijkheid van lokale besturen en overheidsdiensten voor personen met functiebeperkingen" - 20 maart 2012 in het Vlaams parlement.
1) The developer used tools from the AEGIS Open Accessibility Framework (OAF) like the Accessibility Advisor, LWUIT's accessible UI components, and the NetBeans IDE to design and develop an accessible catalog mobile app.
2) She tested the app using accessibility simulation and assistive technologies like screen readers.
3) The fictional app was then released to app stores, making catalog data accessible to users with disabilities.
The document describes how an accessibility framework called AEGIS Open Accessibility Framework (OAF) was used to build an accessible web-based calendar application. It follows a fictional developer, Clyde Channing, as he uses tools from the OAF like the Accessibility Advisor, ARIA specifications, and stock UI components to design, test, and release the calendar application. These tools helped ensure the application was accessible to users with disabilities. The presentation concludes by discussing next steps to further test the OAF tools with developers.
Project number: 224145
Project acronym: ACCESSIBLE
Project title: Accessibility Assessment Simulation Environment for New Applications Design and Development
Starting date: 1 September 2008
Duration: 42 Months
ACCESSIBLE is a targeted research project (STREP) within the ICT programme of FP7.
http://www.accessible-project.eu/
Project number: 224348
Project acronym: AEGIS
Project title: Open Accessibility Everywhere: Groundwork, Infrastructure, Standards
Starting date: 1 September 2008
Duration: 48 Months
AEGIS is an Integrated Project (IP) within the ICT programme of FP7
http://www.aegis-project.eu/
Project number: 247765
Project acronym: VERITAS
Project full title: Virtual and Augmented Environments and Realistic User Interactions To achieve Embedded Accessibility DesignS
Starting date: 1 January 2010
Duration: 48 Months
VERITAS is an Integrated Project (IP) within the 7th Framework Programme, Theme FP7-ICT-2009.7.2, Accessible and Assistive ICT
http://veritas-project.eu/
Project number: 247765
Project acronym: VERITAS
Project full title: Virtual and Augmented Environments and Realistic User Interactions To achieve Embedded Accessibility DesignS
Starting date: 1 January 2010
Duration: 48 Months
VERITAS is an Integrated Project (IP) within the 7th Framework Programme, Theme FP7-ICT-2009.7.2, Accessible and Assistive ICT
http://veritas-project.eu/
Project number: 247765
Project acronym: VERITAS
Project full title: Virtual and Augmented Environments and Realistic User Interactions To achieve Embedded Accessibility DesignS
Starting date: 1 January 2010
Duration: 48 Months
VERITAS is an Integrated Project (IP) within the 7th Framework Programme, Theme FP7-ICT-2009.7.2, Accessible and Assistive ICT
http://veritas-project.eu/
This document contains the proceedings from the 2nd International AEGIS Conference and Final Workshop held from November 28-30, 2011 in Brussels, Belgium. The conference covered a wide range of topics related to accessibility and included sessions on mobile applications, workshops, international research initiatives, developer needs, accessible content, desktop applications, user needs, and accessibility overall. Over 50 speakers presented on various topics such as mobile accessibility, web standards, assistive technologies, and universal design.
The document summarizes identified synergies between the AEGIS project and other projects. It lists each project and potential synergies in areas such as personas, ontologies, user models, portals, pilots, development, integration, roadmaps, and standards. For each synergy, it identifies the relevant aspects and issues to be discussed further. The overall goal is to define specific actions and a roadmap to better fulfill synergies across projects.
The VERITAS project aims to develop tools to support accessibility testing during the planning and development of various products and technologies. It will create virtual user models based on primitive tasks to simulate the experiences of different types of users. This will allow iterative testing and feedback without relying solely on real user testing. The project will develop multi-level simulation platforms and apply the tools to scenarios in automotive, smart home, workplace, entertainment, and healthcare domains. It seeks to address the current lack of accessibility support across different sectors and development stages.
2. The AEGIS Project
●
EC-funded project, Sep. 2008-Feb.2012
●
20+ partners, including Oracle (Sun),
AOL, RIM, Vodafone Foundation, RNIB,
K.U.Leuven, …
●
Access to desktop, RIAs and mobile
applications
●
Many open-source “prototypes” /
products
●
http://www.aegis-project.eu/
FOSDEM, Brussels, Belgium, 5-6 February 2011
3. odt2daisy:
Generating DAISY Books from
OpenOffice.org & LibreOffice
Christophe Strobbe
K.U.Leuven, Belgium
christophe.strobbe@esat.kuleuven.be
FOSDEM, Brussels, Belgium, 5-6 February 2011
4. Digital Talking Books
●
For persons with “print disabilities”
●
Text + audio (synthetic or human voice)
●
Highlighting synchronised with audio
●
DAISY – ANSI/NISO Z39/86
●
Production: typically
●
by specialised production centres
●
for blind & visually impaired users
●
i.e. not by users (in 2007)
FOSDEM, Brussels, Belgium, 5-6 February 2011
5. Objectives
Enable end-users to produce DAISY
●
In most European languages
●
In a free and open-source office suite
●
Support:
●
DAISY 3 (with or without audio)
●
DAISY 2.02 (for older players)
●
Multilingual content
●
Mathematical Markup Language
FOSDEM, Brussels, Belgium, 5-6 February 2011
6. Methodology
●
Build OOo / LibO extension
●
Odt2dtbook by Vincent Spiewak
available in 2008
●
Functionality available as extension and
as reusable JAR (Java Archive)
●
Add:
– DAISY 3 audio, DAISY 2.02
– comprehensive set of test documents
(regression testing)
– Support for multilingual content on
Windows
FOSDEM, Brussels, Belgium, 5-6 February 2011
7. odt2daisy Components (1)
●
Java Open Document Library (JODL)
●
For ODT / XML preprocessing
●
odt2daisy library
●
Converts ODT to DAISY XML (XSLT)
●
Validates output
●
Reusable Java library
●
Command line interface
FOSDEM, Brussels, Belgium, 5-6 February 2011
8. odt2daisy Components (2)
●
odt2daisy extension
●
Wrapper for other components:
●
Uses OpenOffice.org UNO API
●
Uses odt2daisy library
●
Uses DAISY Pipeline Lite (speech
synthesis)
●
Includes templates
●
Templates with custom styles for DAISY
production
FOSDEM, Brussels, Belgium, 5-6 February 2011
9. Results (1)
●
odt2daisy released November 2009
●
Tutorials in various formats (text,
DAISY, video)
●
Developer documentation
●
Test files for regression testing
●
TTS in 27 languages where eSpeak is
available (Linux, Windows)
●
Compatible with OOo Writer 3.0 or
higher and with LibOWriter
FOSDEM, Brussels, Belgium, 5-6 February 2011
10. Results (2)
●
Support for ODT features
●
Heading, List, Table, Images, Captions,
Notes, Foot/Rear notes, Math, TOC,
Section, Frame, Bookmark,
Metadata, ...
●
Page numbering (1,i,I,a,A; advanced)
●
Front / body / rear matter
●
“Complex text layout” and East-Asian
languages not supported
FOSDEM, Brussels, Belgium, 5-6 February 2011
11. Results (3)
●
Release 2.1 in April 2010
●
Localisation in French, Dutch, Spanish
and Hungarian
●
Compatible with OpenOffice.org 3.2
●
Has been tested in first ÆGIS pilot
phase
●
Not yet compatible with 64-bit OSs
●
Integrated into DAISY Pipeline by
DAISY Consortium & Dedicon’s altText
FOSDEM, Brussels, Belgium, 5-6 February 2011
12. Future Plans
●
Support more ODT features
●
Some were hard to parse (e.g.
multilingual text; “Asian” languages)
●
TTS quality:
●
Users want more control over TTS
output (DAISY Pipeline Lite)
●
TTS as internet service/in cloud?
●
Fix bugs (numbered lists, math, image
captions & long description, ...)
FOSDEM, Brussels, Belgium, 5-6 February 2011
13. Installing odt2daisy
●
Download odt2daisy from
http://odt2daisy.sf.net/
●
In OOo or LibO Writer go to Tools ->
Extension Manager... -> Add...
to install it
FOSDEM, Brussels, Belgium, 5-6 February 2011
14. Export to DAISY: 1
●
Choose “Export as Full DAISY...” in File
menu
●
Choose file name and location in “Save
as” dialogue
●
Set metadata and options in odt2daisy
dialog
FOSDEM, Brussels, Belgium, 5-6 February 2011
15. Export to DAISY: 2
●
Some metadata are
copied from source
●
“alternate level
markup”: when > 6
levels of headings
●
CSS: for viewing XML
in browser
●
Some automatic fix
routines
FOSDEM, Brussels, Belgium, 5-6 February 2011
16. Export to DAISY: 3
●
odt2daisy converts ODT to DAISY XML
●
odt2daisy calls DAISY Pipeline Lite for
text-to-speech
FOSDEM, Brussels, Belgium, 5-6 February 2011
17. Export to DAISY: 4
●
DAISY Pipeline also performs validation,
e.g. images must be JPG or PNG (or
SVG)
FOSDEM, Brussels, Belgium, 5-6 February 2011
19. Motivation & Problem Area (1)
●
Braille
●
faces competition from TTS and digital
talking books
●
important for functional literacy
●
only reading method for deafblind
persons
FOSDEM, Brussels, Belgium, 5-6 February 2011
20. Motivation & Problem Area (2)
●
Braille production: current methods:
●
RoboBraille: e-mail based Braille translation
agent
●
AutoBraille & NorBraille: multi-volume Braille
books based on DAISY
●
Dots: open-source Braille transcriber for
GNOME (relies on liblouisxml)
●
Tiger Software Suite (TSS), Braille Maker,
WinBraille: embossing from MS Word and
other Microsoft applications
FOSDEM, Brussels, Belgium, 5-6 February 2011
21. Objectives
Enable end-users to produce Braille
●
In a free, open-source and cross-
platform office suite
=> OpenOffice.org / LibreOffice as
Braille authoring environment
●
Reduce or eliminate the need for editing
Braille codes after export
●
Emboss directly or just export
FOSDEM, Brussels, Belgium, 5-6 February 2011
22. Methodology
●
Build OpenOffice.org extension
●
Reuse existing tools:
●
liblouisxml: open-source library for
Braille transcription of XML docs
●
liblouis: Braille translation engine
●
pef2text (DAISY Pipeline): converts
Portable Embosser Format to generic or
embosser-specific format
●
library from odt2daisy
FOSDEM, Brussels, Belgium, 5-6 February 2011
24. Results (1)
Alpha 0.03 released 2 December 2010:
●
OpenDocument Text (ODT) can be
embossed on small list of embossers
(Interpoint, Index Braille, Braillo)
●
Export to “Braille Formatted files”
(.brf; .bra)
●
Export to Portable Embosser Format
(PEF): embosser-independent; uses
XML and Unicode
FOSDEM, Brussels, Belgium, 5-6 February 2011
25. Results (2)
●
Braille settings stored as metadata in
ODT
●
Braille support for ± 30 languages,
mainly through liblouis
●
UI localised in
●
English, Dutch, French, German,
Spanish, Portuguese,...
●
Currently only on Windows
FOSDEM, Brussels, Belgium, 5-6 February 2011
26. odt2braille > liblouisxml (1)
odt2braille is more than a liblouis &
liblouisxml wrapper (1)
●
Provide easy configuration through GUI
●
Create typical OOo/LibO experience
●
Translate easy-to-understand settings
to complex configuration files for
liblouisxml
FOSDEM, Brussels, Belgium, 5-6 February 2011
27. odt2braille > liblouisxml (2)
odt2braille is more than a liblouis &
liblouisxml wrapper (2)
●
Convert ODT to intermediate XML
format:
●
Put captions after tables, move some style
info, add notes section, add title page
●
= for sequential processing by liblouis
●
(ODT is too complex to be handled by
liblouisxml alone)
FOSDEM, Brussels, Belgium, 5-6 February 2011
28. odt2braille > liblouisxml (3)
odt2braille is more than a liblouis &
liblouisxml wrapper (3)
●
Compensate for limitations of
liblouisxml
●
Volume management
●
Creation of notesections and preliminary
section containing title page, list of
special symbols, transriber’s notes page
and a table of contents
FOSDEM, Brussels, Belgium, 5-6 February 2011
29. odt2braille > liblouisxml (4)
odt2braille is more than a liblouis &
liblouisxml wrapper (4)
●
Store settings as metadata in ODT
document
●
Convert to PEF / various other output
formats
●
Provide output preview
●
Handle embossing
FOSDEM, Brussels, Belgium, 5-6 February 2011
30. Installing odt2braille
●
Download odt2braille from
http://odt2braille.sf.net/
●
In Writer go to Tools -> Extension
Manager... -> Add... to install it
●
New items in File menu
FOSDEM, Brussels, Belgium, 5-6 February 2011
31. Braille Settings
●
File -> Braille
Settings
●
odt2braille
analyses
document &
suggests
settings
●
User can
override settings
FOSDEM, Brussels, Belgium, 5-6 February 2011
32. Export as Braille: 1
●
File -> Export as
Braille...
●
Choose PEF (Portable
Embosser Format), BRF
(Braille Formatted) or
BRA (Spain)
●
Customise...
FOSDEM, Brussels, Belgium, 5-6 February 2011
33. Export as Braille: 2
●
odt2braille performs a few basic
accessibility checks
●
A full accessibility checker is being
developed by K.U.Leuven (AEGIS)
FOSDEM, Brussels, Belgium, 5-6 February 2011
34. Emboss
●
File -> Emboss...
●
Few embossers
currently supported
●
Output can be
customised
FOSDEM, Brussels, Belgium, 5-6 February 2011
35. Future Plans
●
Support for larger set of embossers
●
Availability on non-Windows platforms
●
Extension to check accessibility in
OpenOffice.org / LibreOffice Writer
●
Display errors & warnings in task panel
(OOo / LibO 3.3+)
●
Description & hints for repair
●
Repair button when possible
FOSDEM, Brussels, Belgium, 5-6 February 2011