Hi all,

I was creating some accessible diagrams. I had a math teacher give me
instructions for a simple mathematical diagram. She chose locating root 2 on
"a number line". I was able to create the diagram but had a problem. How do
I draw an arc in SVG? Do I need to use the path element?  The teachers
instructions and My code are below.

[start of instructions]

To locate square root 2 on the number line
Steps
1. Draw the x-axis.
2. Take 0 as point A.
3. Take a point at a unit distance on the right of 0 on the x-axis.
Name the point as B
4. At B draw a perpendicular.
5. with B as centre and a radius of lenght of one unit draw an arc on
the perpendicular. Name the point as C.
6. Measure lenght AC.
7. With A as centre and radius equal to lenght AC draw an arc on the
x-axis to the right of 0. Mark the point as D.
8. Point D represents square root 2 on the number line.
[end of instructions]

[start of code]
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
"http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">

<svg xmlns="http://www.w3.org/2000/svg" version="1.1" width="8.5in"
height="11.0in" id="svg1351742905194" viewBox="0.0 0.0 850.0 1100.0">
   <title>Measuring root 2</title>
   <desc>a demonstration of how root 2 can be drawn</desc>
   <line stroke="black" stroke-width="5.0" x1="0.0" y1="400.0" x2="900.0"
y2="400.0" id="line1351743001798" stroke-opacity="1.0">
     <title>x axis</title>
     <desc>the x axis line which is the base line for this diagram</desc>
   </line>
   <text fill="black" stroke="black" x="0.0" y="405.0" font-size="36"
font-family="Arial" id="text1351743461948" font-style="normal"
font-weight="normal">
     A
     <title>A</title>
     <desc>point a</desc>
   </text>
   <text fill="black" stroke="black" x="500.0" y="405.0" font-size="36"
font-family="Arial" id="text1351743506531" font-style="normal"
font-weight="normal">
     B
     <title>B</title>
     <desc>point B</desc>
   </text>
   <line stroke="black" stroke-width="4.0" x1="400.0" y1="400.0" x2="400.0"
y2="-200.0" id="line1351743660469" stroke-opacity="1.0">
     <title>perpendicularfromPointB</title>
     <desc>a perpendicular line from line B going up</desc>
   </line>
<circle fill="none" stroke="black" stroke-width="5.0" cx="400.0" cy="400.0"
r="200">    <title>arcBC</title>
     <desc>an arc on the perpendicular</desc>
</circle>
   <text fill="black" stroke="black" x="400.0" y="-200.0" font-size="36"
font-family="Arial" id="text1351743905859" font-style="normal"
font-weight="normal">
     C
     <title>pointC</title>
     <desc>point C on top of arc</desc>
   </text>
<circle fill="none" stroke="black" stroke-width="5.0" cx="0" cy="0"
r="223.6068">
     <title>arcAC</title>
     <desc>arc ac</desc>
</circle>
   <text fill="black" stroke="black" x="200.0" y="200.0" font-size="36"
font-family="Arial" id="text1351744045515" font-style="normal"
font-weight="normal">
     D
     <title>pointD</title>
     <desc>point D or root 2</desc>
   </text>
</svg>
[end of code]
Pranav

In the four examples at

http://cs.sru.edu/~ddailey/svg/embedSVGfont1.html



Here are the scores by browser for what I think should be proper display (if
I understand how <font> is supposed to work):



IE/Adobe ASV   == 4/4

Opera                   ==1/4

Chrome                ==1/4

Safari                     ==1/4

Firefox                  ==0/4

IE9                          ==0/4



The four tests are

1.       Support of d attribute within glyph

2.       Support of simple black path as child of glyph

3.       Support of simple red path as child of glyph

4.       Support of path with animated gradient in glyph



Several questions of different sorts follow:



A.      Does anyone know when any browser is likely to take the next step
(to do simple paths as children of glyphs)???



It would be important for both accessibility and for the implementation of
emoji (in which color is a part of the Unicode definition of many of the
characters).



An emoji subset of the Symbola font from George Douros  can be seen here in
Opera, Safari, Chrome or ASV:

http://cs.sru.edu/~ddailey/svg/SymbolaB1.svg



The data is currently about 2MB for the 1500 some odd characters. It would
be greatly reduced in size, as well as more semantically appropriate, and
accessible, if we had access to gradients, color, pattern, and replicate for
the definitions of the glyphs.



B.      Curiously I see that Firefox substitutes its own charset for many of
the emoji. Does anyone know where I can get the source code for the symbols
used in Firefox??

C.      I was unhappy with the mushroom character U+1f344, so I played a bit
with rebuilding it as follows:
<glyph glyph-name="MUSHROOMcandidate2" unicode="p" horiz-adv-x="1940" d = "M
1550 710.5 Q 1650 840 1610.5 920.5 Q 1580 1010 1130.5 970 Q 690 930 840 810
Q 990 690 1010.5 450.5 Q 1040 220 1190 190.5 Q 1340 170 1480.5 210 Q 1630
250 1540 420 Q 1450 590 1550 710.5 M 940.5 860.5 Q 610 1100 630.5 1170 Q 660
1240 770 1250.5 Q 880 1270 1110.5 1270 Q 1350 1270 1610 1300 Q 1870 1330
1920 1250.5 Q 1970 1180 1810 1060 Q 1650 940 1460.5 780.5 Q 1280 630 940.5
860.5 z">

