Re: [Dillo-dev]Hi.

[Michael G. <mi...@sh...>]

 > > I'm Korean. Do you know Korea?
 > > Korea is in asia.
 > > Of course, my charset is 'euc-kr'
 > > It is 2 byte.

Hi, I'm Russian. Of course, I'm not using 2-byte charset, but I'm also
interesting in ability to work with international content in Dillo.

I made some minor changes to Dillo and it work nicely with most of
russian sites. But all of my changes are hacks. There has to be more
universal scheme. What I did:
 
 1. First of all, I've inserted "Accept-Charset:  koi8-r" in request
    headers. After that step most of russian sites gives me pages in
    koi8-r.

 2. I have koi8-r fonts installed in X before others and Dillo renders
    good russian text for me.

 3. I encounter a problem inputing russian text in forms. Then I've
    inserted  gtk_set_locale();  before  gtk_init(&argc, &argv);
    in main(). And it works for me.

But there is some problems at least with russian sites:
A. Some sites sending windows-1251 pages despite of my Accept-Charset
and such behavior is not RFC violation. 
B. There is some broken sites sending me pages with charset not
corresponding to specified one. Many russian sites not specify
charset at all.
C. In russia we have more than 5 different charsets and (in theory)
each can be used by web-server. Oh.

I'm not a gtk+ expert :( and just started to learn it (with problem
N3). Also I'm newbie in Linux C programming. And I had no C/C++
programming practice for 3 years. (Last time PHP mostly). So I can't
solve all problems right now by myself quickly and in the best
universal way :(

Anyway I'm trying to expirement with charset recoding now.
I've added charset pointer to DilloHtml struct. I wrote function
for charset extraction from Content-Type header and I've inserted this
extraction to a_Html_text(). Next version of Glib will contain
g_convert() function for charset recoding. But now I'm using
iconv(). I've inserted recoding to Html_write() function, only from
windows-1251 to koi8-r. It works nicely.
Now I recieved next problem with forms: some servers don't properly
recode my input.


 > > 
 > > I saw that dillo will be able to show us frame & table.
 > > but, I could not see that dillo will be able to show me multibyte
 > > characters.
 > > There is no font selection....
 > > 
 > > Can you help me?
 > 
 > Personally, I'd like it if dillo could be able to render different
 > character sets, this will increase the amount of possible users quite
 > much :-). In Gtk+ 1.2, this is quite hard to implement, but Gtk+ 2.0
 > will depend on the Pango library, which purpose is to handle all
 > different kinds of languages. I haven't taken a look at it yet, but I
 > think that using Pango is indeed an option.

As I understand GTK+ 2.0 should come out before the end of the
year. Is it true? 

Charset-related problems are not in "primary concerns" and not in
"Future Goals". What Dillo developers think about it? Is it will be
easy to solve them in the future without reconstructing of Dillo
internals? I'm meaning all charsets, including CJK. Wouldn't it be
simplier to make some steps now? Or this question requires study?

-- 
-Michael Govorun