There seems to be some misperception about my SVG font update post. 
Let me clarify.

In the beginning of computer programming in order to transmit words 
to the monitor, applications needed to have screen fonts embedded 
within the software. Later when fonts became accessible from the 
clients computer embedded fonts were not needed.

In traditional web design when a graphic image is required, like a 
menu button, a graphic image is created specifically for the purpose. 
Henceforth, if you need five different menu buttons you require five 
distinct image files. Typically these five images were created as 
pixel based images and consumed file size and required storage space.

SVG allows for smaller file size and reduces the need for external 
storage of data files, but even if the buttons are basically the same 
construction with just different wording they require the placement 
of five specific and separate image path data elements within the 
document combined with five separate text descriptions.

This is inefficient and my post was intended to show a solution that 
allows an SVG element to be in multiple locations at the same time 
from a single data path. Not only can the element exist in multiple 
locations from this single written data path, but the elements can 
all have different size, color and other attributes.

SVG is a very robust and precise technology that purports to allow me 
to utilize font technology to transmit graphic elements for multiple 
usages. I purposely created a large and complex file to push (Shove?) 
SVG and test this hypothesis. 

I brought this to the attention of this group only to show the 
abilities of today's browsers to render this file. I do not support 
one browser over another and as a matter of fact do not use any of 
the browsers reviewed.

>From my post feedback was received that said there was a problem with 
my use of the use function. I did not understand this as I checked my 
code and could find no fault. Turns out that my ISP uses a web based 
upload feature that continually corrupted my ASCII file uploads for 
some strange and unknown reason. The point being that I would not 
have known of this without the feedback and because of it I was able 
to fix the problem.

That is the reason I brought this to the groups attention. By showing 
the deficiencies in the rendering of the file by different browsers I 
hoped that it would help in motivating the people responsible to fix 
the problems. Shooting the messenger is not productive to 
promulgating SVG or your choice of browser. Don't make excuses or 
defend a defective implementation, just fix the problems.

I hope that the group does not become fractured into different 
classes, where help and assistance is given based on the web browser 
you use.

Sincerely;
James





------------------------------------

-----
To unsubscribe send a message to: [EMAIL PROTECTED]
-or-
visit http://groups.yahoo.com/group/svg-developers and click "edit my 
membership"
----Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/svg-developers/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/svg-developers/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[EMAIL PROTECTED] 
    mailto:[EMAIL PROTECTED]

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Reply via email to