James wrote:
Are you capable of looking at code and finding issues?
Yes. I don't have the time though. [I'm coding something else for OOo --- though I won't be the least bit surpised if it gets rejected by Sun, because it doesn't fit their roadmap. (It is something that should have been included in OOo 1.0.0, if not earlier.) ]
the 'smoketest' routines and you will see what I mean (not to knock the
The smoke test routines have the virtue of being readable --- unlike some of the code that Sun has provided to OOo.
Section 508 is just one small part. The government (US that is) could not sue us, we have no assets. However, this keeps away those users with less
It isn't a question of being sued by the government.It is a question of whether or not the PHB will check "yes"or "no" when it comes to section508 compliance. Granted,MSO fails Section 508 compliance as badly as OOo does, the difference is that the PHB can hire somebody at $500 an hour to make Word and most of Excel Section 508 compliant. AFAIK, nobody is offering that service for OOo.
presents serious hurdles to those who have ability issues.
A11Y, l10n, and i18n have to be included in the initial design of the program, for them to work correctly. Retrofitting them usually requires a complete code rewrite. With the ODF Toolkit, creating an a11y office suite from scratch should be much easier. [If the one for blind people is coded correctly, the biggest user base will consist of PHBs. ]
JAWS does not
Freedom Scientific is beholden to themselves,and their government contracts.
I would like to see some of the speach to text programs be worked
into OpenOffice.org. That is on the drawing board. [Basically it depends upon how soon Sun releases the Java Speech to text engine that they are working on. ] The big issue with speech to text engines is that they are either proprietary,or else issued under licence that precludes their usage in OOo, and similar projects. I _think_ that Sun's Java Speech to Text engine is the only one that is available under a licnece that is compatible with that used by OOo.
.Sure this would increase its size, but maybe these could be
additional packages, much like language pack.
It appears that we have hit upon two separate issues: 1. The lack of concentrated triage for newly opened issues. 2. The lack of a11y support in OpenOffice.org.
There are a couple of other groups of issues that are significant: * i18n / l10n issues; [ boustrophedoun writing systems, Support for Unicode base 1 thru 15, etc.They usually require the underlying code to be rewritten.] * multilingual document creation issues; [These generally are due to user ignorance.] * Document processing issues. (Why can't OOO have "feature that is in Publisher, Quark, Adobe" )
Can you assist with either of these issues?
I'm coding something else for OOo --- which is related to one of those issues. [ Something that other office suites don't have the ability to do. It will require some customization on the part of the user to use, but the payoff for them is an increase in productivity by several orders of magnitude. ] xan jonathon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
