Hi:
Under the docs/doc-set directory, you will find some internals.{pdf,html} files
that provide an overall description of the internals. This document is a
little out of date, but the high level ideas are still much the same.
Also, under src/orca/acss.py, you will find a definition for an ACSS (Aural
CSS) class, which is used throughout Orca for speech.
Hope this helps,
Will
On Jan 24, 2010, at 6:47 PM, Michael Pozhidaev wrote:
> Good day, everyone!
>
> May I ask few questions regarding Orca internal design? I am
> interesting AT-SPI provided data processing chain until it
> translations to speech processing software like speech servers or
> anything else.
>
> The problem I am thinking about is to mark speech output with
> semantics blocks like hyperlinks, headings, etc, to process them
> inspeech server. Marks can be in terms of oral css as it was published
> at:
>
> http://www.w3.org/tr/css2/aural.html
>
> Probably such translations is not a speech processor concern, yes, it
> is clear, but, in any case, how likely can this happen?
>
> Please, in few words, describe data life cycle and, if it would not be
> so disturbing, refer to code snippets in orca sources to let me read
> more about it. :)
>
> Great thanks!
>
> --
> Michael Pozhidaev. Tomsk, Russia. E-mail: [email protected]
> Info: http://www.marigostra.ru/
>
> _______________________________________________
> Gnome-accessibility-devel mailing list
> [email protected]
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
_______________________________________________
Gnome-accessibility-devel mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
