icu-support — moved to https://groups.google.com/a/unicode.org/g/icu-support see https://icu.unicode.org/contacts

Re: [icu-support] Removal of "imaginary" country flags from the Unicode emojis (Kosovo)

[Markus S. <mar...@gm...>]

1. This is off-topic for a mailing list for the Unicode ICU project.

2. Any participation in Unicode activities, including emails on its lists,
needs to adhere to the Unicode Consortium Code of Conduct
<https://www.unicode.org/policies/code_of_conduct.html>.

3. Unicode is apolitical.

4. There is no Kosovo flag emoji in Unicode. There is a sequence of
characters which could be interpreted as requesting display related to
Kosovo, but that's a bit like spelling "Kosovo" using the letters 'K', 'o',
's', and 'v', and Unicode does not list nor recommend that sequence.

Best regards,
markus

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAN49p6qyeZNm1pcvBH_FWTANWxBLYbqisZ8RccHrkwDrR3taAg%40mail.gmail.com.

Re: [icu-support] icu4c: is there an API for NamedSequences.txt or DoNotEmit.txt?

[Markus S. <mar...@gm...>]

We do not currently have APIs for these data files, nor have plans for them.

It sounds like you would need these for offline building of IME models. I
suggest you just parse these simple text files directly.

Best regards,
markus

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAN49p6oGzu3rY54p5Th1LyNWFCYn7XdtXtM03T5HgaED4n1jbQ%40mail.gmail.com.

Re: [icu-support] silly ParagraphLayout question

