The figures turn out to be quite practical though! :) Non-utf8 Encoding for
most forms should work now, although some corner-cases for POST are still
missing.
Probably the fonts could be copied over or you can look for fonts that include
subfonts covering the fullwidth ranges 0xff01-0xffe5. By
> PS: this is also a test of 9legacy's upas to attach figures☺
Ok, I got right mail with figures.
Kenji
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T9a725c37f61954a8-M5d59097b8c3833de4eecc4c7
Delivery options:
> diff -r 859a4e61471b lib/font/bit/lucidasans/unicode.10.font
> --- a/lib/font/bit/lucidasans/unicode.6.font Mon May 03 21:04:39 2021 +0200
> +++ b/lib/font/bit/lucidasans/unicode.6.font Mon May 03 22:35:32 2021 +0200
> @@ -55,6 +55,7 @@
> 0x9a01 0x9bf5 ../shinonome/k12.9a01
> 0x9c04
Hi!
Here's a patch for most of the fullwidth glyphs in lucidasans and vga! The
subfonts are already used in each font file. I guess one way to quickly test
would be:
hget https://ja.wikipedia.org | htmlfmt > /tmp/wp
for (font in /lib/font/bit/lucidasans/unicode.*.font
Quoth Philip Silva via 9fans <9fans@9fans.net>:
> Hm ok, that's rather tricky to reproduce. (Also unfortunately I don't have a
> running 9legacy system) One thing I noticed though that for instance on
> https://ja.wikipedia.org the parentheses are usually fullwidth parentheses
> and on 9front
Hm ok, that's rather tricky to reproduce. (Also unfortunately I don't have a
running 9legacy system) One thing I noticed though that for instance on
https://ja.wikipedia.org the parentheses are usually fullwidth parentheses and
on 9front rendered to the UTF8 face :-). I added a commit which
I included a picture taken on 9legacy's opossum screen.
On the 6th line, there is a words of '日本語Nul言語Nul',
which should be '日本語(言語)'.
The '(' or ')' is replaced by NUL character, which may be
caused from a library under your program, not from yours.
This is just my guess.
Kenji
from
Awesome, no problem!
> There is still 'NUL' character when 漢字 and ( or ), hankaku moji,
are mixed: like
> 例(日本語) ==>例NUL日本語NUL
I wonder what that could be. So with the current version (910bfe from
yesterday) it can work if the input is UTF-8: http://psilva.sdf.org/ja.html Do
you maybe have a
> Yes, now we can see right Japanese text!
It's not enough.
There is still 'NUL' character when 漢字 and ( or ), hankaku moji,
are mixed: like
例(日本語) ==>例NUL日本語NUL
Kenji
--
9fans: 9fans
Permalink:
Yes, now we can see right Japanese text!
Very quick fix, thanks.
Kenji
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T9a725c37f61954a8-M5edc10f1830b81c5be2d7bc0
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
That was unexpected, but it should be much better now! Now the character set
hint is actually used
‐‐‐ Original Message ‐‐‐
Am Freitag, 23 April 2021 06:37 schrieb :
> Please look at http://google.co.jp
>
> We see many 'NULL' on this page.
>
> Kenji
>
>
>
Please look at http://google.co.jp
We see many 'NULL' on this page.
Kenji
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T9a725c37f61954a8-M26405485fc05d412397ae633
Delivery options:
Although I guess generally it's good to have more than one Browser available.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T9a725c37f61954a8-Mfe40f44f07f618e8e041c150
Delivery options:
> > One big disadvantage is not having 'colspan'...
>
> Nice, now it has this, and do resizing of the window!
True! At least the colspan is gracefully ignored, but probably it's really not
that important :D
Philip
--
9fans: 9fans
Permalink:
> One big disadvantage is not having 'colspan'...
Nice, now it has this, and do resizing of the window!
Kenji
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T9a725c37f61954a8-Maa74ff3b8e96100d5c595a51
Delivery options:
> Also it's quite speculative how far one could get with JS which is
> essentially based on goja and domino.
Yes, JS works in more limited than netsurf, although the latter has a little
functions.
One big disadvantage is not having 'colspan'...
Kenji
Thank you very much for your technical explanation, Philip.
By the way the file sizes of both are:
--rwxrwxr-x M 24 sys sys 51135788 Jan 7 15:33 /amd64/bin/netsurf
--rwxr-xr-x M 24 sys sys 15456437 Jan 7 09:32 /amd64/bin/opossum
Kenji
--
9fans: 9fans
To be fair I think the rendering quality can be attributed to the html/css
processing. For instance parsing is completely done by golang.org/x/net/html
and github.com/aymerick/douceur. (Also one can get quite far with handling
display: inline/inline-block/flex and height/width attributes)
One
http://git.pmikkelsen.com/ph/opossum
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T9a725c37f61954a8-Mf2d9006c5749e4decf646828
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
> Netsurf is written in C, and Opossum is in Go.
> Most basic difference is that opossum is written for Plan 9
> from the beginning which may be better for us...
>
One point in favour, from a Go fan: Go is far more maintainable than
C. I can think of some disadvantages, though.
As I can't find
I got now rwo new web browsers which can do css and/or js on my
9front box.
Both have almost same functionality and speed etc.
A page with JS (https://eonet.ne.jp) is almost same as that by JS enabled
netsurf.
Netsurf is written in C, and Opossum is in Go.
Most basic difference is that opossum
21 matches
Mail list logo