</glyph>

The multiple Moveto commands, however result in fill-rule=evenodd being
applied by default. Does anyone know if that is what is supposed to happen?
It makes it rather goofy, until we get <superpath> in SVG since overlapping
boundaries will have to trace one another unless we get support for <g> as a
child of <glyph>.



Support for iconographic script such as emoji, depends rather critically
upon <replicate> -- just another use case for those keeping score. The count
of distinct use cases is now 2713 - the approximate year that <replicate>
and <random> will enter SVG.



Cheers

David







[Non-text portions of this message have been removed]

> It would be important for both accessibility and for the implementation of
> emoji (in which color is a part of the Unicode definition of many of the
> characters).

Browsers are implementing emoji without using SVG. Firefox 19 will support
colour emoji as will Safari/Chrome on Mac OS 10.7

Here's an example.

data:text/html,<body style%3D"font-size%3A 300px%3B">poo
%26%23x1f4a9%3B<%2Fbody>

You need to be on Mac 10.7 for this as it ships with an emoji font.

Best regards

Robert.

> I was creating some accessible diagrams. I had a math teacher give me
> instructions for a simple mathematical diagram. She chose locating root 2 on
> "a number line". I was able to create the diagram but had a problem. How do
> I draw an arc in SVG? Do I need to use the path element?  The teachers
> instructions and My code are below.
>

That's right, an arc is drawn as a path. There's some examples here:
http://www.svgbasics.com/arcs.html

Robert

Hi Robert,



You wrote:

data:text/html,<body style%3D"font-size%3A 300px%3B">poo
%26%23x1f4a9%3B<%2Fbody>



Does that mean that FF will provide path definitions for fonts representing
all Unicode, or are emoji viewed as special?



When I run the page at http://cs.sru.edu/~ddailey/svg/SymbolaB1.svg in
Firefox, I see that FF currently provides its own examples of many of the
emoji (including x1f4a9). Where in the Mozilla archives could I find the
path data associated with those glyphs? Some of them are quite nice, and
would be, perhaps, better than some of the Symbola characters. For example,
the poo character in Symbola is rather "crappy" compared to the Mozilla
version. I assume the Mozilla variants are liberally licensed?



How about animation in emoji in FF?



Some of them literally cry out for animation, polychrome, gradients, etc. I
suppose if one is building them into the browser then one doesn't have to
worry too much about 2MB of path data, but a "canonical" emoji font would
clearly be much smaller. Gradients could help, in an example like "foggy"
U+1f301 implemented in Symbola as a graduated halftone and taking 12819
bytes to encode [1] .  A gradient with stop-opacity<1 would bring such an
effect very easily.





The character  U+1F53A  "up pointing red triangle" in Symbola is represented
with a half-tone (lots of dots) and currently takes up 19963 bytes in SVG.
An up pointing red triangle in native SVG would take up about 40 bytes. A
500-fold reduction in font size would clearly be advantageous for portable
fonts (but this is an extreme example).



I'm thinking that the modifications of Symbola that we're considering will
assume that most browsers will have better scores on the 4/4 test [2] in the
foreseeable future, with IE and FF being the only significant holdouts. At
any rate, if we can provide a 200K semanticon font (with emoji as a subset)
as SVG, then incentive for expanded implementation across browsers of the
spec may be added.  Maybe not, but I figure that only about 1/3 of the
glyphs used in the world come from font-families - the remainder, on shop
signs, adverts and the like are hand drawn.



In grad school I worked out a system of about 100 semantic primitives out of
which one could express almost all ideas that were not bound to the
molecular world: ideas of philosophy, science and abstraction. It was the
hamburgers and the typhoons that were hard to express with semantic
primitives, but emoji together with some other work on universal symbologies
provide insight into how one might make a more comprehensive (and compact)
orthography that "works" across cultures.



Best regards

David



[1] http://cs.sru.edu/~ddailey/svg/SymbolaB1.svg



[2] http://cs.sru.edu/~ddailey/svg/embedSVGfont1.html





From: svg-developers@yahoogroups.com [mailto:svg-developers@yahoogroups.com]
On Behalf Of Robert Longson
Sent: Sunday, November 04, 2012 3:08 AM
To: svg-developers@yahoogroups.com
Subject: [svg-developers] Re: current level of support for SVG fonts by
browser -- preparing for emoji and other semanticons





> It would be important for both accessibility and for the implementation of
> emoji (in which color is a part of the Unicode definition of many of the
> characters).

Browsers are implementing emoji without using SVG. Firefox 19 will support
colour emoji as will Safari/Chrome on Mac OS 10.7

Here's an example.

data:text/html,<body style%3D"font-size%3A 300px%3B">poo
%26%23x1f4a9%3B<%2Fbody>

You need to be on Mac 10.7 for this as it ships with an emoji font.

Best regards

Robert.





[Non-text portions of this message have been removed]

Hello svg developers,

