View source for Transducers as flag diacritics and their topology learning

== Original Conversation with Jimmy O'Regan ==

  
  * [16: 04] <jimregan> Jacob and I designed an alternative to flag
  diacritics on the back of some paper plates last year
  * [16:04]  <jimregan> using a second transducer
  * [16:04]  <jimregan> (the original motivation behind flag diacritics -
  which are an ugly hack - was to avoid using a second transducer)
  * [16:05]  <jimregan> we use a fairly large number of transducers, in
  almost every phase of the translation pipeline
  * [16:05]  <jimregan> so we thought it wouldn't be unreasonable to have
  a second transducer to use in state pruning, rather than just
  balancing special symbols
  * [16:07]  <jimregan> the second transducer would basically take the
  same form as translation rules in apertium-transfer, but with the
  ability to fully or partially lexicalise (possibly based on a subset
  of regexes)
  * [16:07]  <jimregan> if the initial analysis involves a continuation,
  pass it to the second for validation
  * [16:07]  <jmcejuela> aha
  * [16:07]  <jimregan> prune it if it doesn't match
  * [16:08]  <jimregan> take the symbols of the second transduction for
  output if it does
  * [16:08]  <jimregan> Jacob was pretty pationate about implementing it
  himself, but I think he'd be interested in mentoring it
  * [16:10]  <jimregan> I just remembered how to summarise it: two level
  morphology as cascading transducers
  * [16:11]  <jimregan> but, as it's cascading, two level could
  potentially be made n-level


  [[Category:Flag diacritics]]