From: Jens Staal <staal1978@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] adding javascript enable to netsurf
Date: Sat, 21 Mar 2020 06:00:22 +0100 [thread overview]
Message-ID: <20200321050022.hd6ihoadli3s6pyc@Hugin> (raw)
In-Reply-To: <9ea904c49597157c4e05c37e1d93f35e@oboj.net>
On Fri, Mar 20, 2020 at 08:54:55PM +0200, jamos@oboj.net wrote:
> This one seem to be iconv(). We need a better one, but
> I just updated the "fake" iconv() so that outputs what
> comes in, and that seem to make google work (at least
> if you search for anything 7 bit ASCII). I uploaded it
> to 'nsport' but there seem something missing.
>
> I see multiple options for iconv() ... 1) write something
> that uses tcs(1), 2) use the iconv() for RISCOS (separate
> netsurf repo) requires to implement some unicode routines.
> 3) find some suitable iconv() implementation; Jens Staal
> ported APR iconv() but it is quite big and a bit tricky to
> build. There is also gnulib in ports, but I rather not go
> that route. Iconv() is not connected to the framebuffer
> frontend, but generally needed for the browser. What do
> you all think? Do you know of a sleek iconv()
> implementation?
>
> Jonas
Back when I did APR I musl libc did not exist (or I was not aware of it). Perhaps
could the iconv function from that library be used?
next prev parent reply other threads:[~2020-03-21 5:00 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 5:49 kokamoto
2020-03-20 16:10 ` Kyle Nusbaum
2020-03-20 16:15 ` ori
2020-03-20 17:12 ` telephil9
2020-03-20 17:40 ` Jens Staal
2020-03-20 18:54 ` jamos
2020-03-21 5:00 ` Jens Staal [this message]
2020-03-21 12:24 ` Ethan Gardener
2020-03-20 22:07 ` Kyle Nusbaum
-- strict thread matches above, loose matches on Subject: below --
2020-04-14 5:04 kokamoto
2020-04-14 21:53 ` Kyle Nusbaum
2020-04-15 20:05 ` jamos
2020-04-15 20:24 ` ori
2020-04-18 1:09 ` Kyle Nusbaum
2020-04-18 1:19 ` ori
2020-04-18 17:11 ` Eli Cohen
2020-04-18 17:15 ` telephil9
2020-04-18 17:17 ` ori
2020-04-13 23:46 kokamoto
2020-04-07 4:25 kokamoto
2020-04-06 5:48 kokamoto
2020-04-13 12:44 ` jamos
2020-04-05 4:52 kokamoto
2020-04-05 4:41 kokamoto
2020-03-22 23:47 kokamoto
2020-03-22 2:19 kokamoto
2020-03-21 3:24 kokamoto
2020-03-22 20:27 ` jamos
2020-03-22 20:54 ` ori
2020-03-22 20:54 ` ori
2020-03-17 11:16 kokamoto
2020-03-17 17:42 ` jamos
2020-03-15 9:42 kokamoto
2020-03-15 11:06 ` Steve Simon
2020-03-15 11:38 ` Jens Staal
2020-03-15 13:50 ` jamos
2020-03-14 1:49 kokamoto
2020-03-14 2:09 ` ori
2020-03-14 1:19 kokamoto
2020-03-14 1:34 ` ori
2020-03-13 4:33 kokamoto
2020-03-13 4:58 ` ori
2020-03-12 5:28 kokamoto
2020-03-12 2:20 kokamoto
2020-03-12 2:43 ` ori
2020-03-11 23:59 kokamoto
2020-03-11 10:27 kokamoto
2020-03-11 6:36 kokamoto
2020-03-11 9:29 ` [9front] " jamos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200321050022.hd6ihoadli3s6pyc@Hugin \
--to=staal1978@gmail.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).