microsoft

[MiaKalish@LFP]

I don't know how we would do this since the KWERTY keyboard has the fixed
keys, and everyone knows how to type on it.

Voice recognition is not really sophisticated although there has been a lot
of time and technology logged into it.

I thought about this a lot when I built the template for Athapascan, and I
couldn't think of a better solution than the soft toolbar.

This problem really has several dimensions. First is the font itself, and
making it portable and interchangeable. The Second is the localization
issue, with the related application to generalized software packages. The
third is the hardware. How long has the QWERY keyboard been around? . . .
since 1868, (Cristopher Latham Sholes in 1868;
http://www.google.com/search?hl=en&q=QWERTY+keyboard+invention)

Is anyone submitting to the AIQ? I really think a bunch of us ought to write
about this. We have a lot of people talking about revitalization, but so
far, there is a lot a rhetoric. I think this is both because the
technological support is not there, and also because we aren't having a
public discussion about the processes, steps, and issues. I see a lot of
wonderful links provided by the tireless Phil, but I wonder how many of
these happen because someone at the university gets a grant. How many actual
TRIBES have the technology and expertise to design, develop and support
their own programs (which I think is Very Important).

People?

Mia

----- Original Message -----
From: "Keola Donaghy" <keola at LEOKI.UHH.HAWAII.EDU>
To: <ILAT at LISTSERV.ARIZONA.EDU>
Sent: Tuesday, November 16, 2004 11:14 AM
Subject: Re: microsoft


> Aloha Mia. We did hire the developer of Keyman several years ago to create
> 2 Hawaiian keyboard layouts (both using our custom 8-bit fonts and
> Unicode), and were able to purchase a world-wide license from him so that
> we could distribute it freely (for use with the Hawaiian keyboards only)
> from our website. Has worked OK, but it's still an extra step for our
> users that I'd love to be able to avoid some day.
>
> Keola
>
> Indigenous Languages and Technology <ILAT at LISTSERV.ARIZONA.EDU> writes:
> >I encountered this problem, but at least where I was looking at the time,
> >most of the programs did not support the scripting necessary to build the
> >internal keyboard. I am sure you have looked at Keyman, yes? $50 or so
> >for a
> >keyboard; I don't know what the customization charges are.
> >
> >How I do the exchange, since I do mostly graphics programs for learning
> >materials, is I create the text in Word, and then copy via clipboard into
> >the graphics programs.
> >
> >The place where the change needs to be made, by the way, is in the lowest
> >levels of the operating system, where the language and country codes are
> >set.
> >
> >To weigh in on localization, I think each place with an endangered
> >language
> >needs to have localization support! To say, Is it worth it? is to side
> >with
> >the monoliguists (English works for me! It should work for everyone. NOT)
>
>
> ========================================================================
> Keola Donaghy
> Assistant Professor of Hawaiian Studies
> Ka Haka 'Ula O Ke'elikolani             keola at leoki.uhh.hawaii.edu
> University of Hawai'i at Hilo           http://www2.hawaii.edu/~donaghy/
> ========================================================================
>