On 2/7/2021 10:22 AM, Arrigo Marchiori wrote:
> Hello all,
>
> re-replying to Jim's message.
>
> On Wed, Feb 03, 2021 at 02:25:16PM -0500, Jim Jagielski wrote:
>
>> Funny that you bring this up... I'm been tracking down some bugs and they
>> all seem to be XML related...
Hello Peter, and thank you for taking time to reply.
On Sun, Feb 07, 2021 at 04:58:19PM +0100, Peter Kovacs wrote:
> Hello,
>
> On 07.02.21 16:22, Arrigo Marchiori wrote:
> > Hello all,
> >
> > re-replying to Jim's message.
> >
> > On Wed, Feb 03, 2021 at 02:25:16PM -0500, Jim Jagielski
Hello,
On 07.02.21 16:22, Arrigo Marchiori wrote:
Hello all,
re-replying to Jim's message.
On Wed, Feb 03, 2021 at 02:25:16PM -0500, Jim Jagielski wrote:
Funny that you bring this up... I'm been tracking down some bugs and they
all seem to be XML related... fastsax->libwriterfilter with
Hello all,
re-replying to Jim's message.
On Wed, Feb 03, 2021 at 02:25:16PM -0500, Jim Jagielski wrote:
> Funny that you bring this up... I'm been tracking down some bugs and they
> all seem to be XML related... fastsax->libwriterfilter with occasional cores
> due to __cxa_call_unexpected.
>
>
Hello Peter, All,
On Thu, Feb 04, 2021 at 12:00:44PM +0100, Peter Kovacs wrote:
> +1 for Option 3)
>
[... FTR ...]
> > 3- raise an exception because it is just not acceptable.
I believe it should be a subclass of uno::Exception, but... which one?
There seem to be a lot of Exception's
Hello Jim,
On Wed, Feb 03, 2021 at 02:25:16PM -0500, Jim Jagielski wrote:
> Funny that you bring this up... I'm been tracking down some bugs and they
> all seem to be XML related...
:-)
[...]
> I feel that making AOO more fragile by trying to work around cases where
> invalid and/or
+1 for Option 3)
On 03.02.21 19:38, Arrigo Marchiori wrote:
Dear List,
bug 128356 [1] is mostly about an XML tag that carries an attribute
_twice_. This is not allowed; the SAX parser raises an exception when
it finds it while loading the file, and the user gets upset because
they cannot open
Funny that you bring this up... I'm been tracking down some bugs and they
all seem to be XML related... fastsax->libwriterfilter with occasional cores
due to __cxa_call_unexpected.
I feel that making AOO more fragile by trying to work around cases where
invalid and/or non-compliant XML is
