<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.6000.16481" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial color=#800080 size=2><STRONG>Justin:</STRONG></FONT></DIV>
<DIV><STRONG><FONT face=Arial color=#800080 size=2>Steve bears out in
confirmation of what you have just said. The glottal stop and enge
appeared on his PC in mostly foreign characters -- at least foreign to me.
His contnued suggestion of using adobe .pdf files with our fonts, whatever our
fonts that we use, being embedded in the .pdf file(s) and sent along with
the attached file(s) has been my past vehicle to send files when I wish them to
arrive and be viewed as I sent them. Further, from what you say, it seems
the goal of Unicode will be thwarted via the hope of simple conveyance over the
net, weather it is Email or Attachment of docs via EM.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial color=#800080 size=2></FONT></STRONG> </DIV>
<DIV><STRONG><FONT face=Arial color=#800080 size=2>He
states...</FONT></STRONG></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>Jimm,<BR>For the record, on my Eudora email client your characters look
like this: <FONT size=5><B>ˀηŋ<BR><BR></B></FONT>If everyone used the
same version of Windows and the same version of Word and the same version of
Windows (e)Mail then maybe you could just use the unicode fonts. But we
don't all use the same kinds of computers and software so that making sure what
you send/supply to someone else to view on his/her computer actually appears as
you want is a real trick. I'm presuming that you want your dictionary to
be used by as wide a range of people as possible, not just those who have a
specific kind of computer or software.<BR><BR>To make a long story short, using
Adobe Acrobat (.pdf) files is the answer to this fairly complex problem.
Even though Adobe Reader has gone through a number of revisions and updates in
the past 10 years, a chapter from your dictionary can still be viewed correctly
in .pdf format on what is now the somewhat obsolete version 5 of Adobe Reader, a
version that will work with 10 year old versions of Windows.<BR><BR>Using the
older Word format for your work-in-progress helps to insure that your
collaborators will not have to purchase the latest version of MS Office.
For example, if you want someone else in your own household to use your old
computer system to edit dictionary chapters, or you find some student with an
older copy of Word willing to help out that is only possible if you continue to
use the older Word file format.<BR><BR>My cynical side says that the main reason
Microsoft adopted this newer file format is so that they can force more people
to buy the newer version...<BR><BR></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=jmcbride@kawnation.com href="mailto:jmcbride@kawnation.com">Justin
McBride</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=siouan@lists.colorado.edu
href="mailto:siouan@lists.colorado.edu">siouan@lists.colorado.edu</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, July 13, 2007 12:52
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: SYMBOLS</DIV>
<DIV><BR></DIV>
<DIV><FONT face=Arial size=2>Jimm,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>The UTF-8 characters you sent came through just
fine on my email client. But if you're using a program such as Outlook
Express, like me, once you change your email encoding to UTF-8, I've found
that switching from Edit View to Source View or Preview View completely
destroys the Unicode characters. Also be aware that not all Unicode
characters are created equal. Some fonts, such as MS Arial Unicode, have
what looks to be the whole Unicode set, from the extremely rare to the
everyday. Some, though, such as Times New Roman, only have particular
portions of it, and instead default to other more specialized fonts when some
of the rarer Unicode symbols are used. So, for instance, I'm typing here
in the sans serif font Arial, but when I use the superscript n, ⁿ, you'll
notice that it has serifs on it. Why? It's because Arial has a
slot for that character, and even accepts its entry, but
doesn't actually have that character within its set (at least not when
used in Outlook Express) That brings up another
point. Different Microsoft applications handle Unicode placement
differently. So, you get a series of strange happy face and
musical symbols in the absolute lowest Unicode ranges on, say, MS Excel,
but just squares and blanks on MS Word. Likewise, you can paste a
huge string of Unicode characters into Outlook Express directly from Word, and
only some will come through. There are also several different
varieties of the Unicode, based on how many bits are used to code for the
character. It can get pretty confusing the further into the
technology you delve.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>You may recall that my paper for last year's
Siouan Conference (SIOUAN LANGUAGE DOCUMENTATION IN THE AGE OF .MP3, UNICODE,
AND XML) dealt briefly with placement of Unicode characters.
Sadly, I was never able to get to the copier before the weekend was up at
Billings, so no one got a copy of my paper, but here is an excerpt from it
that you may find useful:</FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV><FONT face=Arial size=2>I have found that keying in lengthy texts is
made much easier by the use of a Unicode-compatible font containing all the
necessary characters and a virtual keyboard to generate them in as few
keystrokes as possible. Unicode is an international character standard
with “a unique [code] number for every character, no matter what the
platform, no matter what the program, no matter what the language,” as well
as space available for private character development (Unicode, Inc.,
2006). Users can use the Unicode to produce a bewildering variety of
arcane characters, such as ề, ʢ, and ȣ, without having to change
fonts. It is, however, a font-dependent technology. I tend to
prefer the fonts Arial Unicode MS, Lucida Sans Unicode, (which come
prepackaged with Microsoft Office and Windows, respectively), and Gentium
(available for free at <A href="http://www.sil.org">www.sil.org</A>), each
of which has its own special uses but is perfectly capable of capturing
Siouan. I use Tavultesoft Keyman 6.0 to access my Siouan Unicode
keyboard on the fly (both are freely available at <A
href="http://www.languagegeek.com">www.languagegeek.com</A>). These
latter tools take some getting used to, but now I can generate Kansa
technical spellings only slightly slower than I can type
English.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>The benefits of digital text are obvious:
It can be easily generated, copied, edited, searched, or otherwise
processed. It can be lifted from one application and dropped into
another with minimal discomfort. Furthermore, the files themselves can
be renamed or organized as needed. There are a variety of text files
and formats to choose from, and even the most basic plain text editors (such
as the standard Notepad or TextEdit programs that come prepackaged with new
PCs or Macintosh models, respectively) are now Unicode-compatible with
slight nudging from the user. </FONT></DIV></BLOCKQUOTE>
<DIV><FONT face=Arial size=2>I hope this helps, and that all is well with you
and your family. Oh, and thanks again for the postcard of Bruce
Cass. I hung it up in my office window facing the hall, so that visitors
to the building can see it before they come in my office.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>-Justin McBride</FONT></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=goodtracks@peoplepc.com href="mailto:goodtracks@peoplepc.com">Jimm
GoodTracks</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=sfellz@earthlink.net
href="mailto:sfellz@earthlink.net">Steve Ellsworth</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=goodtracks@peoplepc.com
href="mailto:goodtracks@peoplepc.com">Jimm ThigrePi</A> ; <A
title=indart@access-one.com href="mailto:indart@access-one.com">Patt</A> ;
<A title=axwehu@yahoo.com href="mailto:axwehu@yahoo.com">RuEBEN AxeweHu</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, July 13, 2007 11:34
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> SYMBOLS</DIV>
<DIV><BR></DIV>
<DIV>Steve:</DIV>
<DIV><FONT face=Arial size=2>Instead of working on my
IOM Dictionary entries, I waste this morning time exploring the
pre-MS-Vista Menus" tab. And I think "What is different now on my old
classic menu. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>So interestingly, I find under "Menus"
>Insert > Symbols > More Symbols.....Letters for the prominent
alphabets of the world, i.e., Latin, Greek-Coptic, Russian, Arabic, and
misc. drawing lines, and other stuff I am not recognizing, ....and then
this... </FONT></DIV>
<DIV><FONT face=Arial size=2>the glottal stop and the enge (elongated tailed
"n"), which I am printing below this line to see if they make it to your
PC.</FONT></DIV>
<DIV><SPAN
style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><STRONG><FONT
size=5>ˀηŋ </FONT></STRONG></SPAN></DIV>
<DIV><SPAN
style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT
face=Arial size=2>These same symbols above and those alphabets used to be in
the font character maps under the previous system. Perhaps they still
are, but I am not checking it out now. </FONT></SPAN></DIV>
<DIV><SPAN
style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT
face=Arial size=2>There in the maps, they showed keying in code(s) and how
to make a short key insert which I never attempted. What is
significant here IS...</FONT></SPAN></DIV>
<DIV><SPAN
style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT
face=Arial size=2></FONT></SPAN> </DIV>
<DIV><SPAN
style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT
face=Arial size=2>They are listed as "Unicode". In short, this is a
world wide font set to eliminate the world wide problem we've experienced
locally, namely, using a set of fonts with accented (stressed) vowels and
various special character fonts in the course of our document files, sending
those files to another PC user, who receives them corrupted or with a
substituted font such as the deutsche esetz (spelling?), i.e., the
German letter for a double "s", as in "Nuss (nut)".</FONT></SPAN></DIV>
<DIV><SPAN
style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT
face=Arial size=2></FONT></SPAN> </DIV>
<DIV><SPAN
style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT
face=Arial size=2>Let me know if these arrive on your PC, as I am using the
MENUS tab you place on the PC yesterday. If you receive them, it will
be a phenomenal achievement for self, Rueben, and other assistants in the
various Siouan Languages Prograns, and the double benefit will more be to
enable more easily the requirement of DEL/ NSF/ ANA grants, and allow us to
eliminate the need to transfer the Siouan Font files among
ourselves. Well, at least for Ioway, Otoe-Missouria, anyway, and
perhaps, Hochank/ Winnebago.</FONT></SPAN></DIV>
<DIV><SPAN
style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT
face=Arial size=2>Jimm</FONT></SPAN></DIV>
<DIV><SPAN
style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT
face=Arial size=2></FONT></SPAN> </DIV>
<DIV><SPAN
style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT
face=Arial size=2>P.S.: I am drawing my conclusions above based on my
general abilities to accomplish the needs of my lexicology and bilingual
texts projects, and without a clue to the implications and interfacing
of the many vintages of PCs out there, and in particular, our MSWord/ Office
'98-2003 applications with the recent MSVista Word/ Office.
</FONT></SPAN></DIV>
<DIV><SPAN
style="FONT-SIZE: 7pt; FONT-FAMILY: 'Times New Roman','serif'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT
face=Arial size=2>To date, I am aware of your counsel to avoid the automatic
Vista extension added on to saved. doc files, which would preclude other PC
users being able to open attached .doc files, and the fact of the loss of
certain functions under the new Vista tabs.</FONT></SPAN></DIV></BLOCKQUOTE>
<P>
<HR>
<P></P>No virus found in this incoming message.<BR>Checked by AVG Free
Edition. <BR>Version: 7.5.476 / Virus Database: 269.10.4/898 - Release Date:
7/12/2007 4:08 PM<BR></BLOCKQUOTE></BODY></HTML>