[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:	DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:	See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:	STAR::VATNE

Created:	Mon Oct 30 1989
Last Modified:	Mon Dec 31 1990
Last Successful Update:	Fri Jun 06 1997
Number of topics:	3726
Total number of notes:	19516

1402.0. "Problem to get the � character" by EVTIS2::TISSERAND (Jean-Marc TISSERAND TSC FRANCE) Fri Sep 08 1989 11:31

    I have a problem to get the � character.                                   
    
    By using the following compose sequence: <COMPOSE CHARACTER><SPACE BAR> oe ,
    it works fine in a decterm window, but nothing appears in an EVE 
    DECWINDOW neither in Calendar (just a beep).
    
    However, compose_character a e works fine and I get � everywhere.
                                                                               
    How can I get it ?
    
    Thanks for your help.
    
    Jean-Marc.

T.R	Title	User	Personal Name	Date	Lines
1402.1	Sounds like ISO Latin 1	HANNAH::MESSENGER	Bob Messenger	`Fri Sep 08 1989 12:41`	17
	Re: .0 It sounds like EVE and Calendar are using ISO Latin 1 as their 8 bit character set, rather than DEC Multinational. DECterm allows you to use either character set. ISO Latin 1 doesn't have OE or oe characters; the character at those positions in the ISO Latin 1 character set (codes 215 and 247) are the multiplication sign and division signs. I see the last two characters in this sentence as multiplcation and division, while you'll see them (in DECterm) as OE and oe: �. DECterm has to subtitute keysyms to trick XLookupString into supporting DEC Multinational compose sequences, so I'm not surprised that EVE and Calendar don't support DEC Multinational. (EVE is based on TPU, which uses the DECterm widget for output but does its own input processing.) -- Bob
1402.2		KONING::KONING	NI1D @FN42eq	`Fri Sep 08 1989 13:06`	8
	Complain to the French national standards organization; they are the one that convinced ISO that "nobody needs oe, it should be removed from Latin-1". I suppose we'll get it back when the Universal character set is implemented, N years from now... paul
1402.3	Not an EVE/Calendar specific problem	CASEE::CLEOVOULOU	Marios Cleovoulou	`Fri Sep 08 1989 13:19`	10
	I think you'll find that it's more that just EVE and Calendar that don't accept oe -- Calendar, like _almost_ every other DW application, uses the DECwindows Toolkit standard SText widget for textual input. It's the SText widget that doesn't accept oe. Regards, Marios
1402.4		PSW::WINALSKI	Careful with that VAX, Eugene	`Fri Sep 08 1989 14:16`	6
	Also DECwindows NOTES. The title to this topic shows up as "Problem to get the <division sign> character." It took me a while to figure out what the note was talking about. --PSW
1402.5	I am baffled too!	YUPPY::CONNOLLY		`Mon Sep 11 1989 13:56`	5
	Well i seem to get this character (A large question mark) all over the place in notes (i use a VT340) and i still dont know why!!! Gerry
1402.6		LESLIE::LESLIE	Andy �� Leslie. Fat was then....	`Mon Sep 11 1989 17:05`	2
	Do a SET TERM/EIGHT.
1402.7	It is ISO Latin-1, that's the way it is supposed to work	HANNAH::LASKO	There are no temporary workarounds	`Tue Sep 19 1989 12:40`	7
	Re: .1 and the general topic DECwindows applications are supposed to support only ISO Latin-1. DECterm is the exception because that application is deliberately backwards compatible with traditional character cell terminals which supported the DEC Multinational Character Set.