discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: "LÉVAI Dániel" <leva@ecentrum.hu>
Cc: discuss@mdocml.bsd.lv
Subject: Re: "cannot parse date" for a seemingly valid .Dd parameter
Date: Thu, 28 Aug 2014 18:11:03 +0200	[thread overview]
Message-ID: <20140828161103.GR912@iris.usta.de> (raw)
In-Reply-To: <20140828083900.GM29425@serenity.local>

Hi Daniel,

LÉVAI Dániel wrote on Thu, Aug 28, 2014 at 10:39:00AM +0200:
> On cs, aug 28, 2014 at 02:43:42 +0200, Ingo Schwarze wrote:

>> After some code reading and some experimentation, i'm still quite
>> unsure where the problem might lie, i fail to reproduce but need
>> additional information.  Please apply the debugging patch appended
>> below (not intended for commit) to anoncvs HEAD, and run:
>> 
>>  $ ./configure
>>  $ make

> With the cvs checkout, mandoc(1) accepts the given date for me too.
> 
> config.h:
> #define HAVE_WCHAR 0

That's the reason you don't see the problem in HEAD:
wide character support is not detected.

>> Then please show me the output of the following sequence of commands:
>> 
>>  $ locale
>>  $ ./mandoc -Wall test.1 > /dev/null
>>  $ ./mandoc -Wall -Tlocale test.1 > /dev/null
 
> $ locale
> LC_TIME=hu_HU.UTF-8

Without wide character sipport, that's effectively disabled, see here:

> $ ./mandoc -Wall -Tlocale test.1 > /dev/null
> main: LC_TIME = C
> a2time: LC_TIME = C
> a2time: calling strptime()
> a2time: LC_TIME = C
> a2time: calling strptime()
> a2time: LC_TIME = C
> a2time: calling strptime()

No setlocale() here whatsoever, it doesn't even get compiled in.

> TBH, I'm a bit confused. You see, I've used 1.12.3 before,
> and I've just upgraded to 1.13.1 recently.

Sure, that would raise the question: Why did you not see the problem
in 1.12.3, and why do you see it in 1.13.1?  But maybe we don't
even have to answer that.  I just committed a small patch to improve
wide character support detection.  Can you do a CVS update, re-run
./configure and make, and re-send the output of the same commands
as before?  Just leave the debugging patches in your checkout
directory while doing all that, they are still needed.  I hope your
lost problem comes back, because i'm still unable to reproduce it,
even on 1.13.1.

> And because 1.12.3 did not have a ./configure script,
> furthermore with 1.13.1 I was not supposed to run
> ./configure directly,

Yeah, i admit that wiggled a bit back and forth until i got the
automatic configuration beat into shape.

> it seems to me, something has changed throughout the development
> that it seems has been fixed in HEAD, but exists (for me) in 1.13.1.
> Does this make sense?

No, what you have compiled from HEAD so far does not work for
you.  Your LC_* settings show you want UTF-8 support, but you
don't actually get that.  Small consolation it would be that
since you lost the feature, you lost the bug contained in it
as well.

Yours,
  Ingo
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2014-08-28 16:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 14:58 LÉVAI Dániel
2014-08-27 15:07 ` Kristaps Dzonsons
2014-08-27 15:15   ` LÉVAI Dániel
2014-08-28  0:43     ` Ingo Schwarze
2014-08-28  8:39       ` LÉVAI Dániel
2014-08-28 16:11         ` Ingo Schwarze [this message]
2014-08-28 16:32           ` LÉVAI Dániel
2014-08-28 17:35             ` Ingo Schwarze
2014-08-28 18:06               ` LÉVAI Dániel
2014-08-28 19:49                 ` Ingo Schwarze
2014-08-28 21:07                   ` LÉVAI Dániel
2014-08-29 15:38                     ` Ingo Schwarze
2014-08-30  8:57                       ` LÉVAI Dániel

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=20140828161103.GR912@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=discuss@mdocml.bsd.lv \
    --cc=leva@ecentrum.hu \
    /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).