9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: LiteStar numnums <litestar@gmail.com>
To: andrey mirtchovski <mirtchovski@gmail.com>
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] OT: Bulgarian Input over Drawterm?
Date: Thu,  2 Jun 2005 03:48:18 -0400	[thread overview]
Message-ID: <283f5df1050602004865193242@mail.gmail.com> (raw)
In-Reply-To: <14ec7b18050602002379a47f8@mail.gmail.com>

Hello (Здраветe и Добро утро) Andrey,
 Thanks for the information; this at least stops me from searching for
reasons why the setup on my wife's laptop is 'broken'. I'll setup
another machine to see if it works from OpenBSD's drawterm (most
probably will); should have a better workstation to server ratio
anyway.
I'll grab the sources from your site, and play around with the input
here too, since it should work on Windblows (although I am rather
ignorant of Windows' workings on a development level; damn you Unix &
VMS for stealing my programing training!). I'll shoot you off another
email after this one about configuring X with Cyrillics.
Наздраве,
 -- Stefan
> Hi Stefan,
> 
> I'm able to type Cyrillic in drawterm and all the drawterm binaries
> (and source) available from ucalgary have this ability, however this
> is restricted only to X-windows and MacOSX. Drawterm for windows will,
> as far as I know, not allow you to input extended ascii or unicode.
> 
> It's unfortunate that I have no suitable windows development
> environment and am not familiar with windows' input codes and I'm of
> very little help with this one.
>
> Others on this list may help answering how difficult it would be to
> "port" /sys/src/9/port/devkbmap.c to drawterm, which would give you
> the ability to switch between keyboard layouts within drawterm, as it
> is done in native Plan 9 (and yes, there is a bulgarian phonetic
> layout there). I may look at that tomorrow, but indeed there's no
> promise of any actual results :)
> 
> I know this doesn't help much, but if you get your hands on an X
> terminal I can guide you through configuring it for Cyrillic input,
> which drawterm will then accept gladly (it knows about X's keymaps).
> Just send me an email.
> 
> Cheers (Наздраве): Andrey
> 


-- 
In possibility the eternal, rightly understood, continually lays out
only a small piece at a time
In possibility the eternal is continually near enough to be at hand
and yet far enough away to keep man advancing towards the
eternal, on the way, in forward movement. In this way the ternal lures
and draws a person, in the possible, from craddle to grave
if he just chooses to hope
   <<Soren Kierkegaard>>

  reply	other threads:[~2005-06-02  7:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02  6:59 LiteStar numnums
2005-06-02  7:23 ` andrey mirtchovski
2005-06-02  7:48   ` LiteStar numnums [this message]
2005-06-02 14:15   ` Sergey Reva
2005-06-02 14:24     ` andrey mirtchovski
2005-06-02 16:14       ` LiteStar numnums
2005-06-03  6:02         ` Sergey Reva
2005-06-03  6:18           ` andrey mirtchovski
2005-06-09 17:32             ` Sergey Reva
2005-06-02  7:46 YAMANASHI Takeshi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=283f5df1050602004865193242@mail.gmail.com \
    --to=litestar@gmail.com \
    --cc=9fans@cse.psu.edu \
    --cc=mirtchovski@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).