['Fredrik R. v. icu-s. <icu...@un...>]

On Tue, Apr 29, 2025 at 4:29 PM mar...@gm...
<mar...@gm...> wrote:

> The icu...@un... addy bounces for me.

The current settings for that group are that you need to first join
the group (anyone can join the group) before you can post to it.

-- 
Fredrik Roubert
ro...@go...

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAPLBv_PrppStz75L93W49oBW56h2Gn-UDaKpOGKpVaHt82Fd9g%40mail.gmail.com.

Re: [icu-support] silly ParagraphLayout question

['Fredrik R. v. icu-s. <icu...@un...>]

On Mon, Apr 28, 2025 at 2:58 PM <mar...@gm...> wrote:

> Hello Fredrik, sorry to bother you, but I've gone through all the
> ParagraphLayout.cpp code over and over again for work, and I can't
> figure out why this function would need or want to have Thai hardcoded
> inside. Or perhaps I don't quite understand the specific Thai case here.

I don't really know anything about the layout module and I have no
clue about why there's a BreakIterator specifically for Thai created
there, but I can see from the revision log that this has been there
from the very first version of this code, which was added for this
ticket:

https://unicode-org.atlassian.net/browse/ICU-2243

Unfortunately there are no comments there whatsoever about why it was
done in this way, but at least it says that the code reviewer was
"srl" which is Steven Loomis who's still around (CC'ed) and who might
possibly have some insight about this.

-- 
Fredrik Roubert
ro...@go...

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAPLBv_POF0zymdOWwBTm3aHSGKqLdBr9XgCF_6S_%2B4mrbzDevg%40mail.gmail.com.

[icu-support] Trouble finding Time Zones by name

[Chris K. <cki...@al...>]

If I construct
        auto tz = icu::TimeZone::createTimeZone("Africa/Harare");
I can then iterate over various styles to get other names for this Time Zone. In particular,
        Tz->GetDisplayName(0, TimeZone::GENERIC_LOCATION, result);
I get the name "Zimbabwe Time". I have not found any way to get from the name "Zimbabwe Time" to get the correct time zone object later. I have been using  a TimeZoneFormat object:
        auto tzf = TimeZoneFormat::createInstance(loc, ec);
And call
        auto foundTZ = tzf->parse(UTZFMT_STYLE_GENERIC_LOCATION, uniName, pos, UTZFMT_PARSE_OPTION_NONE, &ttype);
And I get no foundTZ. I have tried a variety of format styles and parse options, but I haven't found a way to find a TZ object from that name.

If GetDisplayName can give a name, shouldn't Parse be able to find the TZ for that name?

How can I parse this? Is there a better way to find this?

Re: [icu-support] Request for Assistance with ICU 74.1 Compilation on Solaris Studio

['Fredrik R. v. icu-s. <icu...@un...>]

On Fri, Apr 4, 2025 at 7:26 PM Omesharma <sha...@gm...> wrote:

> gmake[1]: Nothing to be done for 'all'.

That is what gmake would print if it was run in a directory where a
build had already been performed.

To make it easier to pinpoint where things go wrong, I recommend you
to start from scratch in an empty directory, extracting the archive,
applying the patch, each and every time.

-- 
Fredrik Roubert
ro...@go...

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAPLBv_M8oTABJqKNbhwdfu3wfh3QxDZFuOmsHaWkZDsPFgBxxw%40mail.gmail.com.

Re: [icu-support] Request for Assistance with ICU 74.1 Compilation on Solaris Studio

['Fredrik R. v. icu-s. <icu...@un...>]

On Thu, Apr 3, 2025 at 4:08 PM Omesharma <sha...@gm...> wrote:

>   514  PATH="/comms/tools/apps/solarisstudio126_sparc/bin:$PATH" CXXFLAGS='-std=c++11'
>   515  ./runConfigureICU Solaris

That's not the same, when you split that one commandline into two
lines the first line will set local variables, which then won't be
passed to the command executed on the second line.

-- 
Fredrik Roubert
ro...@go...

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAPLBv_MZjjG75WsAZRXX3e_PPE2HcLMtGE1_CbvxF7o6DQpEqA%40mail.gmail.com.

Re: [icu-support] Request for Assistance with ICU 74.1 Compilation on Solaris Studio

['Fredrik R. v. icu-s. <icu...@un...>]

On Thu, Apr 3, 2025 at 8:14 AM Omesharma <sha...@gm...> wrote:

> /comms/tools/apps/solarisstudio126_sparc/bin/CC   -DU_HAVE_ELF_H=1 -DU_HAVE_STRTOD_L=0  -I../../common -I../..  -DPACKAGE_NAME=\"ICU\" -DPACKAGE_TARNAME=\"International\ Components\ for\ Unicode\" -DPACKAGE_VERSION=\"74.1\" -DPACKAGE_STRING=\"ICU\ 74.1\" -DPACKAGE_BUGREPORT=\"http://icu-project.org/bugs\" -DPACKAGE_URL=\"http://icu-project.org\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSIZEOF_VOID_P=4 -DHAVE_LIBM=1 -DHAVE_ELF_H=1 -DHAVE_DLFCN_H=1 -DHAVE_DLOPEN=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_LIBPTHREAD=1 -DHAVE_INTTYPES_H=1 -DHAVE_DIRENT_H=1 -DWORDS_BIGENDIAN=1 -DHAVE_WCHAR_H=1 -DSIZEOF_WCHAR_T=4 -O4 -xlibmil  -Wno-ambiguous-reversed-operator -mt  -c   -o scrptrun.o _scrptrun.cpp
> "../../common/unicode/umachine.h", line 386: Error: char16_t is not defined.

That looks like you haven't set CXXFLAGS='-std=c++11'.

To make this easier, I'd recommend you to start out by following the
steps that I listed exactly, including both applying the patch file
and setting CXXFLAGS.

-- 
Fredrik Roubert
ro...@go...

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAPLBv_N_FbEu8wjmwybTM%3DjoEgBPyPBvmSD%2BkYgegjAWj9yGcA%40mail.gmail.com.

Re: [icu-support] Request for Assistance with ICU 74.1 Compilation on Solaris Studio

[Fredrik R. <ro...@go...>]

On Wed, Apr 2, 2025 at 7:55 PM Omesharma <sha...@gm...> wrote:

> Steps followed
> wget https://github.com/unicode-org/icu/releases/download/release-74-1/icu4c-74_1-src.tgz
> tar -xzvf icu4c-74_1-src.tgz
> cd source/
> PATH="/comms/tools/apps/solarisstudio126_sparc/bin:$PATH" CXXFLAGS='-std=c++11'
> ./runConfigureICU Solaris

Why did you not apply the patch?

-- 
Fredrik Roubert
ro...@go...

Re: [icu-support] Request for Assistance with ICU 74.1 Compilation on Solaris Studio

['Fredrik R. v. icu-s. <icu...@un...>]

On Wed, Apr 2, 2025 at 8:46 AM Omesharma <sha...@gm...> wrote:

> Is there any possibility that the ICU 74.1 team could assist in making the library compatible with Solaris Studio (as it worked fine up to ICU version 70.1)?

We don't actually have such resources, but I feel something of a
personal affinity to Solaris and was curious so I took a quick look at
it and with the attached patch applied I was able to successfully
compile ICU4C 74.1 on Solaris using Studio 12.6, like this:

$ tar xzf icu4c-74_1-src.tgz
$ cd icu
$ patch -p1 -i ../icu4c-74-1-solaris-1.patch
$ cd source
$ PATH="/opt/developerstudio12.6/bin:$PATH" CXXFLAGS='-std=c++11'
./runConfigureICU Solaris
$ gmake

-- 
Fredrik Roubert
ro...@go...

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAPLBv_PeYEDQ8T2XzgMVLH0-MW_G1mh9wMy0DHc95%3DBWKC6%2BVQ%40mail.gmail.com.

Re: [icu-support] Request for Assistance with ICU 74.1 Compilation on Solaris Studio

[Rob B. <ro...@da...>]

So, perhaps the pertinent question would be:  Can Solaris Studio support C++11 – the answer is a qualified “yes”, in that to support C++11 Solaris Studio requires a different set of runtime libraries, which tends to make anything built with it incompatible with binaries build without c++11 flags.
Most of these “vendor” compilers had some hacky way to support c++11 and later standards, but if Solaris is your target, you’re much better off using gcc.  We were building binaries with gcc-9 until we dropped support for Solaris.

HTH

From: Markus Scherer <mar...@gm...>
Date: Tuesday, April 1, 2025 at 12:22 PM
To: Omesharma <sha...@gm...>
Cc: han...@gm... <han...@gm...>, icu-support <icu...@un...>
Subject: Re: [icu-support] Request for Assistance with ICU 74.1 Compilation on Solaris Studio
On Tue, Apr 1, 2025 at 3:17 AM Omesharma <sha...@gm...<mailto:sha...@gm...>> wrote:
Does ICU 74.1 officially support compilation with Solaris Studio?

https://icu.unicode.org/download/74
ICU4C Platform Support

ICU4C requires C++11 and has been tested with up to C++20.

We routinely test on recent versions of Linux, macOS, and Windows.

We accept patches for other platforms.


markus
--
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un...<mailto:icu...@un...>.
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAN49p6rDvE%3Do7YidTHocNOyXhSHLA0U6Sj_%3DdkT-Lg_uuSNU7A%40mail.gmail.com<https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAN49p6rDvE%3Do7YidTHocNOyXhSHLA0U6Sj_%3DdkT-Lg_uuSNU7A%40mail.gmail.com?utm_medium=email&utm_source=footer>.

Re: [icu-support] Request for Assistance with ICU 74.1 Compilation on Solaris Studio

[Markus S. <mar...@gm...>]

On Tue, Apr 1, 2025 at 3:17 AM Omesharma <sha...@gm...> wrote:

> Does ICU 74.1 officially support compilation with Solaris Studio?
>

https://icu.unicode.org/download/74

ICU4C Platform Support

ICU4C requires C++11 and has been tested with up to C++20.

We routinely test on recent versions of Linux, macOS, and Windows.

We accept patches for other platforms.



markus

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAN49p6rDvE%3Do7YidTHocNOyXhSHLA0U6Sj_%3DdkT-Lg_uuSNU7A%40mail.gmail.com.

Re: [icu-support] Request for Assistance with ICU 74.1 Compilation on Solaris Studio

['Fredrik R. v. icu-s. <icu...@un...>]

On Tue, Apr 1, 2025 at 5:38 PM Fredrik Roubert <ro...@go...> wrote:

> ICU 74 requires a compiler that supports the C++17 standard:
>
> https://icu.unicode.org/download/74

Oops, I was one version off there, it should be ICU 75 that requires
C++17. But the error messages you got all seem related to standards
compliance, so that's where I'd recommend you start looking for what's
not working.

-- 
Fredrik Roubert
ro...@go...

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAPLBv_NvkObbC0SQzPUxuU5CrTQOAtudLZqYyOLqH4PNA33GWA%40mail.gmail.com.

Re: [icu-support] Request for Assistance with ICU 74.1 Compilation on Solaris Studio

['Fredrik R. v. icu-s. <icu...@un...>]

On Tue, Apr 1, 2025 at 12:17 PM Omesharma <sha...@gm...> wrote:

> While ICU 70.1 compiled successfully on both platforms, we are encountering compilation errors with ICU 74.1 on Solaris when using Solaris Studio (12.6).

ICU 74 requires a compiler that supports the C++17 standard:

https://icu.unicode.org/download/74

But the Studio 12.6 compiler only supports the C++14 standard:

https://docs.oracle.com/cd/E77782_01/html/E77789/bkabg.html

So it's to be expected that compiling ICU 74 with Studio 12.6 won't work.

-- 
Fredrik Roubert
ro...@go...

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAPLBv_PWN-JpYJtpPK-TDg%2BwTRUPSfCddGrKWBdCq3jjiW45Tw%40mail.gmail.com.

Re: [icu-support] Is this the most idiomatic, reasonably performant way to normalize a std::string encoded with UTF8 using ICU4C?

['Fredrik R. v. icu-s. <icu...@un...>]

On Sat, Mar 29, 2025 at 4:23 AM 'prospero' via icu-support
<icu...@un...> wrote:

> icu::UnicodeString unnormalized_string = […]
> icu::UnicodeString normalized_string;

There's no need to convert back and forth to and from
icu::UnicodeString, you'll waste less computing resources if you skip
that and work directly with UTF-8 instead, by calling the
normalizeUTF8() method instead of the normalize() method:

https://unicode-org.github.io/icu-docs/apidoc/released/icu4c/classicu_1_1Normalizer2.html#acf059465e9ced97d153fd21e5a048a37

icu::StringByteSink<std::string> sink(&normalized_utf8_string);
normalizer->normalizeUTF8(0, unnormalized_utf8_string, sink, nullptr, status);

-- 
Fredrik Roubert
ro...@go...

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAPLBv_OmK-3Sp69VGp69fhud9Jtkbw3RaFxC%2B%2BvhN66_Ucc0Ew%40mail.gmail.com.

Re: [icu-support] Issue Building ICU on Windows for Inflection Testing

['Shane C. v. icu-s. <icu...@un...>]

Hi, @George Rhoten <gr...@ap...> can help with questions about
Unicode Inflections.

On Mon, Mar 17, 2025 at 2:03 PM baha bouali <bah...@gm...>
wrote:

> Hello Everyone,
>
> I’ve been stuck for the past two weeks trying to build ICU on Windows as
> part of my preparation for the Google Summer of Code (GSoC) 2025. I’m
> working on a proposal for the project "Integrate Unicode Inflection Into
> Message Format 2"
> <https://docs.google.com/document/u/2/d/e/2PACX-1vQbj0-VFkRjYdnivuPPXuHM3IW4LuHxK6E0LVO3O8ZU_-k8CYH_eFMZ_IwFg_r-oBw3FCEOmHCb5jrn/pub>,
> and I need to test ICU’s inflection functionalities on my machine (C++).
>
> Here’s what I’ve done so far:
>
> 1. Downloaded the ICU source code and extracted it to C:\Users\me.
>
> 2. Opened a Developer Command Prompt for Visual Studio 2022.
>
> 3. Created a `build` directory inside the ICU source directory:
>
>
>
>    cd ~\icu-main\icu4c
>
>    mkdir build
>
>    cd build
>
> 4. Ran CMake to generate build files:
>
>    cmake .. -G "Visual Studio 17 2022" -A x64
>
>
>
> This completed successfully, detecting the compiler and generating build
> files.
>
> 5. Attempted to build ICU:
>
>    cmake --build . --config Release
>
> I also tried following through the ICU Windows Setup
> <https://unicode-org.github.io/icu/userguide/icu4c/build.html#how-to-build-and-install-on-windows>
> Documentation.
>
> However, the build process fails with the following error :
> Cannot open “icui18n.lib” file or not recognize so many other header (.h)
> files.
>
> System Details :
>
> - Windows 10
>
> - CLion 2022.3.2 (uses VS 2022 toolchain with MSVC compiler)
>
> - Visual Studio 2022 (Community Edition) with C++ workload
>
> - CMake 3.28.1
>
> - ICU version: 75
>
>
>
> Could someone please help me troubleshoot this issue? Specifically:
>
>
>    1. Is the process I’m following correct for building ICU on Windows?
>    2. Are there any additional steps to successfully build ICU and test
>    inflection functionalities?
>
>
> Lastly, if building ICU is too hard on Windows, are there other tools or
> frameworks (e.g., Apple Foundation
> <https://developer.apple.com/documentation/foundation>) I can use to test
> inflection functionalities?
>
> --
> You received this message because you are subscribed to the Google Groups
> "icu-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to icu...@un....
> To view this discussion visit
> https://groups.google.com/a/unicode.org/d/msgid/icu-support/7d7a2e64-a64b-46ec-96fe-16d586711183n%40unicode.org
> <https://groups.google.com/a/unicode.org/d/msgid/icu-support/7d7a2e64-a64b-46ec-96fe-16d586711183n%40unicode.org?utm_medium=email&utm_source=footer>
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "ICU - Team" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to icu...@un....
> To view this discussion visit
> https://groups.google.com/a/unicode.org/d/msgid/icu-team/7d7a2e64-a64b-46ec-96fe-16d586711183n%40unicode.org
> <https://groups.google.com/a/unicode.org/d/msgid/icu-team/7d7a2e64-a64b-46ec-96fe-16d586711183n%40unicode.org?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CABxsp%3Dm11HHDtR2mq16xJ--f%3DzyWGU%2BEfFhu%2B6d1Gs%2Bon5zJ4A%40mail.gmail.com.

[icu-support] ICU 78 (2025-oct): moving to Java 11

[Markus S. <mar...@gm...>]

Dear ICU users,

I wanted to emphasize a point from our announcement and from our ICU 77
<https://unicode-org.github.io/icu/download/77.html> page:
Attention: Future Changes

Beginning with ICU 78 (2025-oct):

   1. We want to move the minimum required Java version from Java 8 to Java
   11. This is a significant, useful update in terms of the Java language and
   standard library, and simplifies ICU tooling which currently uses a mix of
   Java 8 and Java 11. Note that Android desugaring
   <https://developer.android.com/studio/write/java11-default-support-table>
supports
   at least Java 11 since late 2023.
   See ICU-23072 <https://unicode-org.atlassian.net/browse/ICU-23072> where
   you can provide comments.


Best regards,
markus

---------- Forwarded message ---------
From: Markus Scherer <mar...@gm...>
Date: Thu, Mar 13, 2025 at 3:24 PM
Subject: ICU 77 Released
To: icu-support <icu...@un...>


Dear friends and users of ICU,

We are pleased to announce the release of Unicode® ICU 77. It updates to CLDR
47 <https://cldr.unicode.org/downloads/cldr-47> (beta blog
<https://blog.unicode.org/2025/02/unicode-cldr-47-beta-available-for.html>)
locale data with new locales, and various additions and corrections.

   -

   Download: releases/tag/release-77-1
   <https://github.com/unicode-org/icu/releases/tag/release-77-1>
   -

   Maven: com.ibm.icu / icu4j / version 77.1
   <https://mvnrepository.com/artifact/com.ibm.icu/icu4j/77.1>


ICU 77 <https://unicode-org.github.io/icu/download/77.html> is mostly
focused on bug fixes, segmentation conformance, and other refinements.

The Java technology preview implementation of the CLDR MessageFormat 2.0
specification has been updated to incorporate the CLDR 46.1 spec
<https://www.unicode.org/reports/tr35/tr35-74/tr35-messageFormat.html> plus
most but not all of the CLDR 47 changes.

The C++ technology preview implementation of MessageFormat 2.0 is not yet
quite up to date with CLDR 46.1.

Please note that for ICU 78 (2025-oct) we are planning to (a) upgrade from
Java 8 to Java 11, and (b) remove the ICU4J Locale Service Provider. See
the ICU 77 <https://unicode-org.github.io/icu/download/77.html> page for
details.

Best regards,

Markus Scherer for the ICU Project

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAN49p6rhTFkn%2BBSTouE0RbmY5bMCKa_2pxd%2BGvSFOeH%2BY_hF1Q%40mail.gmail.com.

[icu-support] ICU 78 (2025-oct): removing ICU4J Locale Service Provider (localespi)

[Markus S. <mar...@gm...>]

Dear ICU users,

I wanted to emphasize another point from our announcement and from our ICU
77 <https://unicode-org.github.io/icu/download/77.html> page:
Attention: Future Changes

Beginning with ICU 78 (2025-oct):

   1. We are planning to remove the ICU4J Locale Service Provider
   <https://unicode-org.github.io/icu/userguide/icu4j/locale-service-provider.html>
    (Maven: com.ibm.icu / icu4j-localespi / version 76.1
   <https://mvnrepository.com/artifact/com.ibm.icu/icu4j-localespi/76.1>).
   It is much less useful than when we added it, has very low usage, needs
   work for newer Java versions, and complicates ICU4J development.
   2. See ICU-23071 <https://unicode-org.atlassian.net/browse/ICU-23071> where
   you can provide comments.


Best regards,
markus

---------- Forwarded message ---------
From: Markus Scherer <mar...@gm...>
Date: Thu, Mar 13, 2025 at 3:24 PM
Subject: ICU 77 Released
To: icu-support <icu...@un...>


Dear friends and users of ICU,

We are pleased to announce the release of Unicode® ICU 77. It updates to CLDR
47 <https://cldr.unicode.org/downloads/cldr-47> (beta blog
<https://blog.unicode.org/2025/02/unicode-cldr-47-beta-available-for.html>)
locale data with new locales, and various additions and corrections.

   -

   Download: releases/tag/release-77-1
   <https://github.com/unicode-org/icu/releases/tag/release-77-1>
   -

   Maven: com.ibm.icu / icu4j / version 77.1
   <https://mvnrepository.com/artifact/com.ibm.icu/icu4j/77.1>


ICU 77 <https://unicode-org.github.io/icu/download/77.html> is mostly
focused on bug fixes, segmentation conformance, and other refinements.

The Java technology preview implementation of the CLDR MessageFormat 2.0
specification has been updated to incorporate the CLDR 46.1 spec
<https://www.unicode.org/reports/tr35/tr35-74/tr35-messageFormat.html> plus
most but not all of the CLDR 47 changes.

The C++ technology preview implementation of MessageFormat 2.0 is not yet
quite up to date with CLDR 46.1.

Please note that for ICU 78 (2025-oct) we are planning to (a) upgrade from
Java 8 to Java 11, and (b) remove the ICU4J Locale Service Provider. See
the ICU 77 <https://unicode-org.github.io/icu/download/77.html> page for
details.

Best regards,

Markus Scherer for the ICU Project

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAN49p6r7NBjbXArOMt0c8pkisk1%3DPgFp5CDRx9aVNm8-S3XQbw%40mail.gmail.com.

[icu-support] ICU 77 Released

[Markus S. <mar...@gm...>]

Dear friends and users of ICU,

We are pleased to announce the release of Unicode® ICU 77. It updates to CLDR
47 <https://cldr.unicode.org/downloads/cldr-47> (beta blog
<https://blog.unicode.org/2025/02/unicode-cldr-47-beta-available-for.html>)
locale data with new locales, and various additions and corrections.

   -

   Download: releases/tag/release-77-1
   <https://github.com/unicode-org/icu/releases/tag/release-77-1>
   -

   Maven: com.ibm.icu / icu4j / version 77.1
   <https://mvnrepository.com/artifact/com.ibm.icu/icu4j/77.1>


ICU 77 <https://unicode-org.github.io/icu/download/77.html> is mostly
focused on bug fixes, segmentation conformance, and other refinements.

The Java technology preview implementation of the CLDR MessageFormat 2.0
specification has been updated to incorporate the CLDR 46.1 spec
<https://www.unicode.org/reports/tr35/tr35-74/tr35-messageFormat.html> plus
most but not all of the CLDR 47 changes.

The C++ technology preview implementation of MessageFormat 2.0 is not yet
quite up to date with CLDR 46.1.

Please note that for ICU 78 (2025-oct) we are planning to (a) upgrade from
Java 8 to Java 11, and (b) remove the ICU4J Locale Service Provider. See
the ICU 77 <https://unicode-org.github.io/icu/download/77.html> page for
details.

Best regards,

Markus Scherer for the ICU Project

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAN49p6p%3Dbb4qNKvGsObDyzPaJVHXP1vVa-rvcV9DC04DarjSCQ%40mail.gmail.com.

Re: [icu-support] Unicode property

[Markus S. <mar...@gm...>]

Oh, and please subscribe to, and use, the icu-support mailing list on
unicode.org. We have moved off of the SourceForge lists.

On Sun, Mar 9, 2025 at 11:37 PM Markus Scherer <mar...@gm...> wrote:

> Hi Georges,
>
> On Sun, Mar 9, 2025 at 5:34 PM Georges MURR via icu-support <
> icu...@li...> wrote:
>
>> Is there  way to find in which Unicode version the Unicode property of a
>> character was defined? For instance I would like to know when the Unicode
>> property of the surrogate pair
>> \uD804\uDFB8 was defined.
>>
>
> First, this is not really an ICU (library) question but a question about
> the Unicode encoding standard.
> https://www.unicode.org/consortium/distlist.html
>
> Second, you won't find much by looking for the escaped UTF-16 notation of
> a character. The data files and documentation use code points. In this
> case, U+113B8.
>
> Third, there are something like 100 Unicode properties. Which one are you
> looking for?
>
> FYI: Just a simple web search for "113B8" gives me some useful results; in
> this case, the second one is https://codepoints.net/U+113B8?lang=en which
> says right in the result snippet:
> “U+113B8 TULU-TIGALARI VOWEL SIGN AA: 𑎸 – Unicode    U+113B8 was added in
> Unicode version 16.0 in 2024. ...”
>
> In the ICU repo, you can find a file with a significant subset of the
> Unicode character data in reformatted form:
>
> https://raw.githubusercontent.com/unicode-org/icu/refs/heads/main/icu4c/source/data/unidata/ppucd.txt
>
> Search for 113B8 -->
> cp;113B8;gc=Mc;GCB=EX;-Gr_Base;Gr_Ext;-IDS;InCB=Extend;InPC=Right;InSC=Vowel_Dependent;lb=CM;na=TULU-TIGALARI
> VOWEL SIGN AA;NFC_QC=M;NFKC_QC=M;SB=EX;WB=Extend;-XIDS
>
> This is specific to ICU but uses Unicode short property names and short
> property value names.
> See here for the gory details:
> https://unicode-org.github.io/icu/design/props/ppucd
>
> I hope this helps,
> markus
>

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAN49p6qRdk3mRTZhfCaqud%3D-NwpST7ZYEvs56GDPaBw%2B%3DBuoYg%40mail.gmail.com.

Re: [icu-support] Unicode property

[Markus S. <mar...@gm...>]

Hi Georges,

On Sun, Mar 9, 2025 at 5:34 PM Georges MURR via icu-support <
icu...@li...> wrote:

> Is there  way to find in which Unicode version the Unicode property of a
> character was defined? For instance I would like to know when the Unicode
> property of the surrogate pair
> \uD804\uDFB8 was defined.
>

First, this is not really an ICU (library) question but a question about
the Unicode encoding standard.
https://www.unicode.org/consortium/distlist.html

Second, you won't find much by looking for the escaped UTF-16 notation of a
character. The data files and documentation use code points. In this
case, U+113B8.

Third, there are something like 100 Unicode properties. Which one are you
looking for?

FYI: Just a simple web search for "113B8" gives me some useful results; in
this case, the second one is https://codepoints.net/U+113B8?lang=en which
says right in the result snippet:
“U+113B8 TULU-TIGALARI VOWEL SIGN AA: 𑎸 – Unicode    U+113B8 was added in
Unicode version 16.0 in 2024. ...”

In the ICU repo, you can find a file with a significant subset of the
Unicode character data in reformatted form:
https://raw.githubusercontent.com/unicode-org/icu/refs/heads/main/icu4c/source/data/unidata/ppucd.txt

Search for 113B8 -->
cp;113B8;gc=Mc;GCB=EX;-Gr_Base;Gr_Ext;-IDS;InCB=Extend;InPC=Right;InSC=Vowel_Dependent;lb=CM;na=TULU-TIGALARI
VOWEL SIGN AA;NFC_QC=M;NFKC_QC=M;SB=EX;WB=Extend;-XIDS

This is specific to ICU but uses Unicode short property names and short
property value names.
See here for the gory details:
https://unicode-org.github.io/icu/design/props/ppucd

I hope this helps,
markus

[icu-support] Unicode property

[Georges M. <ga...@ya...>]

Hi,Is there  way to find in which Unicode version the Unicode property of a character was defined? For instance I would like to know when the Unicode property of the surrogate pair\uD804\uDFB8 was defined.


Thanks.

Re: [icu-support] icu4j 76.1 LowercaseTransliterator synchronized bottleneck

[Markus S. <mar...@gm...>]

On Tue, Feb 25, 2025 at 11:00 AM Steven Schlansker <st...@pa...>
wrote:

> I didn't seem to be able to create a JIRA issue to track due to lack of
> permissions.
>

You need to create a Jira account for creating a ticket.
It's an anti-spam measure by Jira...

tnx
markus

>

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAN49p6ozwUK6LgNX1-EWatFSdixWFdKizxdEVmgKc%3DwY8MA0Aw%40mail.gmail.com.

Re: [icu-support] icu4j 76.1 LowercaseTransliterator synchronized bottleneck

[Markus S. <mar...@gm...>]

Hi Steven,

On Mon, Feb 24, 2025 at 3:03 PM Steven Schlansker <st...@pa...>
wrote:

> Hello ICU world,
>
> We use icu4j through Apache Lucene to power a high-throughput indexing
> pipeline.
> While attempting to analyze our performance using JDK Mission Control, we
> noticed a particularly hot lock - the instance lock on
> LowercaseTransliterator.
>
> It seems that Lucene instantiates a single Transliterator instance, which
> should be safe and performant as the docs note that it is stateless.
>
> However, the LowercaseTransliterator in particular seems to actually keep
> a small bit of state (a ReplaceableContextIterator and a StringBuilder
> result) and guard their reuse via synchronized.
>
> This would indeed avoid some allocation pressure and reuse buffers, but
> the flip side is that our 8 worker threads all trip over each others feet
> trying to mediate access to these shared buffers.
>
> Would the project consider changing this, to accept the cost of allocating
> temporary buffers, in pursuit of allowing many threads to share a
> Transliterator efficiently? Failing that, a ThreadLocal iter + result
> buffer could be the "best of both worlds" with a slight complexity penalty.
>
> We'd be happy to submit a PR if either of these approaches seem acceptable.
> Thank you for your consideration!
>

Sadly, we have not had real work done on the Transliterator code in a long
time. We are also aware that we have a scalability issue there.

It would be great if you could experiment with one or another approach, and
benchmark it, and create a PR based on what you find.

Thanks & best regards,
markus
ICU-TC chair

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAN49p6rDO_CJw1SV1YZaSwN6cjGFcPCJgwKHF1LyKkCD-oY_PA%40mail.gmail.com.

[icu-support] ICU 77 Release Candidate available

[Markus S. <mar...@gm...>]

Dear friends and users of ICU,

We are pleased to announce the release candidate for Unicode® ICU 77. It
updates to CLDR 47 <https://cldr.unicode.org/downloads/cldr-47> (alpha blog
<https://blog.unicode.org/2025/02/unicode-cldr-47-alpha-now-available-for.html>)
locale data with new locales, and various additions and corrections.

ICU 77 is mostly focused on bug fixes, segmentation conformance, and other
refinements.

The Java technology preview implementation of the CLDR MessageFormat 2.0
specification has been updated to incorporate the CLDR 46.1 spec
<https://www.unicode.org/reports/tr35/tr35-74/tr35-messageFormat.html> plus
most but not all of the CLDR 47 changes.

The C++ technology preview implementation of MessageFormat 2.0 is not yet
quite up to date with CLDR 46.1.

For details, please see https://unicode-org.github.io/icu/download/77.html.

Please test this release candidate on your platforms and report bugs and
regressions by Monday, 2025-mar-10, via the icu-support
<https://icu.unicode.org/contacts> mailing list, and/or please find/submit
error reports <https://icu.unicode.org/bugs>.

Please do not use this release candidate in production.

The preliminary API reference documents are published on
unicode-org.github.io/icu-docs/ – follow the “Dev” links there.

Best regards,

Markus Scherer for the ICU Project

-- 
You received this message because you are subscribed to the Google Groups "icu-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icu...@un....
To view this discussion visit https://groups.google.com/a/unicode.org/d/msgid/icu-support/CAN49p6pj0WeHHbRRms6KCm1rJj3WhCsV3NjS3SQQyqn9cBEc_g%40mail.gmail.com.