office-gobmx/i18npool/util
Stephan Bergmann 2eb3922750 Remove duplicate com.sun.star.i18n.IndexEntrySupplier_ja_phonetic_* impls
Ever since 95823ae83c "#95565#add new phonetic
entry for CJK index modules", "com.sun.star.i18n.IndexEntrySupplier_ja_phonetic
(alphanumeric first)" was using the same implementation as
"com.sun.star.i18n.IndexEntrySupplier_ja_phonetic (alphanumeric first) (grouped
by syllable)", and "com.sun.star.i18n.IndexEntrySupplier_ja_phonetic
(alphanumeric last)" was using the same implementation as
"com.sun.star.i18n.IndexEntrySupplier_ja_phonetic (alphanumeric last) (grouped
by syllable)".  But there appears to be no evidence that those implementation
names "com.sun.star.i18n.IndexEntrySupplier_ja_phonetic (alphanumeric first)"
and "com.sun.star.i18n.IndexEntrySupplier_ja_phonetic  (alphanumeric last)" are
actually used anywhere (see also c9b6bf655e "Add
some tests for (Japanese) i18n::IndexEntrySupplier behavior").

And a problem with the current setup is that instantiation those two
implementation names will return implementations whose getImplementationName()
does not match those implementation names (but rather returns
"com.sun.star.i18n.IndexEntrySupplier_ja_phonetic (alphanumeric first) (grouped
by syllable)" and "com.sun.star.i18n.IndexEntrySupplier_ja_phonetic
(alphanumeric last) (grouped by syllable)", resp.)---which is something that
would create failures with an improved CppunitTest_services.

Change-Id: I27cf4ffdb2b84195c6d96f8a7a269120f6a17714
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151144
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2023-04-28 08:14:11 +02:00
..
i18npool.component Remove duplicate com.sun.star.i18n.IndexEntrySupplier_ja_phonetic_* impls 2023-04-28 08:14:11 +02:00
i18npool.en.component