minus or 8-0 should be defined as punctuation. Asterisk or "*" should be defined as sign. In general, a character should be defined according to how it is most frequently used. Note that if your tables are working in forward translation and you aren't concerned about back-translation you don't have to worry much right now. However there could be problems in unusual situations where math and literary text occur together. Only simple math symbols like = and + should be defined in tables intended primarily for literary material. Real math requires tables like nemeth.ctb and liblouisxml. John On Thu, Jan 22, 2009 at 11:42:46AM +0100, Michel Such wrote: > Ok for this, > > I am a bit confused for some rules. > > For example, there are some characters (minus character) that can be > considered as sign or math. > > May I define them in both rules or should I choose one of them? > > > Michel Such > ----- Original Message ----- > From: "John J. Boyer" <johnjboyer@xxxxxxxxxxxxx> > To: <liblouis-liblouisxml@xxxxxxxxxxxxx> > Sent: Thursday, January 22, 2009 11:42 AM > Subject: [liblouis-liblouisxml] Re: Questions about fr-bfu-comp8.utb > > > >michel, > > > >Some of the other problems may be a matter of personal preference. For > >example, in some of the lines there is a wide space between the rule and > >the comments. This can make it difficult to read these lines on a > >braille display. Also, the comment character # is not usually necessary > >between a rule and a comment, since the compiler takes only what it > >needs for the rule and ignores anything else on the line. An exception > >is the replace rule, where the second operand is optional. > > > >More serious is that many characters above hex 80 appear to be defined > >by > >both > >uplow rules and sign rules. This may confuse the forward translator and > >will almost certainly cause trouble in back-translation, because the > >same character is defined as both a letter and a sign. I did not check > >this in detail. I'm thinking of having the compiler print warning > >messages in such cases. This would be controlled by a bit in the mode > >parameter. > > > >John > > > >On Thu, Jan 22, 2009 at 08:14:27AM +0100, Michel such wrote: > >> > >>John, > >> > >>You wrote: > >> > >><I see other problems caused by copying pieces from <early tables, but > >><these are the ones I felt most important to call to the <attention of > >>the > >>list. Many of the early tables were made up before we really knew what > >>we were doing. > >> > >> > >>Since I am working on the tables, can you tell me a bit more on the other > >>problems you found? > >> > >>Sorry, Michel, I don't mean to pick on you. > >> > >>John > >> > >>-- > >>My websites: > >>http://www.godtouches.org > >>http://www.jjb-software.com > >>Location: Madison, WI, USA > >> > >>For a description of the software and to download it go to > >>http://www.jjb-software.com > > > >-- > >My websites: > >http://www.godtouches.org > >http://www.jjb-software.com > >Location: Madison, WI, USA > > > >For a description of the software and to download it go to > >http://www.jjb-software.com > > > > > > > For a description of the software and to download it go to > http://www.jjb-software.com -- My websites: http://www.godtouches.org http://www.jjb-software.com Location: Madison, WI, USA For a description of the software and to download it go to http://www.jjb-software.com