[liblouis-liblouisxml] Re: Issue with emphasis
- From: "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx>
- To: liblouis-liblouisxml@xxxxxxxxxxxxx
- Date: Thu, 20 Nov 2014 11:44:04 -0600
Well, you never know. Oddities crop unexpectedly. That is why they are
oddities. Processing after translation will probably work, but just the
Braille output probably isn't enough. Indexing could be used to get a
look at the original text. Everything should be done using the widechar
type. It may contain virtual dots, which are convenient for resolving
some problems. Unicode conversion, if desired, is done just before
returning to the calling program.
John
On Thu, Nov 20, 2014 at 04:45:44PM +0000, Keith Creasy wrote:
> I don't suppose you know of any examples where emphasis causes oddities when
> applied to text that is already braille? It sure would be nice if we could
> seperate applying special symbols (emphasis, start/end transcribers notes,
> etc.) from the translation.
>
> If it truly can't work then it would be good to understand that and why up
> front.
>
>
>
>
> -----Original Message-----
> From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
> [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of John J. Boyer
> Sent: Thursday, November 20, 2014 11:24 AM
> To: liblouis-liblouisxml@xxxxxxxxxxxxx
> Subject: [liblouis-liblouisxml] Re: Issue with emphasis
>
> multipass opcodes are executed to fix oddities that occur in translation,
> including emphasis.
>
> John
>
> On Thu, Nov 20, 2014 at 03:57:15PM +0000, Michael Whapples wrote:
> > It would be useful to know why pass2, pass3 and pass4 are done after
> > applying emphasis markers and if it is required. This is the sort of
> > thing I need to know if to make a suitably informed decision.
> >
> > Michael Whapples
> > On 20/11/2014 15:02, Bert Frees wrote:
> > >Michael Whapples writes:
> > >
> > >>I think this is sort of what I was meaning by an external option.
> > >>Well may be I was thinking it could potentially go further or it
> > >>could be as you describe.
> > >>
> > >>May be it could be C may be it could be another language, if it is
> > >>not mixed in then this does not matter too much, and whoever writes
> > >>it could use which they feel is most appropriate. "Appropriate"
> > >>including ensuring that it is usable by those who need access to the
> > >>functionality, so realistically it probably would be a choice
> > >>between C,
> > >>C++ or other language which can be used from C and has no large
> > >>dependencies.
> > >Important consideration is that the liblouis table, which should
> > >contain all the information needed to perform the translation, that
> > >means including emphasis markers, should only need to be parsed once.
> > >
> > >>May be it could be called near the end of the liblouis translate
> > >>function, then consumers of liblouis need not deal with additional
> > >>function calls and that complexity.
> > >Absolutely! We definitely need to avoid introducing additional API
> > >calls, we're talking about implementation details here and they
> > >should be hidden from the user.
> > >
> > >I'm not so sure this can just be a post-processing function though in
> > >the sense that it would be called near the end of the translate
> > >function. The way it works now I think is that pass2, pass3 and pass4
> > >are applied *after* emphasis markers have been added. Not sure if
> > >this is really a required feature, but something to keep in mind.
> > >
> > >>If it is C or C++ may be it could be statically linked to liblouis
> > >>and then no additional dependencies are to be handled.
> > >>
> > >>I think I am getting more convinced that it might be the quickest
> > >>option to implement.
> > >>
> > >>The only bit I cannot quite work out is whether the Braille string
> > >>and typeforms would be enough to apply the emphasis indicators or
> > >>whether one needs to have access to the original text.
> > >For a description of the software, to download it and links to
> > >project pages go to http://www.abilitiessoft.com
> >
> > For a description of the software, to download it and links to project
> > pages go to http://www.abilitiessoft.com
>
> --
> John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc.
> http://www.abilitiessoft.com
> Madison, Wisconsin USA
> Developing software for people with disabilities
>
> For a description of the software, to download it and links to project pages
> go to http://www.abilitiessoft.com
> For a description of the software, to download it and links to
> project pages go to http://www.abilitiessoft.com
--
John J. Boyer; President, Chief Software Developer
Abilitiessoft, Inc.
http://www.abilitiessoft.com
Madison, Wisconsin USA
Developing software for people with disabilities
For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com
Other related posts:
