× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. LINUX5250
  3. December 2004

Re: xt5250, x5250, fonts

Scott Klement wrote:

When and if you get this working, there'll always be the chance for more
problems when you change fonts, upgrade X, or upgrade Fedora.


I use Fedora therefore I expect things to break ;)

IMHO, the best solution is to stop using this character.  Use the dollar
sign... for fifty cents, use $0.50

I have no choice in this matter. The symbol is used to mark custom code so as not to be confused with tasks sent by our software provider.

<snip>I'll check that part later</snip>

For keyboard mapping, you'll need to change key.c to return the ASCII code
( NOT THE EBCDIC CODE! ) so that when lib5250 maps it from ASCII to
EBCDIC, it'll translate to the right thing for the iSeries to understand.

For the sake of testing, you should be able to simply "return 162" but of
course, if you change the mapping in transmaps, you need to use whichever
character you changed it to.

Interesting... I changed my XK_bracketleft to return 162 and still got a bracket. Questioning my knowledge level, I changed my (working) XK_Control_L to return 162 and got the cent symbol. That must mean the bracket is not a bracket. I'll either have to map another key or figure out what key that is. (xev said it was bracketleft and confirmed the same code that was in X11/keysymdef.h)

Thanks for the tips!

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.