getopt output reordering (was: xmlto package install question)
Talking to Tim Waugh, the author of xmlto, revealed that the order of arguments doesn't matter on his system (that's Red Hat, I guess), whereas it matters indeed on Cygwin. Investigating it a bit further revealed that Cygwin's getopt differs from what he expected: getopt -- o: xmlto -o foo bar should output this: -o 'foo' -- 'xmlto' 'bar' Cygwin's getopt outputs like this: $ getopt -- o: xmlto -o foo bar -- 'xmlto' '-o' 'foo' 'bar' Checking the archive I found a thread from back in January talking about the inability of Cygwin's getopt to do reordering of arguments. I guess we're facing here the same issue: the option arguments are not output before the non-option arguments. Was any work done wrt this issue? Is anything planned? Tim is going to update the xmlto usage information to reflect the proper order of arguments. Patrick Gerrit P. Haase schrieb: usage: xmlto FORMAT [OPTION]... XML OPTIONs are: -v verbose output (-vv for very verbose) -x stylesheet use the specified stylesheet instead of choosing one -m fragment use the XSL fragment to customize the stylesheet -o directoryput output in the specified directory instead of the current working directory It only works if you swap 'FORMAT [OPTIONS]' to '[OPTIONS] FORMAT' which is what I found in the patch included in the source package. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: xmlto package install question
Hi Patrick. On 2003.08.02 11:57, Patrick Eisenacher wrote: Hi, my Cygwin xmlto installation (v0.0.14) is missing all the fo formats (dvi, pdf, ps) in /usr/share/xmlto/format/docbook, and the fo subfolder is missing from the /usr/share/xmlto/format/ directory completely. Without those files xmlto is unable to create the corresponding target document formats (provided the corresponding toolchain is installed). Talking to Tim Waugh, the author of xmlto, revealed that all formats are installed unconditionally. So I wonder why they didn't get installed on my system. Is anybody else missing those files or do they get installed on your systems? In particular the files in question are: /usr/share/xmlto/format/docbook/dvi /usr/share/xmlto/format/docbook/pdf /usr/share/xmlto/format/docbook/ps /usr/share/xmlto/format/fo/dvi /usr/share/xmlto/format/fo/pdf /usr/share/xmlto/format/fo/ps dvi, pdf and ps format are removed from cygwin xmlto package because there is no way to generate these output formats using cygwin-only packages. They requires xmltex and passivetex which are not available as cygwin packages. I'll add support for missing formats soon after somebody will contribute these packages for cygwin. Regards. -- +---+ | Marcel Telka e-mail: [EMAIL PROTECTED] | |homepage: http://telka.sk/ | |jabber: [EMAIL PROTECTED] | +---+ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: getopt output reordering (was: xmlto package install question)
Patrick Eisenacher wrote: Talking to Tim Waugh, the author of xmlto, revealed that the order of arguments doesn't matter on his system (that's Red Hat, I guess), whereas it matters indeed on Cygwin. Investigating it a bit further revealed that Cygwin's getopt differs from what he expected: getopt -- o: xmlto -o foo bar should output this: -o 'foo' -- 'xmlto' 'bar' Cygwin's getopt outputs like this: $ getopt -- o: xmlto -o foo bar -- 'xmlto' '-o' 'foo' 'bar' Checking the archive I found a thread from back in January talking about the inability of Cygwin's getopt to do reordering of arguments. I guess we're facing here the same issue: the option arguments are not output before the non-option arguments. Was any work done wrt this issue? Is anything planned? IIRC, the end result of the discussion was that no consensus could be reached on whether it was better to reorder or not to reorder, so CGF had to make a ruling, and he ruled not to reorder. Reordering can be enabled by setting POSIXLY_INCORRECT_GETOPT in the environment, but because getopt is statically linked, this only works for programs rebuilt since this change was made, and many haven't been yet. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
xmlto package install question
Hi, my Cygwin xmlto installation (v0.0.14) is missing all the fo formats (dvi, pdf, ps) in /usr/share/xmlto/format/docbook, and the fo subfolder is missing from the /usr/share/xmlto/format/ directory completely. Without those files xmlto is unable to create the corresponding target document formats (provided the corresponding toolchain is installed). Talking to Tim Waugh, the author of xmlto, revealed that all formats are installed unconditionally. So I wonder why they didn't get installed on my system. Is anybody else missing those files or do they get installed on your systems? In particular the files in question are: /usr/share/xmlto/format/docbook/dvi /usr/share/xmlto/format/docbook/pdf /usr/share/xmlto/format/docbook/ps /usr/share/xmlto/format/fo/dvi /usr/share/xmlto/format/fo/pdf /usr/share/xmlto/format/fo/ps Patrick -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: xmlto package install question
Hallo Patrick, Am Samstag, 2. August 2003 um 11:57 schriebst du: Hi, my Cygwin xmlto installation (v0.0.14) is missing all the fo formats (dvi, pdf, ps) in /usr/share/xmlto/format/docbook, and the fo subfolder is missing from the /usr/share/xmlto/format/ directory completely. Without those files xmlto is unable to create the corresponding target document formats (provided the corresponding toolchain is installed). Talking to Tim Waugh, the author of xmlto, revealed that all formats are installed unconditionally. So I wonder why they didn't get installed on my system. Is anybody else missing those files or do they get installed on your systems? In particular the files in question are: Yes, and looking in the source package I see in the patch: -nobase_pkgdata_DATA = format/docbook/dvi \ +nobase_pkgdata_DATA = \ format/docbook/fo \ format/docbook/html \ format/docbook/html-nochunks \ format/docbook/xhtml \ format/docbook/xhtml-nochunks \ format/docbook/man \ - format/docbook/pdf \ - format/docbook/ps \ format/docbook/txt \ format/docbook/htmlhelp \ format/docbook/javahelp \ - format/fo/dvi \ - format/fo/pdf \ - format/fo/ps \ xmlto.mak Also I think that it doesn't work as expected, i.e. no error is displayed when s.th. fails, just the usage information which is not helpful for finding the error: $ make 21 | tee log.make02 make all-am make[1]: Entering directory `/e/ftp.inf.tu-dresden.de/software/windows/cygwin32/release/xmlto/xmlto-0.0.14' for xml in xmlif.xml xmlto.xml; do \ FORMAT_DIR=./format XSL_DIR=/usr/share/sgml/docbook-xsl \ bash ./xmlto man -o man/man1 ./doc/$xml ; \ done usage: xmlto FORMAT [OPTION]... XML OPTIONs are: -v verbose output (-vv for very verbose) -x stylesheet use the specified stylesheet instead of choosing one -m fragment use the XSL fragment to customize the stylesheet -o directoryput output in the specified directory instead of the current working directory It only works if you swap 'FORMAT [OPTIONS]' to '[OPTIONS] FORMAT' which is what I found in the patch included in the source package. Also this annoying behaviour is not documented in the README or elsewhere (besides the patch in the source package). Also to send upstream: It is not possible to specify an alternative to 'XSL_DIR=$(top_srcdir)/xsl' when running configure which makes it neccessary to manually link the xsl directory to the sourcedir or to manually edit the Makefile templates. Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
