GitHubRulesOK

May be a redherring but traditionally synctex only stored latin characters without spaces, more recently some versions will support spaces and unicode but I think CJK may require/benefit from oriental...

I think this is in effect a duplicate of #194 & #193

Potentially since the dawn of time issue 72points = 25.4 mm = 96dpi issue or 36 pixels = 12.7 mm = 48 pixels however, comment above is need **46** pixels...

technically plugins adresses this request, however see my comment in #31 (& enhances #30) Here the suggestion would be to allow user to specify more than one "special" extractor and...

this could be applied to all "variable extractors" for example a non-zip file extractable by z-zip may be handled differently by an alternative un-xxx component it would be useful if...

Just note the time while a bad pre-release is available can sometimes be extended the last 3 weeks have shown this test version as causing crashes easily for 2 different...

Interesting related https://github.com/xellows1305/Document-Image-Dewarping

Many scanned images have lots of noise at the edges so a one pixel test could produce the inverse of expectation, what may be better is a user defined sample...

Last one looks ok to me if documented well enough - is the S needed - @ could trip some platform/upstream app parsing - is -b 8,366,273 good enough for...

Look fine, Looking forward to a release and closure just a Small Matter Of Programming :big grin: