|
From: <tim...@en...> - 2006-01-17 16:39:49
|
Thanks for your detailed explanations ! I don't know why, but I must have forgotten ignore_enhanced_text somewhen after pasting the code from another terminal... It is working now, and my next patch will include the fix. Best regards, Timoth=E9e Ethan Merritt wrote: >On Friday 13 January 2006 06:09 am, Timoth=E9e Lecomte wrote: > =20 > >>Ethan reported that the enhanced text mode remains on when you run >>"load 'all.dem' ". >> =20 >> > > =20 > >>As it seems to be considered as a problem, I propose to add "set >>termoption noenhanced" at the end of the demo file >>'enhancedtext.dem'. >> =20 >> > >No, sorry. I have explained the problem badly. > >The point is that even if the terminal is in enhanced text mode, >there are times when the enhanced text processing is not wanted. >For instance, it is almost always a bad idea to treat underscores in >file names as indicating a subscript. For this reason there is a=20 >core routine ignore_enhanced(TRUE) that temporarily turns off >enhanced text processing. ignore_enhanced(FALSE) turns is back >on again. The routine is implemented by providing a flag variable >available to the terminal drivers: > TBOOLEAN ignore_enhanced_text; > >As best as I can make out, the wxWidgets terminal is not checking >this flag. Therefore if the terminal is in enhanced text mode, some >strings are treated this way when they should not be. > >Example: > set termoption enhanced > load 'histograms.dem' > >In the key there are entries for "Soviet_Union" and "United_Kingdom". >Note the underscores. It is not intended that these be typeset as >subscripts. The x11, post, and other terminals correctly render these >text strings to contain the underscore. The wx terminal shows instead >a subscripted next character.=20 > > =20 > |