ports/78234: x11/eterm invalids compose character definition

[Frank Altpeter]

>Number:         78234
>Category:       ports
>Synopsis:       x11/eterm invalids compose character definition
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Mar 01 10:20:04 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Frank Altpeter
>Release:        FreeBSD 5.3-RELEASE-p5 i386
>Organization:
>Environment:
System: FreeBSD pegasus.default.local 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #28: Fri Feb 11 17:26:41 CET 2005 root at pegasus.default.local:/usr/obj/usr/src/sys/kernconf.pegasus i386


	
>Description:
        After upgrading the port x11/eterm to the current 0.9.3
        revision, a previously working compose character definition
        doesn't work anymore.
        Doing a downgrade to 0.9.2 brings back the feature, so in my
        understanding this proves to be a problem within Eterm.
        
	
>How-To-Repeat:
        # Define RIGHT_ALT as compose character
        echo 'keycode 113 = Multi_key' >$HOME/.xmodmap
        xmodmap $HOME/.xmodmap
        # Start a new Eterm here
        # Press RIGHT_ALT + u + " and you get u" instead of ü
>Fix:

        Downgrade to version 0.9.2 - I tried to contact the
        "developers" through the recommended way of speaking in the IRC
        channel, but nothing happened. Contacted maintainer per email,
        awaiting reply. I suggest either marking the port as BROKEN or
        revert the port to 0.9.2 until this gets fixed, since i don't
        know if there are more things broken in the 0.9.3 release, but
        if someone does rely on compose keys for typing special
        characters, this is quite bad.

	


>Release-Note:
>Audit-Trail:
>Unformatted: