<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hoi GerardM,<br>
<br>
Here's my thoughts of the different topics...<br>
<br>
<br>
SVG versus PNG<br>
----------------------<br>
Right now we're using PNG images to create sign images. These images
do not scale well. They have SSS ID numbers in the format of
xx-xx-xxx-xx-xx-xx. We need to organize and produce SVG files for most
of the current IMWA. Some need to be cleaned up like the white palm
facings. Each SVG for a symbol, or set of symbols needs to be in a
file. We can have each SVG in it's own file. We can pack all of the
SVGs into one file (but this may be too large for older applications).
Or we can break the SVGs into subsets.<br>
<br>
SVG and printing<br>
-----------------------<br>
By the time SVG is ready, we'll be able to switch the printing for
books and articles to use the better graphics. There may need to be a
conversion between the IMWA 1.3 and the SSS ID numbers used for the
IMWA 2.0 (or is it 1.4), but we'll just need to keep a track of this.<br>
<br>
SVG and Client Computer<br>
----------------------------------<br>
We'll need a stand alone viewer for people to use offline. The SVGs
will be perfect for this. The first option is for each client to
download a copy of the SVG files. The second option is to use the
SVGs on the server to create superior images that will be sent to the
client. We'll need to analyze the best way to transfer information.
How much can we compress the data or image stream? <br>
<br>
Unicode<br>
-----------------------<br>
MovementWriting in general needs a Unicode platter of 56 thousand
symbol places. Each symbol should get it's own space, or be logically
combined some how. It's going to be political to get a new platter
opened, but the existing 256 spaces in a nearly full platter are not
enough.<br>
<br>
Unicode and SVG<br>
-----------------------<br>
Once each symbol has a unique number, we can create font files for
SignWriting. We may be able to have a single font file, or we may need
multiple font files. Since we'll already have the SVGs completed, we
can use the SVG style fonts. This whole process will be repackaging.
There should be automated tools that can help. Maybe even font
experts...<br>
<br>
Regards,<br>
-Steve<br>
<br>
<br>
GerardM wrote:
<blockquote
cite="mid:41a006820705010614u2f003549o3176774a9a57b202@mail.gmail.com"
type="cite">Hoi,<br>
When it comes to Unicode, there are two questions relevant to me. <br>
<ul>
<li>How do we get all the SignWriting symbols in Unicode.</li>
<li>Will having the SignWriting symbols in SVG help the move of the
symbols into Unicode
</li>
</ul>
I start off by stating that I am ignorant about SignWriting, but when I
look at the website I find fifty base figures that can be manipulated
in some fifteen ways. If I have this correctly, it means that all
symbols and UNICODE glyphs will be based on these. If this is true, it
may mean that we could start with a quality SVG and result in a glyph
that is acceptable for use in UNICODE. Obviously I do not know and I am
probably overly optimistic, but I am sure you will tell me if I am.. :)
<br>
<br>
Thanks,<br>
GerardM<br>
<br>
<a moz-do-not-send="true"
href="http://www.signbank.org/SignPuddle1.5/signtext.php">http://www.signbank.org/SignPuddle1.5/signtext.php</a><br>
</blockquote>
</body>
</html>