cuneiform team mailing list archive

[Alex Samorukov <samm@xxxxxxxxxxx>]

Jussi Pakkanen wrote:
> Hi all
>
> There have been a lot of additions and bug fixes since 0.3.1, so maybe
> doing another release would be sensible.
>   
"Release Early, Release Often" :) Yes, I think this is a good idea. Some 
my notes about current project bugs:

https://bugs.launchpad.net/cuneiform-linux/+bug/261563
Please, reopen it. Image output on 1 bit images  is still buggy.

I found the problem and fixed it, it was related to incorrect bmp header 
calculation inside picture.cpp
But also then i found another problem - there is a bug inside strange 
function

ApplayMaskToDIB

In 64 bit mode it just return array of 0x00 instead of original bitmap. 
In 32 bit mode all is ok. If i`m commenting it out everything seems to 
work fine. I think it`s better to fix this bug before release because it 
affect html and rtf modes.

Also, as for me, https://bugs.launchpad.net/cuneiform-linux/+bug/261364 
would be fixed before new release. But currently I have no idea where it 
come from,  I only can confirm it.

So, as for me, it`s better to fix #261364 before new release.

Also  i created my (local) branch to support  UTF-8 inside engine, but 
currently it is far from completion, so we should not wait for it.

> To get started, are there any really jarring issues besides the
> crashing bugs that have already been filed to the bug tracker. Is
> there any (small scale) addition or change that you would like to see
> for the next release? Other comments are accepted as well.
>
> Thanks.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~cuneiform
> Post to     : cuneiform@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~cuneiform
> More help   : https://help.launchpad.net/ListHelp
>
>