Re: UIMAfit analysis descriptions appear to trim String configuration parameters

On Mon, Jun 15, 2015 at 8:43 AM, Mario Gazzo wrote: > I am referring to to this Github repo: > > https://github.com/apache/uima-uimafit < > https://github.com/apache/uima-uimafit> > > Thought it was published by you as a mirror of the SVN repo or the other > way around. > Yes, this is the offici

Re: UIMAfit analysis descriptions appear to trim String configuration parameters

Done :) https://issues.apache.org/jira/browse/UIMA-4464 Just pasted excerpts from this thread into the description. Cheers Mario > On 15 Jun 2015, at 08:50 , Richard Eckart de Castilho wrote: > > As far as I know, CPE does not work with in-m

Re: UIMAfit analysis descriptions appear to trim String configuration parameters

As far as I know, CPE does not work with in-memory descriptors (or I never dug deep enough). So if you use CPE (e.g. through the uimaFIT CpeBuilder or otherwise), there is probably some XML serialization of the descriptors involved. Anyway, I think that pinpoints the problem pretty precisely a

Re: UIMAfit analysis descriptions appear to trim String configuration parameters

I am referring to to this Github repo: https://github.com/apache/uima-uimafit Thought it was published by you as a mirror of the SVN repo or the other way around. The trimming is as such not a technical issue for me right now but I felt it might become

Re: UIMAfit analysis descriptions appear to trim String configuration parameters

Just as a quick feedback: uimaFIT (mind capitalization) is maintained in SVN, not in git. https://svn.apache.org/repos/asf/uima/uimafit I have no idea what repository you are referring to ;) Regarding the trimming, I have no idea right away. The parameter values are passed around quite a bit.

UIMAfit analysis descriptions appear to trim String configuration parameters

Using the new gapText parameter in UIMA Ruta HTMLConverter I noticed that the string is trimmed in the pipeline aggregation process e.g. “ . “ ends up as “.” in the pipeline and when writing the pipeline to XML. I don’t think it has anything to do with the HTMLConverter in particular. We use