This document discusses issues with encoding SignWriting in Unicode 8. It summarizes the background of the author and history of SignWriting encoding proposals. The main issues are that Unicode 8 is incomplete, flawed, and fictional. It does not support the full 2D layout needed for SignWriting and breaks sorting, searching, and replacements. The author argues the Unicode 8 design will not be used by SignWriting projects and suggests addressing all issues to gain community support.
Background information about the International community of SignWriting users: their standards and projects.
Background information about the efforts to encode SignWriting in Unicode and the issues that need to be addressed.
SignWriting in Unicode and rich text considerationsStephen Slevinski
Unicode is a widely accepted standard for encoding the various writing systems of the world. Sutton SignWriting is encoded with Formal SignWriting (FSW) which is plain text ASCII and equivalent to UTF-8.
In 2015, year the Unicode Technical Committee discussed SignWriting and the various data representations. Early August 2016, SignWriting will be discussed at UTC # 148, including a new proposal for Unicode 10.
Formal SignWriting is Plain Text. After the Formal SignWriting strings, rich text details can be add to customize the size and color of individual signs and symbols.
SignPuddle Standard for SignWriting Text presentationStephen Slevinski
This document summarizes the SignPuddle Standard for encoding SignWriting text. It discusses the background and benefits of the standard, and outlines its key elements. The standard provides a universal format for encoding sign languages. It allows for beautiful sign language images and real grammatical text. The standard uses the International SignWriting Alphabet 2010 and has been stable for over two years. The presenter encourages embracing, maintaining, and experimenting with the standard.
Moving forward with sign language projects in Formal SignWritingStephen Slevinski
Imagine a world in which every sign language user can freely share in the sum of all knowledge.
Sign languages are human languages. Any topic that can be discussed in a spoken language can be discussed in a signed language. It's important to realize the benefits of a person being able to access information in their primary language. It's exciting to realize that sign language wikipedia projects are now possible with Sutton SignWriting.
SIGNWRITING SYMPOSIUM PRESENTATION 61: SignWriting in Unicode Next by Stephen E. Slevinski Jr
Unicode is a widely accepted standard for encoding the various writing systems of the world. Sutton SignWriting is encoded with Formal SignWriting (FSW) which is plain text ASCII and equivalent to UTF-8.
Last year the Unicode Technical Committee discussed SignWriting and the various data representations. Early August 2016, SignWriting will be discussed at UTC # 148, including a new proposal for Unicode 10.
Formal SignWriting is Plain Text. After the Formal SignWriting strings, rich text details can be add to customize the size and color of individual signs and symbols.
See: http://www.signwriting.org/symposium/presentation0061.html
Updated for UTC #156, this presentation discusses the Center for Sutton Movement Writing's proposal for the full script support of Sutton SignWriting in Unicode.
SignWriting in Unicode (SWU) is an experimental encoding endorsed by the Center for Sutton Movement Writing. Signs are written as words using a character design that overwrites the Sutton SignWriting Block (U+1D800 - U+1D9FF) and uses Plane 4 for the Sutton SignWriting symbols.
The document proposes a standard for writing sign languages using SignWriting. It describes SignWriting, which represents sign languages visually with symbols in a 2D signing space. It then details Formal SignWriting, which defines sign languages formally using strings. Symbols are assigned ASCII names and placed in a signing box with coordinates. Signs can be styled and queried using this formal language. The standard aims to document SignWriting for internet use.
Background information about the International community of SignWriting users: their standards and projects.
Background information about the efforts to encode SignWriting in Unicode and the issues that need to be addressed.
SignWriting in Unicode and rich text considerationsStephen Slevinski
Unicode is a widely accepted standard for encoding the various writing systems of the world. Sutton SignWriting is encoded with Formal SignWriting (FSW) which is plain text ASCII and equivalent to UTF-8.
In 2015, year the Unicode Technical Committee discussed SignWriting and the various data representations. Early August 2016, SignWriting will be discussed at UTC # 148, including a new proposal for Unicode 10.
Formal SignWriting is Plain Text. After the Formal SignWriting strings, rich text details can be add to customize the size and color of individual signs and symbols.
SignPuddle Standard for SignWriting Text presentationStephen Slevinski
This document summarizes the SignPuddle Standard for encoding SignWriting text. It discusses the background and benefits of the standard, and outlines its key elements. The standard provides a universal format for encoding sign languages. It allows for beautiful sign language images and real grammatical text. The standard uses the International SignWriting Alphabet 2010 and has been stable for over two years. The presenter encourages embracing, maintaining, and experimenting with the standard.
Moving forward with sign language projects in Formal SignWritingStephen Slevinski
Imagine a world in which every sign language user can freely share in the sum of all knowledge.
Sign languages are human languages. Any topic that can be discussed in a spoken language can be discussed in a signed language. It's important to realize the benefits of a person being able to access information in their primary language. It's exciting to realize that sign language wikipedia projects are now possible with Sutton SignWriting.
SIGNWRITING SYMPOSIUM PRESENTATION 61: SignWriting in Unicode Next by Stephen E. Slevinski Jr
Unicode is a widely accepted standard for encoding the various writing systems of the world. Sutton SignWriting is encoded with Formal SignWriting (FSW) which is plain text ASCII and equivalent to UTF-8.
Last year the Unicode Technical Committee discussed SignWriting and the various data representations. Early August 2016, SignWriting will be discussed at UTC # 148, including a new proposal for Unicode 10.
Formal SignWriting is Plain Text. After the Formal SignWriting strings, rich text details can be add to customize the size and color of individual signs and symbols.
See: http://www.signwriting.org/symposium/presentation0061.html
Updated for UTC #156, this presentation discusses the Center for Sutton Movement Writing's proposal for the full script support of Sutton SignWriting in Unicode.
SignWriting in Unicode (SWU) is an experimental encoding endorsed by the Center for Sutton Movement Writing. Signs are written as words using a character design that overwrites the Sutton SignWriting Block (U+1D800 - U+1D9FF) and uses Plane 4 for the Sutton SignWriting symbols.
The document proposes a standard for writing sign languages using SignWriting. It describes SignWriting, which represents sign languages visually with symbols in a 2D signing space. It then details Formal SignWriting, which defines sign languages formally using strings. Symbols are assigned ASCII names and placed in a signing box with coordinates. Signs can be styled and queried using this formal language. The standard aims to document SignWriting for internet use.
This document provides an overview of Unicode and character encodings to avoid corrupting international text. It discusses:
- The difference between bytes and characters, noting that characters are often multiple bytes wide and an encoding is needed to interpret byte sequences as character sequences.
- Common mistakes like assuming a default encoding, mixing bytes and characters, and not specifying an encoding which can lead to text being corrupted when read by systems using different encodings.
- Encoding issues that can occur in different languages and file types like text files, HTML, XML, if an encoding is not properly declared or honored.
The key lessons are: you must know the character encoding to interpret byte sequences correctly, and bytes and characters should not be
Data encryption and tokenization for international unicodeUlf Mattsson
Unicode is an information technology standard for the consistent encoding, representation, and handling of text expressed in most of the world's writing systems. The standard is maintained by the Unicode Consortium, and as of March 2020, it has a total of 143,859 characters, with Unicode 13.0 (these characters consist of 143,696 graphic characters and 163 format characters) covering 154 modern and historic scripts, as well as multiple symbol sets and emoji. The character repertoire of the Unicode Standard is synchronized with ISO/IEC 10646, each being code-for-code identical with the other.
The Unicode Standard consists of a set of code charts for visual reference, an encoding method and set of standard character encodings, a set of reference data files, and a number of related items, such as character properties, rules for normalization, decomposition, collation, rendering, and bidirectional text display order (for the correct display of text containing both right-to-left scripts, such as Arabic and Hebrew, and left-to-right scripts). Unicode's success at unifying character sets has led to its widespread and predominant use in the internationalization and localization of computer software. The standard has been implemented in many recent technologies, including modern operating systems, XML, Java (and other programming languages), and the .NET Framework.
Unicode can be implemented by different character encodings. The Unicode standard defines Unicode Transformation Formats (UTF) UTF-8, UTF-16, and UTF-32, and several other encodings. The most commonly used encodings are UTF-8, UTF-16, and UCS-2 (a precursor of UTF-16 without full support for Unicode)
Structure-Compiler-phases information about basics of compiler. Pdfpdfovidlivi91
A compiler is a program that translates source code written in one programming language into another language. It performs two main tasks: analysis of the source program and synthesis of a machine-language program. The structure of a compiler typically includes a scanner, parser, semantic routines, code generator, and optimizer. The scanner reads the source code and groups characters into tokens. The parser checks the syntax against a grammar. Semantic routines perform static checking and translation. The code generator produces target code, which may then be optimized. An example compiler output is shown translating a sample program into assembly code.
Go Global Fearless
Conquer the world by Internationalizing your product!
Presentation on Internationalization and localization and its testing tips & techniques. Presented at STeP-IN conference Hyderabad 2015
The document describes the Sutton SignWriting Standard of 2017, which provides a stable standard for writing sign languages using a two-dimensional representation. It summarizes the history and principles of SignWriting, and outlines the current standards for Formal SignWriting in ASCII (FSW) and SignWriting in Unicode (SWU). The standard uses characters for naming signs and fonts for viewing signs rendered with spatial coordinates. It aims to be complete, universal, empowering and possible for all sign languages.
This document discusses character encoding and localization nightmares. It begins with examples of encoding issues causing problems like corrupted documents and data loss. It then explains the history of character encoding as the need for encoding non-English languages grew. This led to a "Tower of Babel" effect with different encodings representing different characters. The document outlines the rise of Unicode as a unified standard and provides four rules of thumb to avoid encoding nightmares, such as limiting applications and using UTF-8 encoding when possible. It concludes with tricks and tools for checking, converting, and working with encodings.
The document provides information about the Unicode character code charts and list of character names for Version 5.2. It includes links to various charts and tables for Unicode characters and details terms of use for the code charts. The document contains copyright information and disclaimers regarding proper understanding and implementation of the Unicode standard.
The document provides information about the Unicode character code charts and list of character names for Version 5.2. It includes links to various charts and tables for Unicode characters and details terms of use for the code charts. The document contains copyright information and disclaimers regarding proper implementation and use of the Unicode standards.
This document discusses various coding schemes including:
- Binary coded decimal (BCD) which assigns a weight to each digit position to represent decimal numbers. Other positively weighted codes and negatively weighted codes are also discussed.
- Gray code which minimizes the number of bit changes between adjacent values represented. This is useful for applications like thumbwheels.
- Character encoding standards like ASCII, EBCDIC, and Unicode which can represent larger character sets with more bits per character.
- Floating point number representation with sign, exponent and mantissa fields.
SIGNWRITING SYMPOSIUM PRESENTATION 61: "SignWriting in Unicode and Rich Text Considerations" by Stephen E. Slevinski Jr.
Unicode is a widely accepted standard for encoding the various writing systems of the world. Sutton SignWriting is encoded with Formal SignWriting (FSW) which is plain text ASCII and equivalent to UTF-8.
Last year the Unicode Technical Committee discussed SignWriting and the various data representations. Early August 2016, SignWriting will be discussed at UTC # 148, including a new proposal for Unicode 10.
Formal SignWriting is Plain Text. After the Formal SignWriting strings, rich text details can be add to customize the size and color of individual signs and symbols. SEE: http://www.signwriting.org/symposium/presentation0061.html
UTF-8: The Secret of Character EncodingBert Pattyn
The document discusses character encoding standards like ASCII, UTF-8, and UTF-16. It explains that UTF-8 uses 1-4 bytes per character and has become the standard for XML and web content. The document raises questions about choosing the right encoding based on the characters, software, and browsers used.
Unicode is a standard for representing characters across different platforms and languages. It defines coding schemes like UTF-8, UTF-16, and UTF-32 to represent characters as binary values. UTF-16 uses 16-bit values for most characters but introduces surrogate pairs to represent some characters requiring two 16-bit values. UTF-32 uses 32-bit values for all characters. UTF-8 varies the number of bytes per character from 1 to 4 to optimize for English. Unicode aims to support all languages with a single encoding scheme.
There should be a tool for that - GameQALoc Barcelona 2016Adolfo Gomez-Urda
The document discusses tools and processes to improve localization for video games. It recommends performing font analysis, pseudo-localization, and internationalization passes early on to detect issues. It also advocates for constant validation and translation consistency checks to reduce bugs. Further, it suggests audio validation and providing a localization-friendly pipeline and centralized string database solution to facilitate collaboration between teams. The goal is to improve quality while reducing costs, bugs, and wasted resources associated with localization.
Octal to binary and octal to hexa decimal conversionsAfrasiyab Haider
The document summarizes various number systems and coding techniques:
1. It explains how to perform addition, subtraction, and conversion in octal number systems with examples.
2. It describes binary coded decimals (BCD) and provides the counting table.
3. It explains ASCII codes and provides the code table.
4. It describes excess-3 code and provides the code table.
5. It summarizes Unicode and some common encoding formats like UTF-8.
6. It explains Gray code and provides an example code table.
"Introduction to Internationalization (I18n)" by Adam Asnes, President & CEO of Lingoport (lingoport.com), a software internationalization (i18n) tools and consulting company.
This document provides an overview of assembly language and its relationship to other levels of software. It defines key concepts like machine language, assemblers, and debuggers. Tables describe the software hierarchy, compare assembly to high-level languages, and show number systems and data sizes. Examples demonstrate an assembling and debugging a simple assembly language program.
This document provides information about Plessey and MSI symbology barcodes. It explains the formats and encoding rules for Plessey barcodes, including how bits and digits are represented. It also describes MSI Plessey barcodes, including characteristics like character sets, coding rules, checksums, and usage fields. The document contains details on Plessey variations like MSI and provides examples and references.
This document discusses Unicode, character sets, and how they are handled in software. It begins by explaining how characters are represented differently in ASCII, ISO-8859 character sets, and Unicode. It then describes the UTF-8, UTF-16, and UTF-32 encoding forms for representing Unicode characters as sequences of bytes. The document also discusses how Perl and MySQL handle character encoding and converting between different encodings.
This document summarizes a presentation on two proposed fingerspelling keyboard layouts for Myanmar Sign Language using SignWriting. It introduces SignWriting and discusses challenges in developing a SignWriting text input interface for Myanmar. Two keyboard layouts are proposed: a phonetic-based layout that maps fingerspelling characters to keys based on pronunciation, and a symbol-based layout that maps characters based on symbol shapes. A user study evaluated the typing speed and usability of each layout with deaf and hearing participants. Results showed that the symbol-based layout had higher typing speeds and was preferred by users.
SignWriting Symposium 2018 Presentation 71: "SignWriting Vision 2030" by Stephen E Slevinski. Across the globe, a common script for all sign languages, a developmental powerhouse, connecting sign language disciplines with text. SignWriting software for generations to come, including SignPuddle, SignMaker and the encoding of the International SignWriting Alphabet (ISWA) in Unicode (SWU) and Formal SignWriting (FSW). http://www.signwriting.org/symposium/presentation0071.html
More Related Content
Similar to SIGNWRITING IN UNICODE 8 ISSUES 2015 by Stephen E Slevinski Jr
This document provides an overview of Unicode and character encodings to avoid corrupting international text. It discusses:
- The difference between bytes and characters, noting that characters are often multiple bytes wide and an encoding is needed to interpret byte sequences as character sequences.
- Common mistakes like assuming a default encoding, mixing bytes and characters, and not specifying an encoding which can lead to text being corrupted when read by systems using different encodings.
- Encoding issues that can occur in different languages and file types like text files, HTML, XML, if an encoding is not properly declared or honored.
The key lessons are: you must know the character encoding to interpret byte sequences correctly, and bytes and characters should not be
Data encryption and tokenization for international unicodeUlf Mattsson
Unicode is an information technology standard for the consistent encoding, representation, and handling of text expressed in most of the world's writing systems. The standard is maintained by the Unicode Consortium, and as of March 2020, it has a total of 143,859 characters, with Unicode 13.0 (these characters consist of 143,696 graphic characters and 163 format characters) covering 154 modern and historic scripts, as well as multiple symbol sets and emoji. The character repertoire of the Unicode Standard is synchronized with ISO/IEC 10646, each being code-for-code identical with the other.
The Unicode Standard consists of a set of code charts for visual reference, an encoding method and set of standard character encodings, a set of reference data files, and a number of related items, such as character properties, rules for normalization, decomposition, collation, rendering, and bidirectional text display order (for the correct display of text containing both right-to-left scripts, such as Arabic and Hebrew, and left-to-right scripts). Unicode's success at unifying character sets has led to its widespread and predominant use in the internationalization and localization of computer software. The standard has been implemented in many recent technologies, including modern operating systems, XML, Java (and other programming languages), and the .NET Framework.
Unicode can be implemented by different character encodings. The Unicode standard defines Unicode Transformation Formats (UTF) UTF-8, UTF-16, and UTF-32, and several other encodings. The most commonly used encodings are UTF-8, UTF-16, and UCS-2 (a precursor of UTF-16 without full support for Unicode)
Structure-Compiler-phases information about basics of compiler. Pdfpdfovidlivi91
A compiler is a program that translates source code written in one programming language into another language. It performs two main tasks: analysis of the source program and synthesis of a machine-language program. The structure of a compiler typically includes a scanner, parser, semantic routines, code generator, and optimizer. The scanner reads the source code and groups characters into tokens. The parser checks the syntax against a grammar. Semantic routines perform static checking and translation. The code generator produces target code, which may then be optimized. An example compiler output is shown translating a sample program into assembly code.
Go Global Fearless
Conquer the world by Internationalizing your product!
Presentation on Internationalization and localization and its testing tips & techniques. Presented at STeP-IN conference Hyderabad 2015
The document describes the Sutton SignWriting Standard of 2017, which provides a stable standard for writing sign languages using a two-dimensional representation. It summarizes the history and principles of SignWriting, and outlines the current standards for Formal SignWriting in ASCII (FSW) and SignWriting in Unicode (SWU). The standard uses characters for naming signs and fonts for viewing signs rendered with spatial coordinates. It aims to be complete, universal, empowering and possible for all sign languages.
This document discusses character encoding and localization nightmares. It begins with examples of encoding issues causing problems like corrupted documents and data loss. It then explains the history of character encoding as the need for encoding non-English languages grew. This led to a "Tower of Babel" effect with different encodings representing different characters. The document outlines the rise of Unicode as a unified standard and provides four rules of thumb to avoid encoding nightmares, such as limiting applications and using UTF-8 encoding when possible. It concludes with tricks and tools for checking, converting, and working with encodings.
The document provides information about the Unicode character code charts and list of character names for Version 5.2. It includes links to various charts and tables for Unicode characters and details terms of use for the code charts. The document contains copyright information and disclaimers regarding proper understanding and implementation of the Unicode standard.
The document provides information about the Unicode character code charts and list of character names for Version 5.2. It includes links to various charts and tables for Unicode characters and details terms of use for the code charts. The document contains copyright information and disclaimers regarding proper implementation and use of the Unicode standards.
This document discusses various coding schemes including:
- Binary coded decimal (BCD) which assigns a weight to each digit position to represent decimal numbers. Other positively weighted codes and negatively weighted codes are also discussed.
- Gray code which minimizes the number of bit changes between adjacent values represented. This is useful for applications like thumbwheels.
- Character encoding standards like ASCII, EBCDIC, and Unicode which can represent larger character sets with more bits per character.
- Floating point number representation with sign, exponent and mantissa fields.
SIGNWRITING SYMPOSIUM PRESENTATION 61: "SignWriting in Unicode and Rich Text Considerations" by Stephen E. Slevinski Jr.
Unicode is a widely accepted standard for encoding the various writing systems of the world. Sutton SignWriting is encoded with Formal SignWriting (FSW) which is plain text ASCII and equivalent to UTF-8.
Last year the Unicode Technical Committee discussed SignWriting and the various data representations. Early August 2016, SignWriting will be discussed at UTC # 148, including a new proposal for Unicode 10.
Formal SignWriting is Plain Text. After the Formal SignWriting strings, rich text details can be add to customize the size and color of individual signs and symbols. SEE: http://www.signwriting.org/symposium/presentation0061.html
UTF-8: The Secret of Character EncodingBert Pattyn
The document discusses character encoding standards like ASCII, UTF-8, and UTF-16. It explains that UTF-8 uses 1-4 bytes per character and has become the standard for XML and web content. The document raises questions about choosing the right encoding based on the characters, software, and browsers used.
Unicode is a standard for representing characters across different platforms and languages. It defines coding schemes like UTF-8, UTF-16, and UTF-32 to represent characters as binary values. UTF-16 uses 16-bit values for most characters but introduces surrogate pairs to represent some characters requiring two 16-bit values. UTF-32 uses 32-bit values for all characters. UTF-8 varies the number of bytes per character from 1 to 4 to optimize for English. Unicode aims to support all languages with a single encoding scheme.
There should be a tool for that - GameQALoc Barcelona 2016Adolfo Gomez-Urda
The document discusses tools and processes to improve localization for video games. It recommends performing font analysis, pseudo-localization, and internationalization passes early on to detect issues. It also advocates for constant validation and translation consistency checks to reduce bugs. Further, it suggests audio validation and providing a localization-friendly pipeline and centralized string database solution to facilitate collaboration between teams. The goal is to improve quality while reducing costs, bugs, and wasted resources associated with localization.
Octal to binary and octal to hexa decimal conversionsAfrasiyab Haider
The document summarizes various number systems and coding techniques:
1. It explains how to perform addition, subtraction, and conversion in octal number systems with examples.
2. It describes binary coded decimals (BCD) and provides the counting table.
3. It explains ASCII codes and provides the code table.
4. It describes excess-3 code and provides the code table.
5. It summarizes Unicode and some common encoding formats like UTF-8.
6. It explains Gray code and provides an example code table.
"Introduction to Internationalization (I18n)" by Adam Asnes, President & CEO of Lingoport (lingoport.com), a software internationalization (i18n) tools and consulting company.
This document provides an overview of assembly language and its relationship to other levels of software. It defines key concepts like machine language, assemblers, and debuggers. Tables describe the software hierarchy, compare assembly to high-level languages, and show number systems and data sizes. Examples demonstrate an assembling and debugging a simple assembly language program.
This document provides information about Plessey and MSI symbology barcodes. It explains the formats and encoding rules for Plessey barcodes, including how bits and digits are represented. It also describes MSI Plessey barcodes, including characteristics like character sets, coding rules, checksums, and usage fields. The document contains details on Plessey variations like MSI and provides examples and references.
This document discusses Unicode, character sets, and how they are handled in software. It begins by explaining how characters are represented differently in ASCII, ISO-8859 character sets, and Unicode. It then describes the UTF-8, UTF-16, and UTF-32 encoding forms for representing Unicode characters as sequences of bytes. The document also discusses how Perl and MySQL handle character encoding and converting between different encodings.
Similar to SIGNWRITING IN UNICODE 8 ISSUES 2015 by Stephen E Slevinski Jr (20)
This document summarizes a presentation on two proposed fingerspelling keyboard layouts for Myanmar Sign Language using SignWriting. It introduces SignWriting and discusses challenges in developing a SignWriting text input interface for Myanmar. Two keyboard layouts are proposed: a phonetic-based layout that maps fingerspelling characters to keys based on pronunciation, and a symbol-based layout that maps characters based on symbol shapes. A user study evaluated the typing speed and usability of each layout with deaf and hearing participants. Results showed that the symbol-based layout had higher typing speeds and was preferred by users.
SignWriting Symposium 2018 Presentation 71: "SignWriting Vision 2030" by Stephen E Slevinski. Across the globe, a common script for all sign languages, a developmental powerhouse, connecting sign language disciplines with text. SignWriting software for generations to come, including SignPuddle, SignMaker and the encoding of the International SignWriting Alphabet (ISWA) in Unicode (SWU) and Formal SignWriting (FSW). http://www.signwriting.org/symposium/presentation0071.html
SIGNWRITING SYMPOSIUM PRESENTATION 68: "Sign Language Writing: SignWriting as a Tool in Deaf Literacy"
"Escrita da Língua de Sinais: SignWriting como ferramenta no letramento de surdos" by Prof. Fernando Henrique Fogaça Carneiro and Profa. Priscila de Abreu Bortoletti
This document discusses using SignWriting (SW) to represent lexical entries in a dictionary of Peruvian Sign Language (LSP). It notes that there is almost no prior research or published dictionaries on LSP. The planned LSP dictionary (DALSP) will include a video, gloss, translation, description, and SW transcription for each sign. Using SW will allow for deeper analysis of LSP's phonological features and help visualize that sign languages can be written phonologically like spoken languages. However, challenges include students needing training in SW conventions and the system potentially engaging the Peruvian Deaf community's interest in a writing system for LSP.
SignWriting Symposium 2016 Live Broadcast July 18 Session 1: “A Home & Education For Deaf Children in Sicuani, Cusco, Peru” by Kristina Tworek. In Peru there are lots of deaf children, especially in the south. Some time ago there was a home for deaf children here in Sicuani, however now the situation changed. Right now only disabled children, for example with Down Syndrome, are staying there. That is why we want to open a new place for all the deaf children in the South of Peru. In the house they are supposed to get food, because good and healthy nutrition is so important for their physical development and for their health in general.
Moreover we want to create a place, where they get a bed and a significant other they can come to, because unfortunately most of the indigent and disabled children are left out of society. We want to give these children a home, where they feel comfortable and happy. That is why we want a primary school for all the deaf children in the south of Peru. The education of these children is so important for their future. In primary school they will learn the basics, how to communicate and express themselves. There they will have the opportunity to learn:
1) sign language
2) speech
3) lipreading
If they don’t have the opportunity to learn these three basics, they don’t have the same rights for their future as other children have. They have the right for equal opportunities. We want to try to make it possible at any cost. For the necessary educaction there is a big possibility: “SignWriting”. It is a system of writing to demonstrate movements and hand, arm and the used face gestures in the language of sings. This system that we will use in primary school, will make it easier to learn the signs and will improve the comprehension of Spanish, its grammatic and the language in general.
In the following attachment you will find an example for our idea how to learn by just playing a game. SEE: http://www.signwriting.org/symposium/presentation0053.html
SIGNWRITING SYMPOSIUM PRESENTATION 56: "SignWriting in Tunisian Deaf Education” by Wafa Laajili and Mohamed Ali Balti.
Teacher Wafa Laajili presented a SignWriting demonstration to educators in Tunisia on the 4th of May 2016. Wafa introduced her experiences using SignWriting in the classroom with Deaf students. SEE: http://www.signwriting.org/symposium/presentation0056.html
SIGNWRITING SYMPOSIUM PRESENTATION 57: "A Web Tool for Building Parallel Corpora of Spoken and Sign Languages" by Alex Malmann Becker & Fabio N. Kepler & Sara Candeias. See: http://www.signwriting.org/symposium/presentation0057.html
The main objective of this work is to build an online tool for manually annotating texts in any spoken language with SignWriting in any sign language. The existence of such tool will allow the creation of parallel corpora between spoken and sign languages that can be used to bootstrap the creation of efficient tools for the Deaf community. As an example, a parallel corpus between English and American Sign Language could be used for training Machine Learning models for automatic translation between the two languages. Clearly, this kind of tool must be designed in a way that it eases the task of human annotators, not only by being easy to use, but also by giving smart suggestions as the annotation progresses, in order to save time and effort. The tool was implemented in the Java Web platform using the JSF framework (Java Server Faces) and an MVC architecture (Model-View-Controller).
This document proposes introducing SignWriting to a bilingual school in Imperatriz, Maranhão, Brazil. It notes that SignWriting is not widely used in Maranhão yet, as only a few deaf individuals know it. The goals are to promote SignWriting at the bilingual school through activities, create initiatives to expand its use statewide, and pass a municipal law requiring its use. The methodology involves applying the project at the school and partnering with institutions for workshops. It describes Imperatriz and the bilingual school, and proposes actions like a law, conference, training, and app to spread SignWriting in Maranhão.
SIGNWRITING SYMPOSIUM PRESENTATION 60: "The Learning of SignWriting at ANPACIN Bilingual School for the Deaf in Maringá - PR, Brazil" by Daniele Miki Fujikawa Bózoli.
Sign languages are a linguistic way of expression for deaf people. In 1974, Valerie Sutton has created her own registration signs system that consists in sign languages. This system is internationally known as SignWriting, which, in Brazil corresponds to Escrita de Sinais, that allows to register the parameters of sign languages as handshapes, locations, movements, orientations and facial expressions. Such system presents itself as possible ally in the deaf students’s education process. However, the SignWriting is not well known by the deaf communities, in addition there are few studies about the impact of SignWriting on the learning of deaf students. The interest of gathering information to enable more conclusive reflections about the SignWriting that has motivated this study. Therefore, this research consists on the learning of school content by the SignWriting system for high school students from ANPACIN - Bilingual School for Deafs of Maringá - Paraná, Brazil. In the course of the empirical study was possible offering to a group of students the basic knowledge of SignWriting, looking up to verify the impact of the knowledge in the academic performance of the participants. As result, it was observed a better performance of the students activities in SignWriting which may represent an additional tool to facilitate the intellectual development of deaf students. Objectively, SignWriting can act in the psychological field as a tool to expand knowledge of the students that can produce significant cognitive gains, in as much as, the systemized system, especially, for the registration of sign languages.
See: http://www.signwriting.org/symposium/presentation0060.html
SIGNWRITING SYMPOSIUM PRESENTATION 61: "SignWriting in Unicode and Rich Text Considerations" by Stephen E. Slevinski Jr.
Unicode is a widely accepted standard for encoding the various writing systems of the world. Sutton SignWriting is encoded with Formal SignWriting (FSW) which is plain text ASCII and equivalent to UTF-8.
Last year the Unicode Technical Committee discussed SignWriting and the various data representations. Early August 2016, SignWriting will be discussed at UTC # 148, including a new proposal for Unicode 10.
Formal SignWriting is Plain Text. After the Formal SignWriting strings, rich text details can be add to customize the size and color of individual signs and symbols.
See: http://www.signwriting.org/symposium/presentation0061.html
O documento discute o SignWriting (SW) como um sistema de escrita para línguas gestuais e seu potencial para promover o desenvolvimento de habilidades de escrita em estudantes surdos. O autor realizou entrevistas e questionários com professores surdos e ouvintes no Brasil que usam o SW. Os resultados sugerem que o SW se adapta bem às línguas gestuais e pode auxiliar na aquisição da língua portuguesa escrita, além de valorizar a cultura surda. O SW parece ser uma ferramenta educacional promissora
SIGNWRITING SYMPOSIUM PRESENTATION 54: http://www.signwriting.org/symposium/presentation0054.html
SignTyp: a cross linguistic database and dictionaries for sign languages by Harry von der Hulst & Rachel Channon
SignTyp is a research tool – a database of phonological and phonetic information. It is also a set of online sign language dictionaries, and the prompts used to create the dictionaries.
Goals for Online Dictionaries:
To collect 1000 signs each from 15+ sign languages (citation forms). Signers respond to the same prompts cross- linguistically.
To transcribe each sign in SignWriting – a notation system for signs created by Valerie Sutton
To create 15+ sign online dictionaries
Goals for Research Database
To convert SignWriting transcriptions into a more granular analytic coding to enable phonetic/phonological analysis of the structure of signs
To provide a comparative study of the phonological structure of 15+ globally diverse sign languages
To test and develop sign phonology models
To investigate the role of iconicity in phonological form
To develop a cognitive model that generalizes over ‘phonological’ form in signed and spoken languages
SIGNWRITING SYMPOSIUM PRESENTATION 62: SignPuddle 3: Front and Back by Stephen E Slevinski Jr.
SignPuddle 3 is currently under active development. Rather than a monolithic project, SignPuddle 3 is split into two separate, but cooperative, projects: the front end of user interactions and the back end for data manipulation.
The front end is intended for the normal user. It is written in HTML, CSS, and JavaScript. With the front end, the user will be able to view and edit information with a modern interface across a variety of platforms such as desktop and mobile. Behind the scenes, the front end will communicate with the back end without the user needing to know the additional details.
The back end manages the data in a series of SQLite databases. It is written in PHP and is based on the Slim Framework v2. The back end uses HTTP methods and JSON data to communicate.
The benefits of splitting SignPuddle 3 into two separate projects are mainly directed at outside developers. They will be able to directly interact with the SignPuddle Online data in an easy and direct manner. They will be able to search and query the data, and they will be able to post new data from the users of their products. Developers can start accessing the data today, using the API Blueprint generated documentation.
SIGNWRITING SYMPOSIUM PRESENTATION 55: "Moving Forward with Sign Language Projects in Formal SignWriting (FSW)” by Stephen E. Slevinski Jr.
Visit Presentation Web Page: http://www.signwriting.org/symposium/presentation0055.html
Imagine a world in which every sign language user can freely share in the sum of all knowledge. Sign languages are human languages. Any topic that can be discussed in a spoken language can be discussed in a signed language. It's important to realize the benefits of a person being able to access information in their primary language. It's exciting to realize that sign language wikipedia projects are now possible with Sutton SignWriting.For the past several years, we have been working on the technical infrastructure to make it possible to have a wikipedia in any sign language. We've been using Translate Wiki to localize the user interface. Most commonly, SignWriting is displayed vertically and for MediaWiki this requires a custom skin with the CSS vertical writing mode enabled. The technical details are complex, and we continue to make progress. As we've seen with Wikipedia itself, there is a snowball effect with these types of projects. More people getting involved, leads to more people getting involved. One of the major factors holding back the widespread acceptance of SignWriting is having enough reading material available to make it worthwhile to learn SignWriting. The sign language wikipedia projects are important for the growth of SignWriting and the positive effects of the sign language wikipedias will benefit all sign language users far beyond just the particular wikipedia projects themselves. Sign language wikipedia projects are now possible with Sutton SignWriting. We encourage sign language users to get involved by learning SignWriting and the MediaWiki software. We encourage technical MediaWiki users of all levels to get involved and help us improve and streamline the technical details. We encourage everyone to imagine a world in which every sign language user can freely share in the sum of all knowledge.
The Lessons in SignWriting Textbook by SignWriting inventor Valerie Sutton is a 220-page 15-chapter tutorial published first in 1990, expanded to a full reference book in 2002, and updated in 2014. Colorful photos and illustrations are accompanied with short English explanations of symbols with sign language examples in American Sign Language (ASL). The 15 chapters teach how to write the body movements of any sign language in the world, step by step. Chapters are: 1. Introduction to SignWriting, 2. Viewpoints (choosing to write from the Expressive perspective), 3. Handshapes, 4. Contact Symbols, 5. Finger Movement, 6. Straight Arm Movement, 7. Curved Movement, 8. Axial Movement (Arm Rotation and Wrist Movement), 9. Circular Movement, 10. Facial Expressions, 11. Head Movement, 12. Movement of the Body and Torso, 13. Movement Dynamics and Timing, 14. Punctuation for Sign Sentences, 15. Writing Signs & Sign Literature. Available on Amazon.com as a printed book: ISBN: 978-0-914336-55-6
1. The document discusses SignWriting, a writing system for sign languages that is supported by the Center for Sutton Movement Writing.
2. SignWriting uses a grid-based system of glyphs and can be encoded in Unicode, with some sign languages encoded in Plane 15 and others in Plane 16.
3. The Center for Sutton Movement Writing aims to provide standardized, stable, and free specifications for encoding various sign languages in fonts and Unicode for wide accessibility across operating systems and devices.
This document discusses developing an interface for Open Journal Systems (OJS) using SignWriting to make journal content more accessible to deaf users. The researchers are working to translate the OJS interface and journal articles into Brazilian Sign Language (Libras) using SignWriting. Their methods involve defining terminology, transcribing text into SignWriting, integrating the codes into files, deploying JavaScript codes, and testing with deaf users. Their goals are to refine the methods, apply the approach to other systems, and create more resources to support scientific publications in sign languages.
Transform Your Communication with Cloud-Based IVR SolutionsTheSMSPoint
Discover the power of Cloud-Based IVR Solutions to streamline communication processes. Embrace scalability and cost-efficiency while enhancing customer experiences with features like automated call routing and voice recognition. Accessible from anywhere, these solutions integrate seamlessly with existing systems, providing real-time analytics for continuous improvement. Revolutionize your communication strategy today with Cloud-Based IVR Solutions. Learn more at: https://thesmspoint.com/channel/cloud-telephony
Microservice Teams - How the cloud changes the way we workSven Peters
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
What to do when you have a perfect model for your software but you are constrained by an imperfect business model?
This talk explores the challenges of bringing modelling rigour to the business and strategy levels, and talking to your non-technical counterparts in the process.
Top Benefits of Using Salesforce Healthcare CRM for Patient Management.pdfVALiNTRY360
Salesforce Healthcare CRM, implemented by VALiNTRY360, revolutionizes patient management by enhancing patient engagement, streamlining administrative processes, and improving care coordination. Its advanced analytics, robust security, and seamless integration with telehealth services ensure that healthcare providers can deliver personalized, efficient, and secure patient care. By automating routine tasks and providing actionable insights, Salesforce Healthcare CRM enables healthcare providers to focus on delivering high-quality care, leading to better patient outcomes and higher satisfaction. VALiNTRY360's expertise ensures a tailored solution that meets the unique needs of any healthcare practice, from small clinics to large hospital systems.
For more info visit us https://valintry360.com/solutions/health-life-sciences
Using Query Store in Azure PostgreSQL to Understand Query PerformanceGrant Fritchey
Microsoft has added an excellent new extension in PostgreSQL on their Azure Platform. This session, presented at Posette 2024, covers what Query Store is and the types of information you can get out of it.
UI5con 2024 - Boost Your Development Experience with UI5 Tooling ExtensionsPeter Muessig
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
SOCRadar's Aviation Industry Q1 Incident Report is out now!
The aviation industry has always been a prime target for cybercriminals due to its critical infrastructure and high stakes. In the first quarter of 2024, the sector faced an alarming surge in cybersecurity threats, revealing its vulnerabilities and the relentless sophistication of cyber attackers.
SOCRadar’s Aviation Industry, Quarterly Incident Report, provides an in-depth analysis of these threats, detected and examined through our extensive monitoring of hacker forums, Telegram channels, and dark web platforms.
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...XfilesPro
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
Mobile app Development Services | Drona InfotechDrona Infotech
Drona Infotech is one of the Best Mobile App Development Company In Noida Maintenance and ongoing support. mobile app development Services can help you maintain and support your app after it has been launched. This includes fixing bugs, adding new features, and keeping your app up-to-date with the latest
Visit Us For :
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian CompaniesQuickdice ERP
Explore the seamless transition to e-invoicing with this comprehensive guide tailored for Saudi Arabian businesses. Navigate the process effortlessly with step-by-step instructions designed to streamline implementation and enhance efficiency.
All you need to know about Spring Boot and GraalVM
SIGNWRITING IN UNICODE 8 ISSUES 2015 by Stephen E Slevinski Jr
1. Issues with
SignWriting in
Unicode 8
Prepared for UTC # 144 / L2 # 241 (July 27-31, 2015)
a Unicode Technical Committee meeting in Redmond, WA
by Stephen E Slevinski Jr
in association with the Center for Sutton Movement Writing
2. My Background
Bachelor of Science
in Mathematics
Raised two kids with
sign language
Started collaboration with Valerie
Sutton from 2004 until today
Complete symbol encoding model on
PUA Plane 16 (37,811 characters)
Complete script encoding model on
PUA Plane 15 (1,179 characters)
Argued with Unicode in 2011
and then walked away
Released the ISWA 2010
symbol set in 2010
Finalized Formal SignWriting
in ASCII on Jan 12, 2012
5 Years of stability with the
symbol set and fonts design
3 1/2 Years of stability with the
character encoding models
Involved with dozens of sign
languages around the world
Foundation for all online use and
modern publishing efforts
3. SignWriting in Software
All major SignWriting editors and viewers are compatible.
• SignPuddle Online
Primary source of written sign language
• Delegs Editor
Educational software from Germany for bilingual education.
• SignWriter Studio
General purpose SignWriting editor, integrated dictionary, and printing.
• SWift
SignWriting improved fast transcriber that aims to simplify the editing process.
• JSPad
SignWriting editor for Japanese sign language based in the Gifu University.
• Tunisigner
interact with SignWriting notations through a 3D virtual signer able to reproduce
the exact gestures represented within the sign language transcription.
• SignTyp
a linguistic coding system developed by Rachel Channon through an NSF grant
that is being integrated with SignWriting.
4. http://www.signbank.org/signmaker.html
Code Breakdown
0 KB
7 KB
14 KB
21 KB
28 KB
35 KB
42 KB
49 KB
56 KB
63 KB
70 KB
Configuration
Support Libraries
Custom HTML, JS, and CSS
SignMaker 2015
Cross-browser, drag-and-drop sign editor,
with dictionary and advanced sign searching
SignWriting in Software
5. Bookmarklet
Javascript-based SignWriting Keyboard
Keyboarding editing has returned to SignWriting
Wikimedia Incubator
The keyboard editor is enabled on Wikimedia
Incubator for the American Sign Language
Wikipedia and every other sign language project.
Store JavaScript in a bookmark and you can use
SignWriting on any web page in any text fields.
Any Website
Add a few KB of JavaScript and the keyboard editor can be enabled
on any website using standard edit boxes and visual presentation.
http://www.signwriting.org/symposium/presentation0041.html
SignWriting in Software
6. What about Unicode?
PUA Plane 15 design (1,179 characters)
The symbol only design removed 2-D layout by dropping
5 structural markers and 500 number characters
N4015 Preliminary Unicode (674 characters)
N4090 Revised Unicode (672 characters)
N4342 Unicode Proposal (672 characters)
A new inherent design removes 2 characters (F1
and R1) and breaks collation as stated in proposal
A new facial diacritic design is proposed
that is unsupported and untested
The original design is still compatible with the community efforts.
7. Issues with SignWriting
in Unicode 8
The Unicode 8 specification will not be used
for any SignWriting project around the world.
The Unicode 8 specification for SignWriting is
politically valuable, but unhelpful for developers.
8. Issues with SignWriting
in Unicode 8
The issue of the moment is sorting,
but there are three main issues.
If we address all of the issues for
SignWriting, the existing International
community of SignWriters is ready, able,
and willing to embrace the standard.
9. Issue 1: Unicode 8 is incomplete
http://signbank.org/SignWriting_Character_Viewer.html
Unicode 8 only encodes
the symbols and ignores
the issue of layout.
Unicode 8 is missing the
structural markers
and number characters
required for 2-D Layout.
Unicode 8 requires SVG
for the visual presentation.
Unicode 8 requires additional
characters/markup to write a sign.
10. Issue 2: Unicode 8 is flawed
The idea of Inherent characters
breaks from the community
use of today and historically.
Because of Inherent modifiers,
sorting is broken, searching is
ambiguous, and replacements
can be destructive.
w s P
Symbol Bases
Tokens
i oSymbol Modifiers
Tokens
identified with a
string of 3 tokens.
w i o
Writing Symbol
P i o
Punctuation Symbol
Fill Rotation
Triadic
Symbol
11. Issue 2: Unicode 8 is flawed
Sorting is broken
1D800 SIGNWRITING HAND-FIST INDEX (HFI)
1DAA1 SIGNWRITING ROTATION MODIFIER-2 (R2)
1DA9B SIGNWRITING FILL MODIFIER-2 (F2)
1. HFI F1 R1
5. HFI F1 R1 HFI F1 R1
2. HFI F1 R2
6. HFI F1 R2 HFI F1 R1
3. HFI F2 R1
7. HFI F2 R1 HFI F1 R1
4. HFI F2 R2
1. HFI
5. HFI HFI
3. HFI F2
7. HFI F2 HFI
4. HFI F2 R2
2. HFI R2
6. HFI R2 HFI
Correct sorting with F1 & R1 Incorrect sorting without F1 & R1
http://www.unicode.org/L2/L2015/15184-signwriting-ducet.txt
http://signpuddle.net/15184-signwriting-ducet-response.txt
http://www.unicode.org/L2/L2015/15202-signwriting-ducet-aux.txt
13. Issue 2: Unicode 8 is flawed
Searching is ambiguous
1D800 SIGNWRITING HAND-FIST INDEX (HFI)
1DAA1 SIGNWRITING ROTATION MODIFIER-2 (R2)
1DA9B SIGNWRITING FILL MODIFIER-2 (F2)
1. HFI F1 R1
5. HFI F1 R1 HFI F1 R1
2. HFI F1 R2
6. HFI F1 R2 HFI F1 R1
3. HFI F2 R1
7. HFI F2 R1 HFI F1 R1
4. HFI F2 R2
1. HFI
5. HFI HFI
3. HFI F2
7. HFI F2 HFI
4. HFI F2 R2
2. HFI R2
6. HFI R2 HFI
Searching with F1 & R1 Searching without F1 & R1
Searching for the symbol
HFI F1 R1 correctly
finds 4 matches
Searching for the symbol HFI
incorrectly finds 10 matches
without negative lookaheads
14. Issue 2: Unicode 8 is flawed
Searching is ambiguous
Query String:
QS10000S20500
Searching for signs that
include 2 exact symbols will
return these results from
the ASL Dictionary.
15. Issue 2: Unicode 8 is flawed
Searching is ambiguous
Plus 6 more pages of signs.
Query String:
QS100uuS205uu
In Unicode 8, searching for a
symbol base without fill or rotation
modifiers will return 6 times as
much noise as signal.
16. Issue 2: Unicode 8 is flawed
Replacements can be destructive
sub uFD830 uFD810 uFD820 by S10000;
sub uFD830 uFD810 uFD821 by S10001;
sub uFD830 uFD810 uFD822 by S10002;
sub uFD830 uFD810 uFD823 by S10003;
sub uFD830 uFD810 uFD824 by S10004;
sub uFD830 uFD810 uFD825 by S10005;
sub uFD830 uFD810 uFD826 by S10006;
sub uFD830 uFD810 uFD827 by S10007;
sub u1DA8B u1DAA7 by S38b07;
sub u1DA8B u1DAA6 by S38b06;
sub u1DA8B u1DAA5 by S38b05;
sub u1DA8B u1DAA4 by S38b04;
sub u1DA8B u1DAA3 by S38b03;
sub u1DA8B u1DAA2 by S38b02;
sub u1DA8B u1DAA1 by S38b01;
sub u1DA8B by S38b00;
https://github.com/Slevinski/signwriting_2010_tools
The TrueType Fonts use Ligatures to support multiple character sets.
Plane 15 Characters Unicode 8 Characters
Increasing symbols keys or
decreasing works without issue.
Decreasing symbol keys
to avoid destruction.
17. Issue 3: Unicode 8 is fictional
Facial diacritics do not exist. There is no font
support, no software support, and no data.
Facial diacritics are described
in one document, using 177 words.
Facial diacritics have never been tested on any
individual, let alone an international group.
Facial expressions are created using
overlap and overlay of many symbols
using Cartesian coordinates for each.
Facial diacritics should
be handled in software
rather than the
character encoding.
Facial diacritics development was
quietly abandoned the end of 2012.
18. Formal SignWriting
Regular Expressions
Query Strings
Community Use
SVG
PUA Plane 15
Graphite Font
Unicode 8 PUA Plane 16TTF
10% to 50% reduction
15 to 50 times expansion
process million of characters per second
search results
15 times expansion
single character per symbolligatures of 1 to 3 characters
twice the size
cartesian coordinates with GPOS
CSS
style text
Isomorphic
JS
ASCII Lite Markup
preferredunused
prototype
6 KB zipped
20. Unicode 9
Regular Expressions
Query Strings
Ideal Solution
Graphite Font TTF
10% to 50% reduction
15 to 50 times expansion
process million of characters per second
search results
cartesian coordinates with GPOS
CSS
style text
http://signpuddle.net/iswa/#smartfont
Prototype Font uses Cartesian coordinates for 2-D layout with Graphite
JS
6 KB zipped
21. Too Late?
SignWriting is spreading around the world and exploding online.
All of the SignWriting projects are using an ASCII solution and
have no plans to switch to the Unicode 8 design for the symbols.
Without a full script solution for SignWriting, Unicode will not be
used for SignWriting, especially the Unicode 8 design which
complicates otherwise simple routines.
Using Unicode for SignWriting is a great idea in theory, but there are
few advantages and too many disadvantages to seriously consider
applying the Unicode 8 design, even if sorting is fixed.
I left the Unicode effort the end of 2011. In 2012, I was shown the
latest proposal (N4342). I objected privately and asked that they
produce a working font before they contact me again.
In 2014, I was contacted that SignWriting will be in Unicode 8. I
reiterated my objections, pointing out the issues, and was told it
was too late to change the design in any way.
22. Discussion Ideas
2-Color Fonts
SignWriting relies on a 2-color font. Currently, SignWriting mimics a 2-color
font by using 2 TrueType Fonts: one for the line and another for the filling. If
you have any experience with 2-color fonts, let’s discuss the possibilities.
2-Dimensional Layout with Graphite and Cartesian coordinates
SignWriting has a prototype font that uses Cartesian coordinates to control the
2-dimensional layout with Graphite and PUA Plane 15 characters. If you have
any experience with 2-dimensional layout using Cartesian coordinates, let’s
discuss the possibilities.
Alternate designs for a 2-dimensional script
This type of discussion is interesting, but it will not effect the SignWriting
community. The standards are stable and widely used. This would make for
an interesting project, but it is not work that I will be doing myself.
23. Discussion Ideas
Unicode 9 or 10
Can we deprecate Unicode 8? The community design has been stable for 3
1/2 years. There is an interested community and there are many possibilities
for 2-Color fonts and 2-Dimensional layout.
Unicode 8
I will not be using Unicode 8. I partially support Unicode 8 with the SignWriting
2010 Fonts, but not the facial diacritics. I suggested that people avoid use
SignWriting in Unicode 8. I’m willing to discuss any of the 3 issues that I have
outlined, but I’m not invested in any tweaks to the Unicode 8 design.
Symbol Encoding Model
PUA Plane 16 (37,811 characters)
Script Encoding Model
PUA Plane 15 (1,179 characters)
both designs are productive and used today
24. Issues with SignWriting
in Unicode 8
by Stephen E Slevinski Jr
http://slevinski.github.io
slevinski@signwriting.org
http://www.slideshare.net/StephenSlevinski/presentations