Re: [OBO-Edit Working Group] allow extended characters

[Walls, R. <rw...@ny...>]

I'm not certain how the file is encoded (I can't make the file -bi command work in Terminal). It shows up fine on Firefox if I change character encoding to unicode, suggesting it is already in unicode. If I open it in a text editor and specifically save it as unicode, the characters then just show up as nonsense in OE, and I still get the fatal error.

_____________________________
Ramona Walls
Post-doctoral Researcher/Plant Ontology Curator
New York Botanical Garden
2900th Southern Blvd.
Bronx, NY 10458
(718)817-8173
(516)885-8005



-----Original Message-----
From: Waclaw Kusnierczyk [mailto:wa...@id...]
Sent: Wed 9/28/2011 10:35 AM
To: gen...@li...
Subject: Re: [OBO-Edit Working Group] allow extended characters
 
On 09/28/2011 09:25 AM, David Osumi-Sutherland wrote:
>
> On 28 Sep 2011, at 15:15, Walls, Ramona wrote:
>
>> No, they are not in unicode. I don't know what it is called, but they
>> are just the straight version of the Japanese characters copied an
>> pasted into the ontology text file. I know that the old verision of
>> AmiGO that the PO uses can't read them either, but our Japanese
>> translater (who is much more computer savvy than me) has a way to get
>> AmiGO to work for her.
>>
> Easy to change/test encoding in a browser (check your view menu if you
> use firefox).

some text editors should be able to do it for you, too.  for example,
the free komodo-edit ide.  perhaps loading your file and saving it with
a different encoding would help.

you can test the encoding of a file using the file command:

    file -bi <your file>

you can also recode a file using iconv:

    iconv -f <input encoding> -t <output encoding> <input file> >
<output file>

or recode:

    recode <output encoding> <input file> > <output file>



vQ