John -

You said what I have wanted to say during this entire debate. JPEG is the way it is used in a written definition but with the early windows jpg with its standard three characters was the standard. It has remained so.

I might also comment that putting gif files on the web is an invitation for many who are on dial-up access to close the page.

Unless they are incredibly small gif's - they can be excruciatingly slow to load for those on dial-up. (tif's are even worse). I've been making the majority of my living on the internet for a good number of years. The standard has usually been if a page takes more than 30 seconds to load, most people will click off it. I will almost guarantee if a page includes gifs or tifs - most dial-up users will never see the entire page. (My other pet peeve are pages that load music before they download, and I have access to a T-1 line during part of my day.)

I agree that Legacy should not be blamed for what are usual industry standards. Overall, Legacy seems to handle images better than most genealogy programs I am familiar with, especially when it comes to hierarchy and web accessibility as well as what you have stored on your home computer.

Jackie

John Carter wrote:
I think the problem here is in definitions.

JPEG = Joint Photographic Experts Group

JPG = The standard 3 character extension for identifying images created in
the format defined by the Joint Photographic Experts Group.

Since MS-DOS and Windows are de facto standards and some versions only
supported 3 character extensions, JPG became the standard extension. (Yes, I've seen JPEG and JPE as well; neither is a standard.)

Let's not fault Legacy for following a standard.

John

Dennis M. Kowallek wrote:
On Tue, 19 May 2009 09:11:04 +1000, Ian Watkins
<watki...@ozonline.com.au> wrote:


Has anyone else found a problem with the inability of the web page
creator to create the correct HTML code when including a JPEG image in
an individual page. I have tried to create web pages with a JPEG image
only to have Legacy record  the JPEG image as a JPG file. (3 alpha
instead of a 4 alpha file extension).  I have reported the problem to
Legacy.

What version of Legacy and what style of web page are you creating?

My experience is that Legacy will copy the image over to the folder you
specify on the Project tab. In the process it will change the file's
extension from .jpeg to .jpg. The links in the HTML point to .jpg, as
they should.

IOW, I cannot duplicate your problem.


Thanks for your response Dennis

I store all my images in a directory on c drive. Also on c drive is the
legacy directory - two separate directories each with many folders.

The images I use are JPEG files not JPG files.

I add the JPEG images to an individuals photo gallery in the normal way
- either individually or via the picture center. All OK so far
(Initially the picture center would not recognise a JPEG file however
this has been corrected by Legacy when I pointed out the problem to them).

My web site is set up with images in one folder and the web pages in
another folder (mirroring the structure I have on my PC). The images I
want to use on my web site are transferred to the web image folder
withot change - ie they are transferred as JPEG images.

When I create web pages using the Legacy "Create Web Pages" option
Legacy creates the pages OK except that Legacy changes the image
extension from JPEG to JPG.

I now have several hundred images to add to my web page and do not want
to have to individually change each JPEG extension to a JPG extension.

As JPEG extension are quite common I do not see why Legacy cannot fix
the problem.

Regards

Ian Watkins





Legacy User Group guidelines:
   http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages:
   http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp









Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp







Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp



Reply via email to