|
Posted by Chris Beall on November 27, 2004, 11:57 pm
Please log in for more thread options
I'm struggling with how to handle, on a web page, images that contain
text that the user must be able to read. Examples: tombstone photos,
photos or scans of historic documents (handwritten or typed), a map with
place names, route numbers, etc.
(An appropriate alternative for audio UAs would be provided and is not a
part of my concern).
I see two ways to handle these images:
1. Dynamic scaling, with the source image containing enough detail
for readable display in a large window, and a width specified in % so
that it always nearly fills whatever window the user has provided.
CONCERN: For small window sizes (ex: full-screen on a 640 X 480 display)
the browser shrinking of the image may make it illegible, especially the
fine lines in handwritten documents. CONCERN: In the case of a map, I
want to put an image map behind it for navigation. Popular browsers
don't seem to scale image maps when the associated image is scaled,
making this unworkable.
2. Multiple images: Let's say three images, each at a different
resolution, with the middle-sized one presented by default. On the same
page would be links for 'smaller image' and 'larger image' that would
take you to the other versions. CONCERN: Storage space required for 3
copies of every image (and image map, where used). CONCERN: 2/3 of the
users will not want the default and will have to click to the version
they want each time they reference any such image. CONCERN: How best to
create the images:
2a. Scan the original document/photo three times, setting the
scanner for different DPI values each time.
2b. Scan the original once, at a high DPI value, and use PhotoShop
or equivalent to produce the smaller versions.
Comments and suggestions?
Thanks,
Chris Beall
|
|
Posted by Malcolm Dew-Jones on November 28, 2004, 12:15 am
Please log in for more thread options
Chris Beall (Chris_Beall@prodigy.net) wrote:
: I'm struggling with how to handle, on a web page, images that contain
: text that the user must be able to read. Examples: tombstone photos,
: photos or scans of historic documents (handwritten or typed), a map with
: place names, route numbers, etc.
: (An appropriate alternative for audio UAs would be provided and is not a
: part of my concern).
: I see two ways to handle these images:
: 1. Dynamic scaling, with the source image containing enough detail
: for readable display in a large window, and a width specified in % so
: that it always nearly fills whatever window the user has provided.
: CONCERN: For small window sizes (ex: full-screen on a 640 X 480 display)
: the browser shrinking of the image may make it illegible, especially the
: fine lines in handwritten documents. CONCERN: In the case of a map, I
: want to put an image map behind it for navigation. Popular browsers
: don't seem to scale image maps when the associated image is scaled,
: making this unworkable.
: 2. Multiple images: Let's say three images, each at a different
: resolution, with the middle-sized one presented by default. On the same
: page would be links for 'smaller image' and 'larger image' that would
: take you to the other versions. CONCERN: Storage space required for 3
: copies of every image (and image map, where used). CONCERN: 2/3 of the
: users will not want the default and will have to click to the version
: they want each time they reference any such image. CONCERN: How best to
: create the images:
: 2a. Scan the original document/photo three times, setting the
: scanner for different DPI values each time.
: 2b. Scan the original once, at a high DPI value, and use PhotoShop
: or equivalent to produce the smaller versions.
: Comments and suggestions?
Perhaps publish it as a pdf document and let the reader take care of all
those details.
|
|
Posted by Chris Beall on November 28, 2004, 7:42 pm
Please log in for more thread options Malcolm Dew-Jones wrote:
> Chris Beall (Chris_Beall@prodigy.net) wrote:
> : I'm struggling with how to handle, on a web page, images that contain
> : text that the user must be able to read.
>
> : Comments and suggestions?
>
>
> Perhaps publish it as a pdf document and let the reader take care of all
> those details.
Thanks Malcolm.
My main concern with using pdf is that I expect many visitors to be
unfamiliar with it (and may not have the reader). The Adobe Reader
interface uses icons for things like magnification, which could confuse
some visitors.
Also, for the map case, I'm not aware of any way to make a pdf
navigable, i.e.. to put an image map or equivalent behind it.
Chris Beall
|
|
Posted by Lauri Raittila on November 28, 2004, 10:07 pm
Please log in for more thread options in comp.infosystems.www.authoring.html, Chris Beall wrote:
> Malcolm Dew-Jones wrote:
> > Chris Beall (Chris_Beall@prodigy.net) wrote:
> > : I'm struggling with how to handle, on a web page, images that contain
> > : text that the user must be able to read.
Solution depends greatly on images. Usually, best aproach is to just
replicate text below/aside image.
> > Perhaps publish it as a pdf document and let the reader take care of all
> > those details.
> My main concern with using pdf is that I expect many visitors to be
> unfamiliar with it (and may not have the reader). The Adobe Reader
> interface uses icons for things like magnification, which could confuse
> some visitors.
Very likely. It is also great annoyance to wait Acrobat reader to start.
That takes half minute in high end machines, and more on low end. So one
thinks twice before looking at those.
> Also, for the map case, I'm not aware of any way to make a pdf
> navigable, i.e.. to put an image map or equivalent behind it.
PDF will be better that image in html, if your map is vector. If your map
image is bitmap, PDF won't help. And then also, it is useful to have
bitmap for web and provide PDF as alternative.
--
Lauri Raittila <http://www.iki.fi/lr> <http://www.iki.fi/zwak/fonts>
|
|
Posted by erikd@nospam.wanted.here on November 28, 2004, 3:44 am
Please log in for more thread options On Sat, 27 Nov 2004 22:57:16 GMT, Chris Beall
>I'm struggling with how to handle, on a web page, images that contain
>text that the user must be able to read. Examples: tombstone photos,
>photos or scans of historic documents (handwritten or typed), a map with
>place names, route numbers, etc.
I don't know if it will work for your particular application, but
someone in the office is investigating using SVG for displaying
schematics. I tried out a sample and it's pretty impressive the way
that you can zoom in to see the drawing details. I don't know if it
will work for your items of interest. SVG = Scalable Vector Graphics.
--
Erik
|
| Similar Threads | Posted | | Input text whit out suggestions | September 6, 2007, 9:10 pm |
| Text and images in irregular shaped column(s) | October 21, 2005, 9:45 am |
| keep successive text/images in same place on the page? | April 25, 2008, 1:48 pm |
| [OT] Need graphics suggestions | April 18, 2006, 11:27 am |
| Web Design Magazine Suggestions | March 2, 2006, 5:08 pm |
| Re: Web Design Magazine Suggestions | March 2, 2006, 8:14 pm |
| Suggestions > Web developers conferences | October 3, 2006, 7:21 pm |
| Hosting for Reselling - Suggestions | October 9, 2006, 4:12 pm |
| I'm looking for suggestions on Stacked Tabs Menu | November 12, 2007, 4:46 pm |
| Does anyone have any suggestions for synchronizing multiple websites? | March 24, 2008, 11:52 am |
|
XML Sitemap