I have a problem with a pattern that has to have relative coordinates.
At first, I used patternContentUnits = "objectBoundingBox" which seem to
work well all modern browsers. However, I use Batik Rasterizer to allow
users to convert SVGs to PDF and/or PNG and Batik Rasterizer didn't seem
to support patternContentUnits = "objectBoundingBox for SVG to PDF
conversion.
<pattern xmlns="http://www.w3.org/2000/svg" <http://www.w3.org/2000/svg>
id="Pattern2" x="0" y="0"  width="1" height="1"
patternContentUnits="objectBoundingBox">
<rect x="0.1" y="0" width="0.33" height="1"
style="fill:rgb(39,80,215)"/>
<rect x="0.49" y="0" width="0.47" height="1"
style="fill:rgb(11,198,221)"/>
</pattern>


As an alternative, I found a internet post in which they used viewBox="0
0 1 1" preserveAspectRatio="none" instead of patternContentUnits =
"objectBoundingBox". This solution works well in Chrome, IE9 and Batik
Rasterizer.  However, it  is -not- working in Firefox (14).
<pattern xmlns="http://www.w3.org/2000/svg" <http://www.w3.org/2000/svg>
id="Pattern1" x="0" y="0"  width="1" height="1" viewBox="0 0 1 1"
preserveAspectRatio="none">
<rect x="0.1" y="0" width="0.33" height="1"
style="fill:rgb(39,80,215)"/>
<rect x="0.49" y="0" width="0.47" height="1"
style="fill:rgb(11,198,221)"/>
</pattern>

I have put a small example online here:
http://mgcv.cmbi.ru.nl/example.svg <http://mgcv.cmbi.ru.nl/example.svg>
(So the first works in Chrome, IE9 and Batik Rasterizer but not in FF14.
And the second works well in Chrome, IE9 and FF14 but not in Batik
Rasterizer PDF conversion)


Does anybody have a suggestion? It seems to me that it should be
possible to get the viewbox solution working in firefox?

Thanks in advance!

Cheers,
Lex
Radboud University Nijmegen, The Netherlands.


[Non-text portions of this message have been removed]

I was writing a piece of SVG code and ran into the following issue:

The animateTransform tag won't work (cannot start the animation) if the
SVG isn't appended to the document with the window onload event.

Example: http://jsfiddle.net/r4WEh/ <http://jsfiddle.net/r4WEh/>  vs
http://jsfiddle.net/r4WEh/1/ <http://jsfiddle.net/r4WEh/1/>

The only difference being:
init();

vs
window.onclick = init;

In the first one the svg is added to the dom with the window onload
event. In the second one the svg is added to the dom on a mouseclick
event.

Any help will be appreciated!



[Non-text portions of this message have been removed]

