Your message dated Sun, 13 Aug 2017 11:46:38 -0700
with message-id 
<capqicoxdqqrx2he-fbbaenlt9bqfyfh-l6g8huhykdcdkw2...@mail.gmail.com>
and subject line Intended behavior from back in 2007
has caused the Debian Bug report #441009,
regarding Asciidoc enhancement requests
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
441009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441009
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: asciidoc
Version: 8.2.2-1
Severity: normal

Hi, 

I'm a long time asciidoc user (eg, 
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/doc-mode
).

Recently I've upgraded my Debian from Etch to Lenny (eg, upgrading
asciidoc from version 7.1.x to 8.2.2-1), and noticed different
behaviors between current implementation of asciidoc and the version
that I previously used. 

In brief, I hope that new asciidoc will keep urls as is, instead of
doing text formatting to it:

 $ cat asciidoc.test.doc
 HTML-WikiConverter
 http://search.cpan.org/~diberri/HTML-WikiConverter-0.61/[]
 http://search.cpan.org/~diberri/HTML-WikiConverter-MediaWiki-0.55/[]

 test
 http://host/~user/file#_anchor_tag_str_[]

 $ cat asciidoc.test.doc | asciidoc -s -
 <p>HTML-WikiConverter
 <a 
href="http://search.cpan.org/<sub>diberri/HTML-WikiConverter-0.61/">http://search.cpan.org/<sub>diberri/HTML-WikiConverter-0.61/</a>
                                 ^^^^^
 <a 
href="http://search.cpan.org/</sub>diberri/HTML-WikiConverter-MediaWiki-0.55/">http://search.cpan.org/</sub>diberri/HTML-WikiConverter-MediaWiki-0.55/</a></p>
                                 ^^^^^
 <p>test
 <a 
href="http://host/~user/file#<em>anchor_tag_str</em>">http://host/~user/file#<em>anchor_tag_str</em></a></p>
                                 ^^^^^             ^^^^^

Urls that I collected from Internet can vary beyond anybody's
imagination, eg.
http://search.cpan.org/~grantm/XML-Simple-2.12/lib/XML/Simple.pm#ForceArray_=%3E_1_#_in_-_important
Keeping them as is without applying text formatting will sure easy
the task to use asciidoc as a documentation tool.

Also IMHO, the most common use of superscripts and subscripts are in
math and chemical equations. In such case, the superscripts and
subscripts are rather short. But I notice for the following
paragraph, even I've ensured that there is only one tilde (~) per
line, the several-line text from "15 minutes" til "on HD within
6" are all considered as subscripts by the current version of
asciidoc. This is way too much. I hope this can be fixed:

Its installation does not require human intervention. So whenever I need a
Linux system, I was able to have a system ready within 10~15 minutes, which
contains the very tools that I want. This is the most important thing to
me. Some other Debian Live Systems, eg, sidux, can be installed on HD within
6~8 minutes or so, but how long will it take to further tune the installed
System to your taste?

Thanks

Tong

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (600, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-grml
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages asciidoc depends on:
ii  python                        2.4.4-2    An interactive high-level object-o

Versions of packages asciidoc recommends:
pn  docbook-utils                 <none>     (no description available)
pn  fop                           <none>     (no description available)
ii  source-highlight              2.4-5      convert source code to syntax high
pn  vim-addon-manager             <none>     (no description available)
pn  xmlto                         <none>     (no description available)

-- no debconf information



--- End Message ---
--- Begin Message ---
Hi,

This was an intended behavior from the upgrades back in 2007.
Has been tagged as won't fix in 2010.
I guess it's safe to close this.

Mode: cleanup

Thanks
Joseph

--- End Message ---

Reply via email to