On 2013-05-13 17:04, Warren Young wrote:
I know how to fix this when you generate PDF from DocBook via XSL-FO
(e.g. xsltproc and Apache FOP) but that brings in its own bag of
problems. For one biggie, all the XSL-FO processors depend on Java.
Fop is available in Ports; it is used to generate t
On 5/10/2013 17:19, Linda Walsh wrote:
the PDF code font is less than optimal..
The current doco PDFs are generated through dblatex, via xmlto. I don't
know if it's possible to reach through two generators to affect final
output fonts.
I suspect part of this is due to the weirdness of font
On May 10 11:13, Warren Young wrote:
> On 5/10/2013 08:31, Christopher Faylor wrote:
> >
> >I don't know what Corinna's return has to do with this.
>
> http://cygwin.com/ml/cygwin-patches/2013-q2/msg00011.html
>
> The open question is whether we're going to switch all the DOCTOOL
> tags and *.sgm
Warren Young wrote:
> On 5/9/2013 22:12, Christopher Faylor wrote:
> I haven't tried digging further to figure out how these man pages were
> http://etr-usa.com/cygwin/doc/test/ccp.3
> http://etr-usa.com/cygwin/doc/test/ccp.pdf
> I think these outputs look pretty good, myself. The HTML is
On 5/10/2013 08:31, Christopher Faylor wrote:
I don't know what Corinna's return has to do with this.
http://cygwin.com/ml/cygwin-patches/2013-q2/msg00011.html
The open question is whether we're going to switch all the DOCTOOL tags
and *.sgml in winsup/cygwin to Doxygen, or keep it as DocBoo
On Fri, May 10, 2013 at 10:29:04AM -0400, Christopher Faylor wrote:
>On Fri, May 10, 2013 at 03:48:37AM -0600, Warren Young wrote:
>>On 5/9/2013 22:12, Christopher Faylor wrote:
>>>
>>> Warren, if you want to take over the cygwin-doc package you're welcome
>>> to it.
>>
>>Pending our discussion wit
On Fri, May 10, 2013 at 03:48:37AM -0600, Warren Young wrote:
>On 5/9/2013 22:12, Christopher Faylor wrote:
>>
>> Warren, if you want to take over the cygwin-doc package you're welcome
>> to it.
>
>Pending our discussion with Corinna when she gets back, sure.
>
>I haven't tried digging further to f
On 5/9/2013 22:12, Christopher Faylor wrote:
Warren, if you want to take over the cygwin-doc package you're welcome
to it.
Pending our discussion with Corinna when she gets back, sure.
I haven't tried digging further to figure out how these man pages were
generated for the cygwin-doc package
On Thu, May 09, 2013 at 08:04:45PM -0600, Warren Young wrote:
>On 5/9/2013 13:37, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
>>
>> I'm using stock Cygwin 1.7.18-1, and tried to read manpages about Cygwin
>> path conversion routines, cygwin_conv_path() et al. The output does not
>> appear formatte
On 5/9/2013 13:37, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
I'm using stock Cygwin 1.7.18-1, and tried to read manpages about Cygwin
path conversion routines, cygwin_conv_path() et al. The output does not
appear formatted properly,
This appears to be a very old problem.
Here's what I know
> Perhaps something has changed in your '/etc/man.conf' too?
Thanks for the suggestions, but I did not touch anything from
their standard settings after installation. And I checked my
environment for any man settings, found nothing.
FWIW, I am using very wide terminal (at least 132 cols, mintty)
On 5/9/2013 3:37 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
Hello,
I'm using stock Cygwin 1.7.18-1, and tried to read manpages about Cygwin
path conversion routines, cygwin_conv_path() et al. The output does not
appear formatted properly, e.g. DESCRIPTION goes as a single paragraph,
but cl
12 matches
Mail list logo