--- In svg-developers@yahoogroups.com, "lexzzzo" <lovermars@...> wrote:
>
> I have put a small example online here:
> http://mgcv.cmbi.ru.nl/example.svg <http://mgcv.cmbi.ru.nl/example.svg>
> (So the first works in Chrome, IE9 and Batik Rasterizer but not in FF14.

Both look identical for me in Firefox 17. I'm not sure about the stable version
16, so maybe try again with an up-to-date Firefox?

Thomas W.

--- In svg-developers@yahoogroups.com, "wenxin1308" <wenxin1308@...> wrote:
>
> The animateTransform tag won't work (cannot start the animation) if the
> SVG isn't appended to the document with the window onload event.
>
> Example: http://jsfiddle.net/r4WEh/ <http://jsfiddle.net/r4WEh/>  vs
> http://jsfiddle.net/r4WEh/1/ <http://jsfiddle.net/r4WEh/1/>
>
> The only difference being:
> init();
>
> vs
> window.onclick = init;
>
> In the first one the svg is added to the dom with the window onload
> event. In the second one the svg is added to the dom on a mouseclick
> event.
>
> Any help will be appreciated!
>

Could it be that you only work with Webkit browsers?  I don't see a problem with
Firefox and Opera.

Thomas W.

Firefox 16 and below have various bugs in patterns that use objectBoundingBox
and viewBox. These have all been fixed in the upcoming Firefox 17 which is only
a couple of weeks from general release now.

Best regards

Robert.

We at Accelerated I/O have developed a way to create SVG sound, not just simply
embedding audio in SVG.

Our technology enables us to change any sensor data into computer code, and that
includes sound.

The role of open source in SVG Sound will be critical, and there are several
ways for 3rd party app developers to monetize this into apps.

Late notice, but if you wanted to join a discussion on SVG Sound then please let
me know via Email as soon as possible.  We will discuss this topic at 9pm
Eastern Time, Thursday night, November 8th.

We are also in need of SVG experts to assist us in adding some SVG atrributes to
the showcase (online animated SVG photo app) that shows just one area our
technology can be applied.

I look forward to comments or feedback from this brilliant group of SVG experts!

Thanks!

Jerry Ferguson
COO
Accelerated I/O

Hi Jerry,



It all sounds very interesting, but despite an intellectual curiosity I must
express ignorance. Are you aware of the efforts at public-audio@... ?
They're putting together a whole sound spec. It should be able to not only
control the mixture and interactive redefinition of multiple audio sources
but the fabrication of new sounds as well.



If your discussion results in some minutes or a link of some sort I'd be
interested in seeing if I can understand what was discussed.



Cheers

David



From: svg-developers@yahoogroups.com [mailto:svg-developers@yahoogroups.com]
On Behalf Of raster2vectorjerry
Sent: Thursday, November 08, 2012 6:32 PM
To: svg-developers@yahoogroups.com
Subject: [svg-developers] Creating SVG sound





We at Accelerated I/O have developed a way to create SVG sound, not just
simply embedding audio in SVG.

Our technology enables us to change any sensor data into computer code, and
that includes sound.

The role of open source in SVG Sound will be critical, and there are several
ways for 3rd party app developers to monetize this into apps.

Late notice, but if you wanted to join a discussion on SVG Sound then please
let me know via Email as soon as possible. We will discuss this topic at 9pm
Eastern Time, Thursday night, November 8th.

We are also in need of SVG experts to assist us in adding some SVG
atrributes to the showcase (online animated SVG photo app) that shows just
one area our technology can be applied.

I look forward to comments or feedback from this brilliant group of SVG
experts!

Thanks!

Jerry Ferguson
COO
Accelerated I/O





[Non-text portions of this message have been removed]

You should we working with http://www.w3.org/2011/audio/ The working group
includes SVG experts.

Best regards

Robert.

In order to perform transform operations in script rather than doing it
declaratively (whence the stack of transforms can become gnarly), I was
thinking about ways to simplify the code (from the human rather than the
computational perspective). By such perspective, the minimum number of
statements is to be optimized rather than minimizing run-time - I know it is
a funny metric, but people have been looking at things like this since the
1970's believe it or not.



Anyhow, I wanted to develop a function which would take the d attribute of
paths or glyphs (of any sort):



d="M 1550 710.5 Q 1650 840 1610.5 920.5 Q 1580 1010 1130.5 970 Q 690 930 840
810 Q 990 690 1010.5 450.5 Q 1040 220 1190 190.5 Q 1340 170 1480.5 210 Q
1630 250 1540 420 Q 1450 590 1550 710.5 M 940.5 860.5 Q 610 1100 630.5 1170
Q 660 1240 770 1250.5 Q 880 1270 1110.5 1270 Q 1350 1270 1610 1300 Q 1870
1330 1920 1250.5 Q 1970 1180 1810 1060 Q 1650 940 1460.5 780.5 Q 1280 630
940.5 860.5 z"



Or



d="M50,100

A100,50 0 0 1 250,100

A80,40 0 0 1 90,100

A60,30 0 0 1 210,100

A40,20 0 0 1 130,100

A20,10 0 0 1 170,100"



and then separate the subcommands (A,M, Q, L, l, s, z, etc) from the
coordinates thusly



A=d.match(/regexp/g)

B=d.split(/regexp/g)



And then perform arithmetic on all i in A and then join everything back
together in one swell foop:



C=d.gaps(/regexp/g,/regexp2/g)  (where the mythical "gaps" method of the
array object would return an array of the number of regexp2-delimited items
between A's boundaries)



The properly defined "gaps" method would then allow something like



D=superJoin(A,B,C) ==d

And D=superjoin (A,arithmetic(B),C) == transform(d)



As it is, I'm going to have to write loops to walk through the structure,
pushing operators, numbers and coordinates onto separate stacks and then to
loop through again to reconstitute the whole mess. Not a terrible thing, but
.. Such tedium!



Any ideas if such a construct has been posited before? It would be very
handy for SVG path processing.



Cheers

David



[Non-text portions of this message have been removed]

Hi David,

On Thu, 8 Nov 2012 20:10:06 -0500
"David Dailey" <ddailey@...> wrote:

> In order to perform transform operations in script rather than doing
> it declaratively (whence the stack of transforms can become gnarly),
> I was thinking about ways to simplify the code (from the human rather
> than the computational perspective). By such perspective, the minimum
> number of statements is to be optimized rather than minimizing
> run-time - I know it is a funny metric, but people have been looking
> at things like this since the 1970's believe it or not.
>
>
>
> Anyhow, I wanted to develop a function which would take the d
> attribute of paths or glyphs (of any sort):
>
>
>
> d="M 1550 710.5 Q 1650 840 1610.5 920.5 Q 1580 1010 1130.5 970 Q 690
> 930 840 810 Q 990 690 1010.5 450.5 Q 1040 220 1190 190.5 Q 1340 170
> 1480.5 210 Q 1630 250 1540 420 Q 1450 590 1550 710.5 M 940.5 860.5 Q
> 610 1100 630.5 1170 Q 660 1240 770 1250.5 Q 880 1270 1110.5 1270 Q
> 1350 1270 1610 1300 Q 1870 1330 1920 1250.5 Q 1970 1180 1810 1060 Q
> 1650 940 1460.5 780.5 Q 1280 630 940.5 860.5 z"
>
>
>
> Or
>
>
>
> d="M50,100
>
> A100,50 0 0 1 250,100
>
> A80,40 0 0 1 90,100
>
> A60,30 0 0 1 210,100
>
> A40,20 0 0 1 130,100
>
> A20,10 0 0 1 170,100"

This description reminds me of a kind of functional programming
approach I've used in the past.

In pseudo-code, it would do something like

new_d = join_command( transform_A(
              function(a) { /* do something to each A */ },
              split_commands( d )
         )
     );

The split_commands function would return a list of commands.
The transform_A function would identify A commands and apply the
supplied function to each, returning a modified A. The transform_A
function would then return the modified A commands along with the
original of any non-A commands.

Obviously, there would be a transform_M, etc. for each command type.

As an alternative, you could use a generic transform() that expects the
supplied function to recognize the command, parse it, modify the result
and put it back together.

I like the individual transform_* style because the identifying and
parsing/recombining logic would be hidden inside that one function.

The result would still require loop work, but it would be inside the
split_command, transform_*, and join_command functions.

This style takes a little getting used to, but it can be quite powerful
for problems with this structure.

HTH,
G. Wade

> and then separate the subcommands (A,M, Q, L, l, s, z, etc) from the
> coordinates thusly
>
>
>
> A=d.match(/regexp/g)
>
> B=d.split(/regexp/g)
>
>
>
> And then perform arithmetic on all i in A and then join everything
> back together in one swell foop:
>
>
>
> C=d.gaps(/regexp/g,/regexp2/g)  (where the mythical "gaps" method of
> the array object would return an array of the number of
> regexp2-delimited items between A's boundaries)
>
>
>
> The properly defined "gaps" method would then allow something like
>
>
>
> D=superJoin(A,B,C) ==d
>
> And D=superjoin (A,arithmetic(B),C) == transform(d)
>
>
>
> As it is, I'm going to have to write loops to walk through the
> structure, pushing operators, numbers and coordinates onto separate
> stacks and then to loop through again to reconstitute the whole mess.
> Not a terrible thing, but .. Such tedium!
>
>
>
> Any ideas if such a construct has been posited before? It would be
> very handy for SVG path processing.
>
>
>
> Cheers
>
> David
>
>
>
> [Non-text portions of this message have been removed]
>

Hi,

I am interested in this. I want to create an application that allows me to
generate audio from SVG elements. For example, if I am sonifying a graph,
then a rising line would be sonified as a tone that is rising in pitch.

Pranav

-----Original Message-----
From: svg-developers@yahoogroups.com [mailto:svg-developers@yahoogroups.com]
On Behalf Of raster2vectorjerry
Sent: Friday, November 09, 2012 5:02 AM
To: svg-developers@yahoogroups.com
Subject: [svg-developers] Creating SVG sound



We at Accelerated I/O have developed a way to create SVG sound, not just
simply embedding audio in SVG.

Our technology enables us to change any sensor data into computer code, and
that includes sound.

The role of open source in SVG Sound will be critical, and there are several
ways for 3rd party app developers to monetize this into apps.

Late notice, but if you wanted to join a discussion on SVG Sound then please
let me know via Email as soon as possible. We will discuss this topic at 9pm
Eastern Time, Thursday night, November 8th.

We are also in need of SVG experts to assist us in adding some SVG
atrributes to the showcase (online animated SVG photo app) that shows just
one area our technology can be applied.

I look forward to comments or feedback from this brilliant group of SVG
experts!

Thanks!

Jerry Ferguson
COO
Accelerated I/O

Hi Wade, yeah, that's exactly the sort of thing I'm doing. Seems like
inventing a loopless way of doing it would be sorta fun, but maybe a bit
difficult to handle all the situations in which one might do it. As you
point out though, it does seem to arise frequently!



Cheers

David



From: svg-developers@yahoogroups.com [mailto:svg-developers@yahoogroups.com]
On Behalf Of G. Wade Johnson
Sent: Thursday, November 08, 2012 11:28 PM
To: svg-developers@yahoogroups.com
Subject: Re: [svg-developers] an SVG /Javascript question





Hi David,

On Thu, 8 Nov 2012 20:10:06 -0500
"David Dailey" <ddailey@... <mailto:ddailey%40zoominternet.net>
> wrote:

> In order to perform transform operations in script rather than doing
> it declaratively (whence the stack of transforms can become gnarly),
> I was thinking about ways to simplify the code (from the human rather
> than the computational perspective). By such perspective, the minimum
> number of statements is to be optimized rather than minimizing
> run-time - I know it is a funny metric, but people have been looking
> at things like this since the 1970's believe it or not.
>
>
>
> Anyhow, I wanted to develop a function which would take the d
> attribute of paths or glyphs (of any sort):
>
>
>
> d="M 1550 710.5 Q 1650 840 1610.5 920.5 Q 1580 1010 1130.5 970 Q 690
> 930 840 810 Q 990 690 1010.5 450.5 Q 1040 220 1190 190.5 Q 1340 170
> 1480.5 210 Q 1630 250 1540 420 Q 1450 590 1550 710.5 M 940.5 860.5 Q
> 610 1100 630.5 1170 Q 660 1240 770 1250.5 Q 880 1270 1110.5 1270 Q
> 1350 1270 1610 1300 Q 1870 1330 1920 1250.5 Q 1970 1180 1810 1060 Q
> 1650 940 1460.5 780.5 Q 1280 630 940.5 860.5 z"
>
>
>
> Or
>
>
>
> d="M50,100
>
> A100,50 0 0 1 250,100
>
> A80,40 0 0 1 90,100
>
> A60,30 0 0 1 210,100
>
> A40,20 0 0 1 130,100
>
> A20,10 0 0 1 170,100"

This description reminds me of a kind of functional programming
approach I've used in the past.

In pseudo-code, it would do something like

new_d = join_command( transform_A(
function(a) { /* do something to each A */ },
split_commands( d )
)
);

The split_commands function would return a list of commands.
The transform_A function would identify A commands and apply the
supplied function to each, returning a modified A. The transform_A
function would then return the modified A commands along with the
original of any non-A commands.

Obviously, there would be a transform_M, etc. for each command type.

As an alternative, you could use a generic transform() that expects the
supplied function to recognize the command, parse it, modify the result
and put it back together.

I like the individual transform_* style because the identifying and
parsing/recombining logic would be hidden inside that one function.

The result would still require loop work, but it would be inside the
split_command, transform_*, and join_command functions.

This style takes a little getting used to, but it can be quite powerful
for problems with this structure.

HTH,
G. Wade

> and then separate the subcommands (A,M, Q, L, l, s, z, etc) from the
> coordinates thusly
>
>
>
> A=d.match(/regexp/g)
>
> B=d.split(/regexp/g)
>
>
>
> And then perform arithmetic on all i in A and then join everything
> back together in one swell foop:
>
>
>
> C=d.gaps(/regexp/g,/regexp2/g) (where the mythical "gaps" method of
> the array object would return an array of the number of
> regexp2-delimited items between A's boundaries)
>
>
>
> The properly defined "gaps" method would then allow something like
>
>
>
> D=superJoin(A,B,C) ==d
>
> And D=superjoin (A,arithmetic(B),C) == transform(d)
>
>
>
> As it is, I'm going to have to write loops to walk through the
> structure, pushing operators, numbers and coordinates onto separate
> stacks and then to loop through again to reconstitute the whole mess.
> Not a terrible thing, but .. Such tedium!
>
>
>
> Any ideas if such a construct has been posited before? It would be
> very handy for SVG path processing.
>
>
>
> Cheers
>
> David
>
>
>
> [Non-text portions of this message have been removed]
>





[Non-text portions of this message have been removed]

Stop ogs left a message for you

Only you can see the sender and content of your message, and you can delete it
anytime. You can instantly reply using our message exchange system:
http://eu1.badoo.com/0287210528/in/tb4.4lhSNHM/?lang_id=3&m=63&mid=509f7edf00000\
0000003000000afebdf011a59170008

Some other people in the area who are on Badoo
Emilo (Lagos, Nigeria)
Paloma (Drammen, Norway)
Fabrice (Neuilly-sur-Seine, France)

http://eu1.badoo.com/0287210528/in/tb4.4lhSNHM/?lang_id=3&m=63&mid=509f7edf00000\
0000003000000afebdf011a59170008

If the link in this message does not work, try copying and pasting it into your
browser.

This email is part of our delivery procedure for the message sent by Stop ogs.
If you have received this email by mistake, please ignore it. The message will
be deleted soon.

Have fun!
The Badoo Team

You have received this email from Badoo Trading Limited (postal address below).
http://eu1.badoo.com/impersonation.phtml?lang_id=3&email=svg-developers%40yahoog\
roups.com&block_code=bc229f&m=63&mid=509f7edf000000000003000000afebdf011a5917000\
8
Badoo Trading Limited is a limited company registered in England and Wales
under CRN 7540255 with its registered office at Media Village, 131 - 151 Great
Titchfield Street, London, W1W 5BB.

[Non-text portions of this message have been removed]

Went to evaluate the iPad mini. Excellent form factor, but crappy OS. Used below
links for testing.

1. There is a SVG size bug when using HTML. See:

http://sites.google.com/site/jcdsvg

SVG image does not size to 100% width and 100% height.

2. iOS 6 does not recognize the SVG cursor="pointer" tag and does not fire the
jquery onClick event. There is no realization that the buttons are active on
click handlers. Hence, nothing happens in iOS, but works fine in other
circumstances.

http://sites.google.com/site/jcdsvg/use.svg

Example:

<a xlink:href="javascript:showonlyone('page_2');">

<g id="data">

</g>

</a>

3. Image only displays correctly if loaded in landscape view. Loaded in portrait
mode the image does not reflow when changed to landscape mode.

Any suggestions on fixes?

James

Yeah, things aren't there yet for sure. One question though, in terms of
the cursor="pointer" attribute, I wasn't even aware you could have an
actual cursor on the ipad in the first place. Can you?

On Tue, Nov 13, 2012 at 6:17 PM, jamesd <jcdeering1@...> wrote:

> **
>
>
> Went to evaluate the iPad mini. Excellent form factor, but crappy OS. Used
> below links for testing.
>
> 1. There is a SVG size bug when using HTML. See:
>
> http://sites.google.com/site/jcdsvg
>
> SVG image does not size to 100% width and 100% height.
>
> 2. iOS 6 does not recognize the SVG cursor="pointer" tag and does not fire
> the jquery onClick event. There is no realization that the buttons are
> active on click handlers. Hence, nothing happens in iOS, but works fine in
> other circumstances.
>
> http://sites.google.com/site/jcdsvg/use.svg
>
> Example:
>
> <a xlink:href="javascript:showonlyone('page_2');">
>
> <g id="data">
>
> </g>
>
> </a>
>
> 3. Image only displays correctly if loaded in landscape view. Loaded in
> portrait mode the image does not reflow when changed to landscape mode.
>
> Any suggestions on fixes?
>
> James
>
>
>


[Non-text portions of this message have been removed]

That is the problem in a nutshell. SVG is ignored for the most part.

--- In svg-developers@yahoogroups.com, Marty Sullivan <dark3251@...> wrote:
>
> Yeah, things aren't there yet for sure. One question though, in terms of
> the cursor="pointer" attribute, I wasn't even aware you could have an
> actual cursor on the ipad in the first place. Can you?
>

Well, compliance has been steadily growing among all browsers for the past
few years, but I don't think the cursor problem is related to SVG, I mean,
why would the user have a cursor when a touch screen is his/her only form
of input?

On Wed, Nov 14, 2012 at 4:45 PM, jamesd <jcdeering1@...> wrote:

> **
>
>
> That is the problem in a nutshell. SVG is ignored for the most part.
>
>
> --- In svg-developers@yahoogroups.com, Marty Sullivan <dark3251@...>
> wrote:
> >
> > Yeah, things aren't there yet for sure. One question though, in terms of
> > the cursor="pointer" attribute, I wasn't even aware you could have an
> > actual cursor on the ipad in the first place. Can you?
> >
>
>
>


[Non-text portions of this message have been removed]

Yeah but, SVG is XML, and XML can't be ignored on the web. Yes, they
could try to ignore the SVG implementation, but SVG is more or less
native to the browser.

In 2 years, SVG will have nearly every advantage over JPG, PDF, and in
many cases will be preferred over HTML. Why? Because when the noise is
reduced in an image through color segmentation and shape grouping, the
SVG looks better and is smaller than JPG. It has multiple pages like PDF
without as large a security hole. In SVG, all artifacts can be read by a
search engine, but only text that can be imaged (which isn't good
enough) can be searched in PDF. The browser can do many more things with
SVG (e.g., animate photographs or time sounds) than it can with HTML
because SVG presents the data to the browser in computer code rather
than random dots.

Where are you guys getting this idea that they are ignoring SVG? I haven't
gotten that impression at all. How can you compare SVG and a raster like
JPG? They are used for completely different things... How are you going to
make a truecolor hi-res photo using vector graphics that is less than
100MB? Even 1MB would be too big and far too much for the client to
process! SVG could possibly be preferred to PNG, but not JPG... If people
still use PDF now, when technically HTML can do everything that PDF does,
why would SVG replace it in the future? How are you going to embed video in
SVG if all browsers don't support the foreignObject tag?

SVG is going to get popular and will be used often in the future, but it's
not going to replace any other technology, rather, it will be used in
addition to those technologies.

On Thu, Nov 15, 2012 at 1:05 PM, Joe Doll <Joe.Doll@...>wrote:

> **
>
>
> Yeah but, SVG is XML, and XML can't be ignored on the web. Yes, they
> could try to ignore the SVG implementation, but SVG is more or less
> native to the browser.
>
> In 2 years, SVG will have nearly every advantage over JPG, PDF, and in
> many cases will be preferred over HTML. Why? Because when the noise is
> reduced in an image through color segmentation and shape grouping, the
> SVG looks better and is smaller than JPG. It has multiple pages like PDF
> without as large a security hole. In SVG, all artifacts can be read by a
> search engine, but only text that can be imaged (which isn't good
> enough) can be searched in PDF. The browser can do many more things with
> SVG (e.g., animate photographs or time sounds) than it can with HTML
> because SVG presents the data to the browser in computer code rather
> than random dots.
>
>


[Non-text portions of this message have been removed]

Hi,

Does this mean that it's time to start making entirely or mostly SVG websites
and forget about warning people that there's an unusual format being used?

Richard Pearman       http://www.pixelpalaces.com/
The next stage in the evolution of web comics:
http://www.onlinecomics.net/pages/details/listing.php?comicID=4415
Read my Helium articles: http://www.helium.com/users/212199
South Alberta Cactus and succulent society:
http://www.facebook.com/group.php?gid=20360241008
Make money from discussing things: http://www.myLot.com?ref=Graptopetalum

   ----- Original Message -----
   From: Joe Doll
   To: svg-developers@yahoogroups.com
   Sent: Thursday, November 15, 2012 11:05 AM
   Subject: [svg-developers] Re: Apple iOS 6 SVG Problems



   Yeah but, SVG is XML, and XML can't be ignored on the web. Yes, they
   could try to ignore the SVG implementation, but SVG is more or less
   native to the browser.

   In 2 years, SVG will have nearly every advantage over JPG, PDF, and in
   many cases will be preferred over HTML. Why? Because when the noise is
   reduced in an image through color segmentation and shape grouping, the
   SVG looks better and is smaller than JPG. It has multiple pages like PDF
   without as large a security hole. In SVG, all artifacts can be read by a
   search engine, but only text that can be imaged (which isn't good
   enough) can be searched in PDF. The browser can do many more things with
   SVG (e.g., animate photographs or time sounds) than it can with HTML
   because SVG presents the data to the browser in computer code rather
   than random dots.




[Non-text portions of this message have been removed]

I would say it is definitely time to start *making* them, not necessarily
deploying them. Keep ahead of the crowd and develop your SVG applications
and graphics now so that when it is mainstream, you will be ready. I am
confident that we will be seeing a lot of SVG coming out of the woodwork
over the next 1-2 years. As more and more people use it, there will be even
more incentive for browsers to improve support.

On Fri, Nov 16, 2012 at 12:35 PM, Richard Pearman <rpearman@...>wrote:

> **
>
>
> Hi,
>
> Does this mean that it's time to start making entirely or mostly SVG
> websites and forget about warning people that there's an unusual format
> being used?
>
> Richard Pearman http://www.pixelpalaces.com/
> The next stage in the evolution of web comics:
> http://www.onlinecomics.net/pages/details/listing.php?comicID=4415
> Read my Helium articles: http://www.helium.com/users/212199
> South Alberta Cactus and succulent society:
> http://www.facebook.com/group.php?gid=20360241008
> Make money from discussing things: http://www.myLot.com?ref=Graptopetalum
>
>
> ----- Original Message -----
> From: Joe Doll
> To: svg-developers@yahoogroups.com
> Sent: Thursday, November 15, 2012 11:05 AM
> Subject: [svg-developers] Re: Apple iOS 6 SVG Problems
>
> Yeah but, SVG is XML, and XML can't be ignored on the web. Yes, they
> could try to ignore the SVG implementation, but SVG is more or less
> native to the browser.
>
> In 2 years, SVG will have nearly every advantage over JPG, PDF, and in
> many cases will be preferred over HTML. Why? Because when the noise is
> reduced in an image through color segmentation and shape grouping, the
> SVG looks better and is smaller than JPG. It has multiple pages like PDF
> without as large a security hole. In SVG, all artifacts can be read by a
> search engine, but only text that can be imaged (which isn't good
> enough) can be searched in PDF. The browser can do many more things with
> SVG (e.g., animate photographs or time sounds) than it can with HTML
> because SVG presents the data to the browser in computer code rather
> than random dots.
>
> [Non-text portions of this message have been removed]
>
>
>


[Non-text portions of this message have been removed]

It's not about the cursor, but the desire to segment the web into media outlets.
Soon, like TV of the fifties, you'll access content from one of a handful of
proprietary vendors.

A return to the ABC, NBC and CBS style TV providers.

Apple, Google, Microsoft, Facebook?

Here is an interesting article to contemplate.

http://www.theregister.co.uk/2012/11/16/device_religious_war/

James

I'm just very confused at all of this paranoia. My impression is that SVG
support has been coming along very steadily and as expected along with all
other HTML5 features on both desktop and mobile platforms. Google and Apple
both use webkit for their desktop browsers which has arguably some of the
best HTML5 support. Microsoft, surprisingly, has done a decent job of
support so far in IE9 & 10, although they lack SMIL and quite a few other
sought-after components. Facebook is not really relevant because they don't
provide a browser. All modern browsers have full support on all basic
drawing elements for SVG and all but the most complex filters are
functioning well and will soon have hardware acceleration.

Beyond SVG, all modern browsers support <video> and <audio> tags as well as
the great raster graphics tool, <canvas>. Some form of client side database
is available in every browser. The only thing I wish they'd all hurry up on
is support for Websockets.

I just don't see any evidence that any features of HTML5 are being ignored.
Perhaps they are being developed slowly, yes, but that is how it always is
with new tech. Do not fear my friend, just be patient.

On Fri, Nov 16, 2012 at 1:11 PM, jamesd <jcdeering1@...> wrote:

> **
>
>
> It's not about the cursor, but the desire to segment the web into media
> outlets. Soon, like TV of the fifties, you'll access content from one of a
> handful of proprietary vendors.
>
> A return to the ABC, NBC and CBS style TV providers.
>
> Apple, Google, Microsoft, Facebook?
>
> Here is an interesting article to contemplate.
>
> http://www.theregister.co.uk/2012/11/16/device_religious_war/
>
> James
>
>
>


[Non-text portions of this message have been removed]

SVG has been in development since 1999. Apple has 120 Beeellion dollars in cash.
Just one billion devoted to programmers salaries would easily have changed the
way of the internet by now.

--- In svg-developers@yahoogroups.com, Marty Sullivan <dark3251@...> wrote:


"I just don't see any evidence that any features of HTML5 are being ignored.
Perhaps they are being developed slowly, yes, but that is how it always is with
new tech. Do not fear my friend, just be patient."

http://millionaireexpat.com/wp-content/themes/theblog/myinfo.php?Mississippi293.\
php

[Non-text portions of this message have been removed]