On Wed, 31 Jul 2002, Jason Maiorana wrote:
>
>>I see the problem. This is a very important bug, and I wish I knew
> more
>>about encodings and stuff so that I could fix it. Make sure to submit
> a
>>bug report on it. In fact, there should probably be several separate
>>reports: One that Dia doesn't assume that files without specific
> encoding
>>is latin1, one that it doesn't read latin1 encoding correctly (and
> probably
>>not others, either), and one about how to input non-ascii chars.
>
> It may be sufficient for dia to only support utf-8. You generally dont
> create dia files by hand, so you probably shouldnt care which encoding
> they are
> in. If you want to view/edit or print dia source code, then many apps
> (IE,Mozilla)
> exist that work fine for that. If you are writing scripts then there
> should be
> no difficulty in translating to utf-8, as there are many libraries
> available
> for that. If you always edit dia files from within dia, then it shouldnt
> be an
> issue whatsoever.
We need to support non-utf8 encodings for two reasons: Backwards
compatibility and diagrams created by other programs. And the problem of
inputting non-ascii chars still stands.
-Lars
--
Lars Clausen (http://shasta.cs.uiuc.edu/~lrclause)| Hårdgrim of Numenor
"I do not agree with a word that you say, but I |----------------------------
will defend to the death your right to say it." | Where are we going, and
--Evelyn Beatrice Hall paraphrasing Voltaire | what's with the handbasket?