public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: Erwin Waterlander <waterlan@xs4all.nl>
To: "cygwin-announce@cygwin.com" <cygwin-announce@cygwin.com>
Subject: Updated: libunistring 1.2-1
Date: Wed, 17 Apr 2024 08:29:17 +0200 (CEST)	[thread overview]
Message-ID: <1627635084.2104677.1713335357498@kpc.webmail.kpnmail.nl> (raw)

libunistring (source package)
libunistring5 (runtime library)
libunistring-devel (development library and include files)
libunistring-doc (documentation)


CHANGES:
========

New in 1.2:
* The data tables and algorithms have been updated to Unicode version 15.1.0.
* New functions u8_pcpy, u16_pcpy, u32_pcpy, similar to mempcpy.
* New functions uc_indic_conjunct_break_name, uc_indic_conjunct_break_byname,
  uc_indic_conjunct_break.
* New functions
    uc_is_property_prepended_concatenation_mark,
    uc_is_property_id_compat_math_start, uc_is_property_id_compat_math_continue,
    uc_is_property_ids_unary_operator and new constants
    UC_PROPERTY_PREPENDED_CONCATENATION_MARK,
    UC_PROPERTY_ID_COMPAT_MATH_START, UC_PROPERTY_ID_COMPAT_MATH_CONTINUE,
    UC_PROPERTY_IDS_UNARY_OPERATOR.
* New constant _libunistring_unicode_version.
* The UTF-8 decoder functions, especially u8_mbtouc, are now more Unicode
  Standard compliant.
* The *printf functions no longer support the %n directive, for security
  reasons.
* Fixed a bug in the *printf functions: In the %U, %lU, %llU directives, a
  negative width given as an argument did not trigger left-justification.
* The functions u16_strstr and u32_strstr now operate in worst-case linear
  time.

http://git.savannah.gnu.org/cgit/libunistring.git/tree/NEWS


DESCRIPTION:
============

Text files are nowadays usually encoded in Unicode, and may consist of 
very different scripts – from Latin letters to Chinese Hanzi –, with 
many kinds of special characters – accents, right-to-left writing marks, 
hyphens, Roman numbers, and much more. But the POSIX platform APIs for 
text do not contain adequate functions for dealing with particular 
properties of many Unicode characters. In fact, the POSIX APIs for text 
have several assumptions at their base which don't hold for Unicode 
text.

This library provides functions for manipulating Unicode strings and for 
manipulating C strings according to the Unicode standard.

homepage: http://www.gnu.org/s/libunistring/
license: LGPL


DETAILS:
========

This library consists of the following parts:

<unistr.h> elementary string functions
<uniconv.h> conversion from/to legacy encodings
<unistdio.h> formatted output to strings
<uniname.h> character names
<unictype.h> character classification and properties
<uniwidth.h> string width when using nonproportional fonts
<uniwbrk.h> word breaks
<unilbrk.h> line breaking algorithm
<uninorm.h> normalization (composition and decomposition)
<unicase.h> case folding
<uniregex.h> regular expressions (not yet implemented)
<unigbrk.h> grapheme cluster breaking


Who needs libunistring?
=======================

libunistring is for you if your application involves non-trivial text 
processing, such as upper/lower case conversions, line breaking, 
operations on words, or more advanced analysis of text. Text provided by 
the user can, in general, contain characters of all kinds of scripts. 
The text processing functions provided by this library handle all 
scripts and all languages.

libunistring is for you if your application already uses the ISO C / 
POSIX <ctype.h>, <wctype.h> functions and the text it operates on is 
provided by the user and can be in any language.

libunistring is also for you if your application uses Unicode strings as 
internal in-memory representation

Porting notes
=============

Failing test:
test-lock.ex

New tests in 1.2 failing:
All failing in the zh_CN.GB18030 locale.
test-c32isalpha.sh
test-c32iscntrl.sh
test-c32isgraph.sh
test-c32islower.sh
test-c32isprint.sh
test-c32ispunct.sh


-- 
Erwin Waterlander
http://waterlan.home.xs4all.nl/

                 reply	other threads:[~2024-04-17  6:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1627635084.2104677.1713335357498@kpc.webmail.kpnmail.nl \
    --to=waterlan@xs4all.nl \
    --cc=cygwin-announce@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).