>Allows for multilingual documents
using any or all the languages you desire. Invoice or ticketing applications can
print native language names.
*"multilingual documents" are rare --
as most people understand the term 'documents'. What more people care about is
that all their customer information, from whatever country, can be stored and
accessed everywhere, without data corruption when passing between different
systems. Drop "and
ticketing"
> One set of algorithms for
processing text reduces development and support costs, improves time-to-market,
and allows for single version of source code.
* "set of algorithms for processing"
sounds too techy, and too specific. How about "way to
process"
* And reduces maintanence: you don't
have to have separate service packs for different national
versions.
>Applications can be marketed
globally the day of initial release.
* Not really an example; another
benefit.
> ISO Standards insure interoperability and portability by prescribing conformant behavior. Applications process text consistently and conformance is verifiable. Note that pplications conforming to Unicode, also conform to ISO 10646. * Needs significant rework. Drop "ISO" -- it is not the only game in town,
by any means.. Also, they only insure interoperability if people follow them.
"pplications", and drop commas
> Worldwide deployment capability. Text can be sent from any part of the world to any other part. * Needs significant rework. Even if I were using Latin-1, it can be sent to
any part of the world! Usually "deployment" doesn't mean 'data transport'
>Support by most, if not all, modern technologies allows easy integration. Applications can exchange text without conversion loss or errors. * change "most, if not all," to "all". If it doesn't support Unicode, it
isn't modern ;-)
... >Internet-ready for use in E-business. Internet standards, such as XML,
Perl, Java and JavaScript are Unicode-based
* why are the bullets on standards not combined?
> Continuous evolution extends application lifetime and expands capabilities to meet future needs. Unicode Version 3.0 added 25,000+ characters and new technical specifications that improved, for example, Middle Eastern language support. > that improved, for example, Middle Eastern language support.
* If "Middle Eastern language support" is the major improvement, Joe
Company Manager will not get it; pick another example.
You might also look at http://www.unicode.org/unicode/standard/WhatIsUnicode.html
Mark
|
Title: Unicode Benefits
- Re: Benefits of Unicode J M Sykes
- Re: Benefits of Unicode Michael \(michka\) Kaplan
- Re: Benefits of Unicode Michael \(michka\) Kaplan
- Re: Benefits of Unicode Tex Texin
- Re: Benefits of Unicode Tex Texin
- Re: Benefits of Unicode Tex Texin
- Re: Benefits of Unicode Lukas Pietsch
- Re: Benefits of Unicode Tex Texin
- Re: Benefits of Unicode Peter_Constable
- Re: Benefits of Unicode Peter_Constable
- RE: Benefits of Unicode Mark Davis
- RE: Benefits of Unicode Richard, Francois M
- Re: Benefits of Unicode John Cowan
- RE: Benefits of Unicode Marco Cimarosti
- RE: Benefits of Unicode Marco Cimarosti
- RE: Benefits of Unicode Peter_Constable
- RE: Benefits of Unicode Jonathan Rosenne
- RE: Benefits of Unicode Thomas Chan
- RE: Benefits of Unicode Alistair Vining
- RE: Benefits of Unicode Murray Sargent
- RE: Benefits of Unicode Peter_Constable