discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Kristaps Dzonsons <kristaps@bsd.lv>
To: Ingo Schwarze <schwarze@usta.de>, discuss@mdocml.bsd.lv
Subject: Re: mdocml: It's annoying that we don't have preconv, so throw together a
Date: Thu, 26 May 2011 21:02:43 +0200	[thread overview]
Message-ID: <4DDEA3D3.80707@bsd.lv> (raw)
In-Reply-To: <20110526165415.GA9429@iris.usta.de>

>> It's annoying that we don't have preconv,
>
> All the more thanks for starting that!
>
> However, i see main() in there.
> That will end up with pipes and knobs.
>
> In the long run, i think this needs to be intregrated into mandoc,
> with as few knobs as possible.  OK, maybe we will need a knob to
> specify the input encoding, but maybe even that can sometimes be
> guessed from the file, for example when there is a BOM.
>
> In an UTF-8 terminal,
>
>    mandoc foo.jp.1 | less
>
> ought to be enough for everyone.
>
> Of course, there is nothing wrong with developing new functionality
> stand-alone, it was quite successful with tbl.

Ingo, I hope you don't mind that I cross-post this to discuss@...

For those of you not reading source-changes, there's now a preconv 
utility in mdocml for recoding multibyte manuals as mandoc input.

And it's more or less finished, not started! ;)  I'm able to download 
the Japanese manuals and read through them just fine.  Er... "look at 
them" just fine.  After running them through iconv to UTF-8, of course.

I do agree with what you say.  When you (and other downstream) think the 
time has come, it's ready to be migrated.  Til then, there's plenty of 
catching up to do as it is. ;)

I'll put out a release in the next few days to get eyeballs on all this 
locale stuff that's been checked in since BSDCan.  Once it's been in the 
wild for a little bit, I'll be more prepared to muck around with putting 
it directly into mandoc.

In terms of bloat, if we keep to Latin-1, US-ASCII, and UTF-8, there's 
not very much overhead (as you can see in preconv.c, most of which is 
read_whole_file, which will soon go away to compat.c where it belongs).

Thanks,

Kristaps
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

           reply	other threads:[~2011-05-26 19:02 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20110526165415.GA9429@iris.usta.de>]

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=4DDEA3D3.80707@bsd.lv \
    --to=kristaps@bsd.lv \
    --cc=discuss@mdocml.bsd.lv \
    --cc=schwarze@usta.de \
    /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).