[liblouis-liblouisxml] Re: Back-translation of French

  • From: "Michel such" <michel.such@xxxxxxx>
  • To: <liblouis-liblouisxml@xxxxxxxxxxxxx>
  • Date: Wed, 18 Mar 2009 07:20:13 +0100

Hi,

I also noticed backtranslations problems, but I only tested it from grade 2.
So I need to investigate a bit to try to figure out the problems.

  ----- Original Message ----- 
  From: John J. Boyer 
  To: liblouis-liblouisxml@xxxxxxxxxxxxx 
  Sent: Wednesday, March 18, 2009 12:01 AM
  Subject: [liblouis-liblouisxml] Re: Back-translation of French


  Jonathan,

  I want to give Michel Such a chance to reply before I comment 
  extensively. You have a good point that there may be a problem with 
  back-translation when the user-defined classes are used. The code of 
  lou_backTranslateString.c may need some adjustment.

  Please describe your project a little further.

  Thanks,
  John

  On Wed, Mar 18, 2009 at 11:03:48AM +1300, Jonathan Sharp wrote:
  > Hi John,
  > 
  >  
  > 
  > I'm evaluating the new French tables for possible use in a project that
  > needs both forward and back translation.  I've found some problems with
  > back-translation and these are also present in the older French tables, so
  > are not a result of the recent changes.  Here's an example:
  > 
  >  
  > 
  > If I forward-translate "pierre" I get "pi(re", which is correct.  Now if I
  > back-translate "pi(re", I get "pi(re" still - the left-parenthesis is not
  > translated back into "er".
  > 
  > If the "er" occurs at the end of a word, such as "marcher", then it is
  > back-translated correctly. However in this case the "ar" contraction is not
  > back-translated while the "ch" contraction is back-translated correctly.
  > 
  >  
  > 
  > Looking at the braille table there are two entries for "er", one for the
  > middle of a word:
  > 
  >  
  > 
  > before con midword er 236
  > 
  >  
  > 
  > and one for the end of a word:
  > 
  >  
  > 
  > endword er 236
  > 
  >  
  > 
  > It seems the endword entry is back-translating correctly while the midword
  > one is not.
  > 
  >  
  > 
  > The "ar" entries are:
  > 
  >  
  > 
  > before con always ar 4
  > 
  > endword ar 4
  > 
  >  
  > 
  > whereas "ch", which works only has one entry:
  > 
  >  
  > 
  > always ch 12356
  > 
  >  
  > 
  > Trying some of the other entries, I wonder if the problem occurs when the
  > user-defined character classes, con, voy, etc. are used?
  > 
  >  
  > 
  > Jonathan
  > 
  >  
  > 
  >  
  > 
  >  
  > 

  -- 
  My websites:
  GodTouches Digital Ministry, Inc. http://www.abilitiessoft.com/godtouches
  Abilitiessoft, Inc. http://www.abilitiessoft.com
  Location: Madison, WI, USA

  For a description of the software and to download it go to
  http://www.jjb-software.com

Other related posts: