Legacy ImageMagick Discussions Archive

I've released the Perl module https://metacpan.org/release/Image-Magick-CommandParser.

You're right. I was confused by the identical syntax.

This page - http://imagemagick.org/script/command-line-processing.php - has 2 copies of this section: Stream Buffering By default, the input stream is buffered. To ensure information on the source file or terminal is read as soon as its available, set the buffer size to 0: convert logo: gif ...

And at the same point: {size}{offset} Specifying the offset (default is +0+0). Below, {size} refers to any of the forms above. {size}{+-}x{+-}y Horizontal and vertical offsets x and y, specified in pixels. Signs are required for both. Offsets are affected by ‑gravity setting. Offsets are not a ...

On this page: http://imagemagick.org/script/command-line-processing.php there is an option: area@ Resize image to have specified area in pixels. Aspect ratio is preserved. But the example uses a different syntax: convert logo: -resize '@10000' wiz10000.png. Should the latter read convert logo ...

Ahh. OK. Thanx.

BTW: Is label:"Some text" the deprecated form of -label "Some text"?

And here it is as space-filled gist:

https://gist.github.com/ronsavage/eaa52bd0ab619cfc467b

Here it is: :default ::= action => [values] #lexeme default = latm => 1 # Longest Acceptable Token Match. # G1 rules in top-down order. :start ::= command_and_options command_and_options ::= command_name input_file_name rule_set command_name ::= 'convert' action => command | 'mogrify' action ...

An update. I originally wrote the BNF to treat each action (-size etc) separately. After re-writing the BNF many times to treat actions uniformly, I got the BNF down to 28 lines. But, post-processing the output of the parsing engine (Marpa::R2) to handle special cases caused me to write what I feel ...

For those intrigued, the Marpa-style BNF [1] is 425 lines, double-spaced for my personal preference making it 850.
[1] https://metacpan.org/pod/distribution/M ... ss/DSL.pod where DSL [2] is domain-specific language.
[2] https://en.wikipedia.org/wiki/Domain-specific_language.

An update on my Perl module. It's working well enough on options and their parameters. Now I'm just adding support for handling the trailing output file name as a special case of the latter. After that, a little cleaning up and I'll release it. The first practical use I see is to accept an IM -crop ...

OK. Thanx.

Re the table for '-ordered-dither threshold_map{,level...}', do I read it correctly that columns 1 and 3 only are valid inputs?

Thanx for the quick response. Many years (decades?) ago I was allowed to log on to IM and made some doc changes, but they were obliterated a couple of versions later, so I've been deeply reluctant to make any since :-( but I do appreciate the availability of it on github, since I use github myself ...