public inbox for mlmmj@mlmmj.org
 help / color / mirror / Atom feed
From: Ben Schmidt <mail_ben_schmidt@yahoo.com.au>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] [patch] man page fixes
Date: Mon, 23 Jan 2012 00:37:25 +0000	[thread overview]
Message-ID: <4F1CABC5.2040101@yahoo.com.au> (raw)
In-Reply-To: <4F1BD224.40908@goirand.fr>

On 23/01/12 6:13 AM, Thomas Goirand wrote:
> On 01/22/2012 09:56 PM, Ben Schmidt wrote:
>> Hi, Thomas,
>>
>> Thanks for this. I have a few issues/questions.
>>
>> 1. This doesn't apply cleanly to current sources in version control.
>> Would you be able to provide a patch that does?
>
> Sorry, my patch is from MLMMJ 1.2.17, as I didn't upgrade the Debian
> package yet (I'm waiting that you release something).

It's a wise move to wait until a release, of course. Just a little
tricky for me to apply old patches.

>> I can probably resolve the clashes OK, but I know little about groff,
>> so I'm not sure if other man-page changes/additions might also
>> require fixing, so it'd be better if someone who knows more what
>> they're doing could look at it.
>
> The issue is when you have something with dash "like-this". Groff will
> then try to wrap it, and you mind end up with something displayed like-
> this (eg: with a return to the next line, when you really don't want
> one). Adding a \ in front of the - makes it so that groff wont do the
> word break.

Thanks a lot for that detailed clarification. I'll do a semi-automated
find-replace on the current man pages and escape all the dashes.

>> 2. My system (Mac OS X) doesn't like the UTF-8 encoding. The existing
>> Latin-1 encoding works for me (in fact, the ø is replaced by just an o
>> for me automagically somewhere).
>
> All man pages should be using UTF-8 in Debian, and I believe that you
> should have your mac to use UTF-8 if possible. If not, do we care? Is
> MLMMJ used in the Apple platform?
>
> Also, what type of encoding do you use? Why is your encoding more valid
> than UTF-8? What if the user is let's say Chinese, Russian, or who knows?
>
> It really doesn't make sense to use any type of specific encoding,
> everyone should be using UTF-8, IMO.

I agree, it makes sense for everyone to use UTF-8 these days. However,
I'd prefer not to expect or assume that. I didn't mention my system
because I think it is particularly important, but simply to point out
that there is at least one system out there that this change will break.
There may be others. I would like to find a way to make this change that
won't break any system. Does anyone know how to do this, or another
project that has solved this problem whose work we can copy or imitate?

Cheers,

Ben.





  parent reply	other threads:[~2012-01-23  0:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-22  9:08 [mlmmj] [patch] man page fixes Thomas Goirand
2012-01-22 13:56 ` Ben Schmidt
2012-01-22 19:13 ` Thomas Goirand
2012-01-23  0:37 ` Ben Schmidt [this message]
2012-01-23  2:06 ` Ben Schmidt
2012-01-23  7:11 ` Thomas Goirand
2012-01-23 16:39 ` Ben Schmidt
2012-01-24  6:17 ` Mads Martin Jørgensen
2012-01-27  4:47 ` Thomas Goirand
2012-01-27  5:37 ` Ben Schmidt

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=4F1CABC5.2040101@yahoo.com.au \
    --to=mail_ben_schmidt@yahoo.com.au \
    --cc=mlmmj@mlmmj.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