cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Your Friends List is a way to easily have access to the community members that you interact with the most! X

Resizing images in Editor's View

goreggioni-2
2-Explorer

Resizing images in Editor's View

Hi,


Is there any way in the DCF file or in the FOSI to limit the size the images are shown in the Editor's view?


We are working with Epic 5.4 and we would like to limit the large images (sometimes more than 2000 pixels wide or high) to be shown in the editor's view with a maximum of 600 px wide or high. Unfortunately I can't force the editors to use smaller images while working the XML files with Epic.


Tnx!


_____________________________

Gabriel Oreggioni

10 REPLIES 10

Hi Gabriel!

If your graphics are specified with an entity name, you can code the FOSI with an att for editor-only that suppresses the graphic and fillvals the graphic entity name into putgraph graphname. Code the putgraph characteristics to scale the graphic to the desired size. However, you will need to set hidesuppressed=yes for the Edit window, which may or may not work for you.

Good luck!

Suzanne Napoleon
www.FOSIexpert.com
"WYSIWYG is last-century technology!"

We are not using entities. Instead we have a tag <image src="filename"> for the images, and we have declared the tag as an graphic tag in the DCF file...


Any suggestion in such a case...?


_____________________________

Gabriel Oreggioni

You can also set your view preferences to show graphics as icons, which would totally disable all viewing of graphics, but you may not want this. However, this is easily turned on and off via tools-preferences-view for those times when users want to take a quick peek at a particular graphic somewhere.

Unfortunately, putgraph works only with an entity name, not a file name. Lemme think about it a little more.

IMHO a thumbnail capability should have been added to Arbortext Editor ages ago. I think everyone wants it.

Suzanne


Gabriel,

Does <image> have any other attributes besides filename?

Suzanne


Hi,


No, the tag has only the src att... 😞


_____________________________

Gabriel Oreggioni
______________________________

Are the file names in your image tags absolute, or do you rely on the
graphics path feature to resolve them? If the latter, you could set one
graphics path for use during authoring, which points to a directory
containing scaled-down versions of the graphics (which would have to be
properly maintained as new and modified versions of full-size images are
created) and point to the directory containing the full-size versions
during publishing runs. How you'd do this would depend on how you do your
publishing.

If you have absolute paths in your image tags... well, first, I'd suggest
moving away from that, as the graphics path approach has many advantages.
But in the meantime, the entity_path ACL callback might help, but I'm not
sure if it gets called for graphic references with a file name, rather than
an entity. Worth a try.

-Brandon 🙂


Hi Brandon,


Yes we use the graphics path feature, but the idea of maintaining two folders was something I was trying to avoid in favour of some FOSI______________________________

It's something that could be automated, easier or harder depending on the
tools and processes you use for maintaining your graphics. However, I can
understand the desire to avoid this type of solution, regardless. So, some
alternatives...

Do you have control of the DTD? If so, you could add an attribute to
control the width and use a variant of Suzanne's approach to have the FOSI
fill it in when it is empty and you're in screen mode (leaving it as-is for
print). If you want to avoid your authors messing with the attribute,
there are ways of hiding it, or you could add a completely separate
element, also configured as a graphic element in the DCF, which you can
hide from element lists so only the FOSI uses it.

If you don't have control of the DTD, you might be able to do the above
with a FOSI pseudo-element, though I don't know if the DCF will let you set
that up or not. Alternatively, you could maintain a separate version of
the DTD that is only used during authoring. This version would be the same
except it would add the width attribute and provide a default value
appropriate for screen display.

-Brandon 🙂


What version of Arbortext Editor are you using?

Suzanne


Announcements

Top Tags