forums.silverfrost.com

PaulLaidler · Posted: Fri Aug 16, 2019 9:03 am Post subject:

John-Silver

Thank you for your post.

1) The headers should have been added to clearwin.ins and the associated mod files. I have updated clearwin.ins and you can download the new version via the following link...

https://www.dropbox.com/s/puw7w3u2r5dkxek/clearwin.ins?dl=0

Please note that the Fortran routines end with @.

2) The name of the executable is EditSVG and not svgedit.

3) I think that you are expected to provide your own image files but I will make enquiries and get back to you if these should have been supplied.

PaulLaidler · Posted: Fri Aug 16, 2019 12:07 pm Post subject:

John-Silver

If you are using INCLUDE and clearwin.ins then you don't need the associated mod files. Mod files are for USE statements.

PaulLaidler · Posted: Mon Aug 19, 2019 7:09 am Post subject:

John-Silver

The author of EditSVG has read your post and here is his response...

The normal procedure when loading a TeX object is to use IMPORT_TEX_OBJECT@ to load the image in the correct place on the screen. Internally this uses Latex to obtain an SVG file that contains the big border, but it then strips the border off as it loads it. All that should be automatic, but what I think John-S has done is saved the SVG file and then loaded that file with IMPORT_SILVERFROST_SVG@, which doesn't know it should remove the white border!

The call to IMPORT_TEX_OBJECT@ should be between the open_svg@ call and the close_svg@ call - because it writes its result onto the currently open graphics region.

There should be no call to IMPORT_SILVERFROST_SVG@ and __SVGTEMP.svg was a name used by the software and it probably got deleted before the system tried to open it.

The problem is that one of the commands in Latex - DVISVGM - does not accept paths like any sane program would, so everything has to happen in the user's directory!

PaulLaidler · Posted: Wed Aug 21, 2019 7:30 pm Post subject:

John-Silver

This enquiry seems too long and complex to me. We have limited resources and many demands on our time.

LitusSaxonicum · Posted: Thu Aug 22, 2019 9:04 am Post subject:

Isn't this matter better resolved by posting an example that does work?
Documentation comes in many forms, including short demonstration codes .

Eddie

PaulLaidler · Posted: Thu Aug 22, 2019 10:05 am Post subject:

Eddie

I am not familiar with the subject but I agree that it would help if we were to provide a sample program that calls EDITSVG_DRIVER. Also the documentation refers to some sample files that might be missing.

LitusSaxonicum · Posted: Thu Aug 22, 2019 10:32 am Post subject:

Thanks Paul. I am an avid reader of documentation before I embark on something new, and although I sometimes miss things, I know from experience that one can be hung up on a simple point for ages, just 'not getting it'.

Incidentally, the new(ish) %sb status bar is excellent.

Eddie