Hi Karl, Olivier, Guylaine, > It looks like the native2ascii invocations have been stripped entirely from the build.xml files everywhere, not just in ui-core.
FYI, the native2ascii command disappeared in the patch I provided to support Java 11 which was included in the PR below. I'm so sorry for that. https://github.com/apache/manifoldcf/pull/150/files#diff-38e7ea3183260ebac5d6772723b64a3b69ce8aab6a0c1ca2ada6fd9f410c0ba6L283 Thank you for investigating this matter! Regards, Mingchun 2023年10月10日(火) 2:17 Karl Wright <daddy...@gmail.com>: > It's worse than that. > It looks like the native2ascii invocations have been stripped entirely from > the build.xml files everywhere, not just in ui-core. I'm trying to figure > out when that happened and see if I can get it back. > > Karl > > > On Mon, Oct 9, 2023 at 12:42 PM Olivier Tavard < > olivier.tav...@francelabs.com> wrote: > > > Hi Karl, > > > > My colleague Guylaine noticed that one line was missing into > > framework/build.xml into the latest version : > > <native2ascii encoding="UTF-8" src="ui-core/src/main/native2ascii" > > dest="build/ui-core/classes" includes="**/*.properties" /> > > > > So all the i18n translation files were missing into the build. The > correct > > code is : > > > > <target name="compile-ui-core" depends="compile-core"> > > <mkdir dir="build/ui-core/classes"/> > > <javac srcdir="ui-core/src/main/java" > > destdir="build/ui-core/classes" deprecation="true" target="1.8" > > source="1.8" debug="true" encoding="utf-8" > debuglevel="lines,vars,source"> > > <classpath> > > <path refid="framework-classpath"/> > > <pathelement location="build/core/classes"/> > > </classpath> > > </javac> > > * <native2ascii encoding="UTF-8" > > src="ui-core/src/main/native2ascii" dest="build/ui-core/classes" > > includes="**/*.properties" />* > > </target> > > > > By adding this line, the build is now OK. We can do a PR tomorrow for > > that if needed. > > > > Thanks, > > > > > > Olivier TAVARD > > Directeur Général - Cofondateur > > France Labs – Makers of Datafari Enteprise Search > > Datafari Enterprise Search <https://www.datafari.com> > > <https://www.milipol.com/Visiter/Inscription-visiteurs> > > > > <https://www.milipol.com/Visiter/Inscription-visiteurs>[image: > > image003.jpg] > > > > Le 9 oct. 2023 à 18:32, Karl Wright <daddy...@gmail.com> a écrit : > > > > I looked very briefly at this and discovered that every message is > > affected. > > It may be due, therefore, to jetty refusing access to the translation > > resources. But if that's the case I'm not going to be able to do > anything > > to get this release out this month; I'm booked solid in fact until > January. > > > > So good luck, folks. I'd try rolling the Jetty version update back if > you > > can as a first step. > > > > Karl > > > > > > On Mon, Oct 9, 2023 at 9:08 AM Karl Wright <daddy...@gmail.com> wrote: > > > > No change to paths has been made. > > Probably the translation files have been corrupted due to many merges and > > perhaps bad encodings for some of them. It will need to be looked into. > > Karl > > > > > > On Mon, Oct 9, 2023 at 8:40 AM Guylaine BASSETTE < > > guylaine.basse...@francelabs.com> wrote: > > > > Hello all, > > > > We have tested this version and everything is OK, except for translation, > > something is broken: > > > > It looks like the translations files are not found anymore. Maybe a > > change in the path to those files ? > > Best regards, > > Guylaine > > > > France Labs – Your knowledge, now > > Datafari Enterprise Search – Découvrez la version 5 / Discover our > > version 5 > > www.datafari.com > > > > Retrouvez-nous à Milipol <https://www.milipol.com/> du 14 au 17 novembre > > > > Le 06/10/2023 à 09:31, Karl Wright a écrit : > > > > Hi all, > > > > The tentative release schedule had a release going out on Sept 30th, > which > > is now overdue. Partly this was because of me, but also partly it's the > > result of new contributions from France Labs. But these contributions > are > > now committed to trunk and we could go ahead - unless others are expected > > to be coming shortly, in which case we should wait. Please let me know. > > > > In any case, if I don't hear back by this weekend I will try to create a > > release candidate then. > > > > Karl > > > > > > >
