xournal-devel — discussions among developers (not for feature requests:those go on the tracker)

[Xournal-devel] Search text on pdf background

[Eduardo P. <edu...@ho...>]

Dear all,
      I have been using xournal to read and take notes on papers and books for a long time.  I love xournal because  it is a very light and  powerful software.  However, for reading and taking notes on papers and books it is very useful to be able  to search for text on pdf background. I was testing xournalpp, which includes this functionality and many others but it is slow and has a problem with the absolute location of the pdf background directory, which is very troublesome for me. I was looking at  "Various third-party patches" on the xournal webpage and I found a thread about  "search text on pdf background" but I cannot find the implementation of this functionality. I would like any help on the "search text on pdf background" funtionality for xournal.
Thanks!

[Xournal-devel] Search text on pdf background

[Eduardo P. <edu...@ho...>]

Dear all,
      I have been used xournal to read and take notes on papers and books for a long time.  I love xournal because  it is a very light and  powerful software.  However, for reading and taking notes on papers and books it is very useful to can search text on pdf background. I was testing xournalpp, which includes this functionality and many others but it is slow and has a problem with the absolute location of the pdf background directory, which is very troublesome for me. I was looking at  "Various third-party patches" on the xournal webpage and I found a thread about  "search text on pdf background" but I can not find the implementation of this functionality. I would like any help on the "search text on pdf background" funtionality for xournal.
Thanks!

Re: [Xournal-devel] [xournal:bugs] Re: #69 unable to insert custom/external page into PDF

[Denis A. <au...@ma...>]

Copying xournal-devel since there's an actual UI proposal further down 
this message (in fact several -- as usual with me, there's the first 
idea, then the amended hopefully better idea).  The question is how to 
adjust the xournal file to create/delete xoj pages when the PDF file it 
annotates changes in length, possibly by having pages inserted/deleted 
in the middle of it rather than at the end.

On 04/04/2017 01:41 AM, Ragnarok wrote:
> Just wondering if it might be possible/feasible to compare the total
> number of pages actually present in the linked PDF file, and the largest
> page number mentioned in the XOJ file, each time the XOJ file is opened.
> If there is a mismatch in the two, the following actions could be taken:
> /If the PDF file has fewer pages than the XOJ file, the annotations in
> the XOJ file's extra pages are placed on blank pages.
> / If the PDF file has more pages than the XOJ file, the extra PDF pages
> are just inserted as backgrounds with no annotations to the end of the
> XOJ file.

This is not a good idea in general, because many people (at least me) 
annotate PDF files but insert blank pages of "plain paper" for extra 
comments in between PDF pages wherever extra space is needed. So I might 
have a page of handwritten annotations between pages 3 and 4 of the PDF 
file, etc. etc.

> If I'm not mistaken, I don't see any real need to maintain a one-to-one
> relation between PDF and XOJ pages, hence requiring no change to the
> GUI. For instance, if an extra page is added to the middle of the PDF
> file, the XOJ file is not aware of this and one-to-one correlation is
> lost anyway.

Indeed -- but then the GUI should help the user fix the correlation in 
the right way, because:

> This is not really an issue even, since as I mentioned
> before, I could just shift all annotations in the XOJ file down by one
> page to solve this problem.

How do you propose to do this? There is no easy way to move a whole 
page, especially if
there are several layers on it, and there is even less of a way to move 
a range of pages.

> I could, similarly, move all annotations up
> by one page if I delete a page from the PDF file (I haven't tried this
> feature yet, but I'm assuming it would work if I'm viewing my PDF file
> in continuous mode).

No it doesn't -- sorry! Continuous is a *viewing* mode, doesn't change the
behavior of the drawing tools which still work one layer at a time on 
one page
at a time.

So: the right thing to do is instead add an entry or two in the page 
menu. Most
obviously, one that sets the background of the current page to be page 
<N> of the
PDF for your favorite value of N.  Then by using Page -> New Page 
After/Before
and this new command, you can create the extra pages you need and assign 
them to
the PDF pages you want.  Second, there should be a bit of magic that 
figures when
you are trying to adjust PDF page numbers and asks if you are trying to 
adjust all
following page numbers as well.

Initial thought: Perhaps the new commands should be

- Page -> Paper style -> PDF page: sets background of current page to 
specified PDF page
- Page -> Adjust PDF Pages After: asks for a number k of pages to shift 
by, if run on
a xoj page that annotates page n of the PDF and k is positive then 
creates k new blank
xoj pages that annotate pages n+1, ..., n+k of the PDF, and shifts all 
PDF pages greater
than n in subsequent xoj pages by +k.  If k is negative, then replaces 
backgrounds in
subsequent xoj pages by blank background if page number is n+1, ..., 
n+|k|, and shifts
PDF page numbers by k for page numbers greater than n+|k|.

Example, if I'm currently having backgrounds in the xoj that are PDF pages
1 2 3 blank 4 5 6 blank 7
and on xoj page 5 = PDF page 4 I ask to adjust PDF pages after by 2, 
then it inserts two blank pages annotating pages 5 and 6, and the pages 
with backgrounds 5 6 blank 7 become 7 8 blank 9.
Whereas if I ask to adjust by -2, then no xoj page disappears but the 
backgrounds become 1 2 3 blank 4 blank blank blank 5.

Perhaps for simplicity there should also be Page -> Adjust PDF Pages at 
End (that does it at the end of the file).

Revised thought, which I think is better: Instead of creating Page -> 
Adjust PDF Pages, this should be just built into Page -> New Page 
Before/After/At End, and Page -> Delete Page. Namely, when running a 
"new page" command when the current (or last) page is annotating a PDF, 
then New Page should ask the user whether the new page is blank, a 
duplicate of the current PDF page, or a new PDF page to insert by 
shifting all PDF page numbers by 1. And similarly Delete Page should ask 
whether to shift all remaining PDF page numbers by 1.  This is probably 
much more intuitive than creating a new command "adjust PDF pages" -- 
the user who wants to fix pages will probably try to add or remove pages 
in the xoj and might reasonably expect xournal to adjust the xoj/pdf 
page correspondence as this happens, so this is where we should ask. 
(One would still have Page -> Paper style -> PDF page  to allow for 
manual adjustments whenever needed).

Is this reasonable?

Further thoughts for beyond phase 1:

- As an additional bit of magic, "New page at End" could detect if the 
last PDF page used is less than the current PDF file page count and ask 
if you want to create all the missing pages at once if more than one. 
(Not going to happen in phase 1 of the plan, don't get your hopes up. I 
assume that doing things one page at a time will still be useful at 
first and should handle the most pressing needs).

- Yet another issue is that xournal does not refresh when the PDF 
changes under its nose (even though printing/exporting might in some 
cases work with the PDF file on disk rather than the one shown on 
screen). Perhaps the File menu should contain an entry to refresh the 
PDF background. I don't know if this is easy to do though, I think it 
may be easier to just do the current thing and ask the user to save and 
re-open the xoj as a way to refresh the PDF. One could imagine however 
an automagic command that refreshes by saving (prompting the user of 
course), re-opening the xoj, and then detects if page count has 
increased in the PDF and offers to create new pages at end if needed. Or 
even better, perhaps we should monitor the PDF file for changes (not all 
the time, perhaps only after specific operations such as scrolling 
beyond a page or saving the file) and, if it has changed, prompt the 
user whether they want to save and re-open to refresh the PDF.  What do 
you think?


Denis

-- 
Denis Auroux
UC Berkeley, Department of Mathematics
817 Evans Hall, Berkeley CA 94720-3840, USA
au...@ma...

[Xournal-devel] translation in Italian updated

[Marco C. <ci...@li...>]

Hello Xournal devs!
attached (hoping that attached files allowed)
there is the Italian translation (from git master) updated.
Please apply.

TIA

PS: reply directly to me, I am not subscribed to this list

Regards,

-- 


Marco Ciampa

I know a joke about UDP, but you might not get it.

------------------------

 GNU/Linux User #78271
 FSFE fellow #364

------------------------

Re: [Xournal-devel] fix for xournal crash (finding icon)

[Florian B. <me...@th...>]

Hi,

* Denis Auroux <au...@ma...> [2017-03-19 22:29:12 -0400]:
> Hi Daniel (and Florian assuming he reads this mailing list),

I do ;-)

> I'm very confused. The link you give gives an error 404, I can't find 
> the original bug report anymore, and I can't reproduce the problem.

FWIW the 0.4.8 release seems to work fine for me too.

> There is a comment from Florian about the original code improperly using 
> a pointer allocated on the stack, I've been looking through the code he 
> removed/replaced and can't find the problem (+ there is another very 
> similar function create_pixmap() that was not put into question).

This turned out to be a red herring. The real reason (which I
mentioned in the GitHub issues, which are indeed turned off now?!) was
that - at least on the next branch - create_pixbuf was not declared
properly (haven't checked the details, presumably missing from the
header file? In any case, there was a compiler warning).

This caused the compiler to implicitly assume int, which happens to be
compatible with a void*, which means the code worked fine on 32bit
systems, but segfaulted on 64bit (because the returned pointer got
truncated).

Florian

-- 
http://www.the-compiler.org | me...@th... (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/

Re: [Xournal-devel] fix for xournal crash (finding icon)

[Denis A. <au...@ma...>]

Hi Daniel (and Florian assuming he reads this mailing list),

I'm very confused. The link you give gives an error 404, I can't find 
the original bug report anymore, and I can't reproduce the problem.

I don't see how this patch is supposed to work in improving things. In 
the original code,

gtk_window_set_icon(..., create_pixbuf("xournal.png"));

create_pixbuf() is pretty careful about error checking and returns NULL 
whenever something goes wrong; and the manual for gtk_window_set_icon() 
explicitly says that it's ok to pass NULL.

When I delete xournal.png, I get a
** (xournal:27193): WARNING **: Couldn't find pixmap file: xournal.png
as expected, but everything works fine.

Meanwhile, the proposed replacement code doesn't look obviously cleaner 
to me in any way -- for example it only ensures that the file exists but 
doesn't check whether it can be successfully loaded as an image; and the 
behavior of gtk_window_set_default_icon_from_file() on an invalid file 
is not completely clear to me (presumably warning and go on), but in any 
case I don't see the benefit.

There is a comment from Florian about the original code improperly using 
a pointer allocated on the stack, I've been looking through the code he 
removed/replaced and can't find the problem (+ there is another very 
similar function create_pixmap() that was not put into question).

Help please?

Thanks in advance,
Denis


On 03/19/2017 04:17 PM, D M German wrote:
>
> Hi Denis,
>
> you might remember this bug:
>
> https://github.com/dmgerman/xournal/issues/30
>
> I tracked it and it was present in official xournal
>
> Florian Bruhin provided a fix and I created  patch to apply to official
> xournal. It is available here:
>
> https://github.com/dmgerman/xournal/tree/icon
>
> thanks Denis,
>
> --dmg
>
> --
> Daniel M. German                  "None but those who have experienced
>    Mary Shelley (Frankenstein) ->  them can conceive of the enticements of science."
> http://turingmachine.org/
> http://silvernegative.com/
> dmg (at) uvic (dot) ca
> replace (at) with @ and (dot) with .
>

-- 
Denis Auroux
UC Berkeley, Department of Mathematics
817 Evans Hall, Berkeley CA 94720-3840, USA
au...@ma...

[Xournal-devel] fix for xournal crash (finding icon)

[D M G. <dm...@tu...>]

Hi Denis,

you might remember this bug:

https://github.com/dmgerman/xournal/issues/30

I tracked it and it was present in official xournal

Florian Bruhin provided a fix and I created  patch to apply to official
xournal. It is available here:

https://github.com/dmgerman/xournal/tree/icon

thanks Denis,

--dmg

--
Daniel M. German                  "None but those who have experienced
   Mary Shelley (Frankenstein) ->  them can conceive of the enticements of science."
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .

Re: [Xournal-devel] Fwd: Arrow Tool / Getting into development

[dmg <dm...@tu...>]

Hi Hans,

thank you for trying this. Is there a place where we can download the
patches?

thank you!

--dmg

On Fri, Mar 17, 2017 at 2:25 PM, Hans Rochus <gor...@gm...>
wrote:

> Hi,
>
> thanks for your very in depth answer. I just got to try this two days ago
> and got it working!. I've added a few more points to the existing polyline
> inside continue_stroke() to create an arrow head. Now I wanted to switch
> between the ordinary ruler and my modified one. This was quite a hurdle and
> certainly isn't nice looking code. I didn't want to create a new tool from
> scratch, as that would have taken a lot longer. Instead I added a new int
> to the UIData struct, that serves as a switch for the different "ruler
> tools". This int can be modified by a GtkMenuToolButton in the toolbar,
> which has multiple radio items (the button itself does nothing). All these
> items are connected to the same handler and by comparing the sender's label
> to strings the int value gets set (What could possibly go wrong? Well
> translation is an issue for sure. I think there is a possibility to send
> this data over the gpointer user_data, but I didn't try that one). With
> this information I can select the tool that will be applied
> inside continue_stroke(). Currently the UI looks like this (i don't know if
> embedded pictures will work here):
>
> [image: Inline-Bild 1]
> [image: Inline-Bild 2]
> Its not really clean and forward, but I have to leave it at that for now.
> Changing the ruler toggle button into a radio control required changing
> code in parts of Xournal that caused a myriad of new problems. I didn't
> want to face those without a debugger.
> Maybe you have a better idea on how to handle all this. As it is now, I'm
> quite happy as these were my most wanted features.
>
> Thanks again,
>
> Mo.
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Xournal-devel mailing list
> Xou...@li...
> https://lists.sourceforge.net/lists/listinfo/xournal-devel
>
>


-- 
--dmg

---
Daniel M. German
http://turingmachine.org

[Xournal-devel] Fwd: Arrow Tool / Getting into development

[Hans R. <gor...@gm...>]

Hi,

thanks for your very in depth answer. I just got to try this two days ago
and got it working!. I've added a few more points to the existing polyline
inside continue_stroke() to create an arrow head. Now I wanted to switch
between the ordinary ruler and my modified one. This was quite a hurdle and
certainly isn't nice looking code. I didn't want to create a new tool from
scratch, as that would have taken a lot longer. Instead I added a new int
to the UIData struct, that serves as a switch for the different "ruler
tools". This int can be modified by a GtkMenuToolButton in the toolbar,
which has multiple radio items (the button itself does nothing). All these
items are connected to the same handler and by comparing the sender's label
to strings the int value gets set (What could possibly go wrong? Well
translation is an issue for sure. I think there is a possibility to send
this data over the gpointer user_data, but I didn't try that one). With
this information I can select the tool that will be applied
inside continue_stroke(). Currently the UI looks like this (i don't know if
embedded pictures will work here):

[image: Inline-Bild 1]
[image: Inline-Bild 2]
Its not really clean and forward, but I have to leave it at that for now.
Changing the ruler toggle button into a radio control required changing
code in parts of Xournal that caused a myriad of new problems. I didn't
want to face those without a debugger.
Maybe you have a better idea on how to handle all this. As it is now, I'm
quite happy as these were my most wanted features.

Thanks again,

Mo.

Re: [Xournal-devel] Arrow Tool / Getting into development

[Denis A. <au...@ma...>]

Hi there,

Just adding points to ui.cur_path.coords (and adjusting num_points) is 
not necessarily enough, because that is just a temporary points array 
used while drawing -- at the end of the process, ui.cur_path will 
eventually get inserted into the page and drawn.  For regular drawing, 
create_new_stroke() allocates ui.cur_item and fills some of the data; 
continue_stroke() updates ui.cur_path and draws segments as the pen is 
being moved; and finalize_stroke() takes care of finishing the job: 
cleans up the data in ui.cur_path, copies it into ui.cur_item->path, 
updates the gnome canvas structures, and adds ui.cur_item onto 
ui.cur_layer->items to make it part of the page's data structures.

You won't need to do all these things yourself, but you do need to make 
sure that the place where you modify ui.cur_path's contents is before 
the moment where it gets copied into data structures that will remain in 
place in the journal.

Easy case: If your arrow is going to be part of the same polyline as the 
stroke is goes onto, i.e. the stroke + arrow are all a single connected 
polygonal shape, then you can indeed insert it at the beginning of 
finalize_stroke() (updating ui.cur_path.coords and num_points) and the 
code will take care of it.

Hard case: If the arrow is its own separate polyline, then it will 
become a distinct item both in gnomecanvas (for display) and in 
ui.cur_layer (for data storage), so you need to make sure those get 
created, and that the creation operation can be undone. The best place 
to look for such things is indeed the shape recognizer.

In xo-shapes.c, try_arrow() will take existing strokes and create 
several strokes, if you look at the end of the code for try_arrow(), we 
create several stroke items by hand. The fastest way to do it is just 
the same as the way the arrow head is created at the end of try_arrow():

   realloc_cur_path(3);
   ui.cur_path.num_points = 3;
   ui.cur_path.coords[0] = x2 - dist*cos(angle+delta);
   ui.cur_path.coords[1] = y2 - dist*sin(angle+delta);
   ui.cur_path.coords[2] = x2;
   ui.cur_path.coords[3] = y2;
   ui.cur_path.coords[4] = x2 - dist*cos(angle-delta);
   ui.cur_path.coords[5] = y2 - dist*sin(angle-delta);
   insert_recognized_curpath();

We make sure cur_path is large enough for 3 points, fill in the 
coordinates, and then insert the new curpath into the journal.

*However* you can't use insert_recognized_curpath() as is, because it 
assumes that a recognizer operation is in progress and the undo stack 
contains an "ITEM_RECOGNIZER" entry, with a list of erasures already in 
place. (See the first 6 lines of code in remove_recognized_strokes(), 
which gets called before any call to insert_recognized_curpath(): we 
create a new undo item).

You can either piggyback on this, making your arrows in a "recognizer" 
undo operation (this has implications for the undo process, it'll undo 
in two stages) but with no erasures if you are not removing any 
user-drawn stroke to replace it with the arrow, and calling 
insert_recognized_curpath();  or make a different function similar to 
insert_recognized_curpath() but that doesn't place information into the 
undo stack in this particular way (instead makes an ITEM_STROKE undo 
operation).

Sorry if this is technical, but that is not the easiest part of the code 
to modify if you want to create an extra polyline along the way -- 
easiest if you just make the arrowhead part of the same continuously 
drawn polyline as the stroke, in that case just add your arrow points to 
ui.cur_path at the beginning of finalize_stroke() (before cur_path gets 
copied into other data structures and redrawn on screen).

Denis

On 01/28/2017 07:22 AM, Homo Fürst wrote:
> Hi,
>
> I just got around to building xournal-next on Windows and would like to
> add a few tools (not using the shape recognizer, as i want more control
> over size and position), although I can't seem to understand the source
> code all that well. For guidance I looked at code which defines the
> ruler paths in xo_paint.c in the following functions:
>
> - void create_new_stroke(GdkEvent *event)
> - void continue_stroke(GdkEvent *event)
> - void finalize_stroke(void)
>
> Now my idea is to add new points to that path, so I can add an arrow
> head after the straight line (like this: ----|>) . Where would one
> insert these points? In xo_shapes.c make_circle_shape() adds points to
> the ui.cur_path.coords array, but I can't seem to get it to work this way.
>
> I'd be grateful for any guidance in this direction.
>
> Also, it took me quite some time getting Xournal and gtk2 to build on
> Windows (using MSYS2 / mingw64). If anyone is interested, I posted
> updated instructions in the SourceForge forum
>
> Thanks,
>
> Mo.
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>
>
>
> _______________________________________________
> Xournal-devel mailing list
> Xou...@li...
> https://lists.sourceforge.net/lists/listinfo/xournal-devel
>

-- 
Denis Auroux
UC Berkeley, Department of Mathematics
817 Evans Hall, Berkeley CA 94720-3840, USA
au...@ma...

[Xournal-devel] Arrow Tool / Getting into development

[Homo F. <gor...@gm...>]

Hi,

I just got around to building xournal-next on Windows and would like to add
a few tools (not using the shape recognizer, as i want more control over
size and position), although I can't seem to understand the source code all
that well. For guidance I looked at code which defines the ruler paths in
xo_paint.c in the following functions:

- void create_new_stroke(GdkEvent *event)
- void continue_stroke(GdkEvent *event)
- void finalize_stroke(void)

Now my idea is to add new points to that path, so I can add an arrow head
after the straight line (like this: ----|>) . Where would one insert these
points? In xo_shapes.c make_circle_shape() adds points to the
ui.cur_path.coords array, but I can't seem to get it to work this way.

I'd be grateful for any guidance in this direction.

Also, it took me quite some time getting Xournal and gtk2 to build on
Windows (using MSYS2 / mingw64). If anyone is interested, I posted updated
instructions in the SourceForge forum

Thanks,

Mo.

Re: [Xournal-devel] Crash with xournal-next

[Denis A. <au...@ma...>]

> Romano, Denis, I think this issue has been fixed in next. Immi was very
> good at fixing it. But I have not had time to test it, so I'll
> appreciate it if you let us know if the bug has been addressed.

I think I took a look a long while ago and it was ok. I just looked 
again at the patch to xo-file.c addressing the issue and I think it 
looks ok. Sorry I can't test seriously now (in the middle of New York -> 
Berkeley -> France -> Berkeley -> Los Angeles -> Princeton with kids, so 
no hope of getting anything done), but I believe that indeed Immi fixed 
the issue well.  I'm also aware that I'm supposed to review and 
incorporate at least parts of this into upstream at some point; 
hopefully sometime this semester once I'm settled in Princeton (but 
don't hold your breath).

Denis

Re: [Xournal-devel] Crash with xournal-next

[D M G. <dm...@tu...>]

 Denis Auroux twisted the bytes to say:


 Denis> Hi Romano,
 Denis> I'm happy to take a look at the xoj file (no need to send the pdf) even though I'm not directly involved in
 Denis> xournal-next.  Daniel (cc-ed) might also appreciate a copy.  With your permission, if this is related as I suspect to
 Denis> one of Immi Halupczok's recent patches, can we forward the xoj file to him if we determine his patch is likely to be the
 Denis> cause of the problem? (if you'd prefer not, we can also try to reproduce the problem separately).

This was one of my worst terms in a some time. But it is over and I
can now go back to my normal life. :)

Romano, Denis, I think this issue has been fixed in next. Immi was very
good at fixing it. But I have not had time to test it, so I'll
appreciate it if you let us know if the bug has been addressed.

--dmg



 Denis> On 10/05/2016 12:05 PM, Romano Gtti (comp) wrote:
 >> Hi,
 >> 
 >> I am using xournal-next (satisfactorily) in the last couple of
 >> weeks, but today I have found a problem. One the file that I edited
 >> refuses to open (I do not know since when). I closed it after exporting
 >> (no error) and now it segfaults on opening:
 >> 
 >> 
 >> [romano:~/software/bugs/xournal] % xournal test2.xoj
 >> 
 >> (xournal:6334): GnomeCanvas-CRITICAL **: gnome_canvas_points_new:
 >> assertion 'num_points > 1' failed
 >> [1]    6334 segmentation fault (core dumped)  xournal test2.xoj
 >> [romano:~/software/bugs/xournal] 139 %
 >> 
 >> 
 >> The document is a report correction (writing over a PDF), and
 >> there should be no privacy problem in posting it without the associated
 >> PDF (no names/references to people) but I would feel better in sending
 >> it privately to anyone that want to try to debug it.
 >> 
 >> Thanks!
 >> 
 >> Romano
 >> 
 >> 

 Denis> -- 
 Denis> Denis Auroux
 Denis> UC Berkeley, Department of Mathematics
 Denis> 817 Evans Hall, Berkeley CA 94720-3840, USA
 Denis> au...@ma...

--
Daniel M. German                  "You cannot have the success without 
   H. G. Hasler ->                 the failures."
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .

 

Re: [Xournal-devel] Xournal double

[David v. r. <dav...@gm...>]

Hi Torsten,

I have answered your questions below. And i realized that i really don't
have time to start writing on this again, but i would be happy to answer
any other questions, or help debugging.

Hope it helps.

2016-10-13 16:05 GMT+02:00 Torsten Wagner <tor...@gm...>:

> Hi again,
> I gave it a try again.
> I still struggle to get it working. However, it could be due to my tiling
> window manager (i3wm).
> 1. I did not find a way to get the second screen really in full screen. I
> always end up with some gray boarders.
>
I also use a tiling wm (awesome) and i tend to always use the fullscreen
function of it instead of the app. But there is as of yet no button to make
it go fullscreen.

> 2. I can see a kind of frame but independently of what I choice from the
> lower right selection box, it seems not to fit and the frame is not fitting
> to the slides (created by LaTeX Beamer).
>
In the lower right selection box, only 'top left corner' is implemented
completely yet.

> 3. I have no idea what the pencil button is for, seems to have no effect
>
 It is the toggle for the pointer indicator on the child window. Except for
now it only works if you hide and show the child window first.

> 4. Loading a PDF, I still have an overlay of blue ruled paper background
> in both windows.
>
Yes, this was by request, because i was writing this for a job at the time.
It should be a setting somewhere, but i didn't have time to implement it
that way.

>
> Would be very glad if someone could tell me how it should work, if he can
> reproduce the problems, or simply tell me that this problems might be on my
> side.
>
> Thanks
>
> Torsten
>
>
> On 13 October 2016 at 15:19, Torsten Wagner <tor...@gm...>
> wrote:
>
>> I am not a developer but I am highly interested in this.
>> For the moment I use Xorg capabilities to show a part of the main
>> screen on the secondary screen. This works surprisingly well but
>> requires tweaking whenever the display resolution of the projector
>> changes.
>> In addition to have a second screen I would love to have the feature
>> to "freeze" the second screen thus, it allows me to scroll through the
>> pages without confusing the audience. Or to do annotations and update
>> them in one go on the second screen.
>> Other then this, there was a friendly fork which included a side-bar
>> to show the slides in a scrolling list. I modified the code a bit to
>> make those thumbnails a bit bigger, which allows me nicely move up and
>> down the list to select a certain slide/page. Would really be happy to
>> have this two features within xournal.
>>
>
>

Re: [Xournal-devel] Xournal double

[Torsten W. <tor...@gm...>]

Hi again,
I gave it a try again.
I still struggle to get it working. However, it could be due to my tiling
window manager (i3wm).
1. I did not find a way to get the second screen really in full screen. I
always end up with some gray boarders.
2. I can see a kind of frame but independently of what I choice from the
lower right selection box, it seems not to fit and the frame is not fitting
to the slides (created by LaTeX Beamer).
3. I have no idea what the pencil button is for, seems to have no effect
4. Loading a PDF, I still have an overlay of blue ruled paper background in
both windows.

Would be very glad if someone could tell me how it should work, if he can
reproduce the problems, or simply tell me that this problems might be on my
side.

Thanks

Torsten


On 13 October 2016 at 15:19, Torsten Wagner <tor...@gm...>
wrote:

> I am not a developer but I am highly interested in this.
> For the moment I use Xorg capabilities to show a part of the main
> screen on the secondary screen. This works surprisingly well but
> requires tweaking whenever the display resolution of the projector
> changes.
> In addition to have a second screen I would love to have the feature
> to "freeze" the second screen thus, it allows me to scroll through the
> pages without confusing the audience. Or to do annotations and update
> them in one go on the second screen.
> Other then this, there was a friendly fork which included a side-bar
> to show the slides in a scrolling list. I modified the code a bit to
> make those thumbnails a bit bigger, which allows me nicely move up and
> down the list to select a certain slide/page. Would really be happy to
> have this two features within xournal.
>

Re: [Xournal-devel] Xournal double

[Torsten W. <tor...@gm...>]

I am not a developer but I am highly interested in this.
For the moment I use Xorg capabilities to show a part of the main
screen on the secondary screen. This works surprisingly well but
requires tweaking whenever the display resolution of the projector
changes.
In addition to have a second screen I would love to have the feature
to "freeze" the second screen thus, it allows me to scroll through the
pages without confusing the audience. Or to do annotations and update
them in one go on the second screen.
Other then this, there was a friendly fork which included a side-bar
to show the slides in a scrolling list. I modified the code a bit to
make those thumbnails a bit bigger, which allows me nicely move up and
down the list to select a certain slide/page. Would really be happy to
have this two features within xournal.

Re: [Xournal-devel] Crash with xournal-next

[Romano G. (comp) <rom...@rg...>]

On 09/10/16 14:13, Immi Halupczok wrote:
> Ok, I found the bug. It has nothing to do with the -nan; instead, the
> problem is that my code doesn't handle fixed-width strokes properly.
> I'll fix it in a minute.
>
>             Immi

Hi, has the fix been pushed/integrated in xournal-next? Because I can't 
still open the file ;-)...
Thanks,
      Romano

-- 
--
Romano Giannetti
http://www.rgtti.com

Re: [Xournal-devel] Xournal double

[Immi H. <im...@ka...>]

Hi,

I also tried it, and I'd also like to use it (and to improve it, if I 
find time). I created a new branch xournal-double in my repository 
(github.com/immi-h/xournal) which is the master branch with the changes 
from xournal-double merged in. (I also tried to rebase xournal-double to 
master, but this created a lot of conflicts, so it would have been much 
more work.)

I also tried whether it would be easy to merge it into next; as I 
expected, there will be a bunch of conflicts to be resolved.

How do we want to proceed? I think xournal-double is not yet in a state 
to be part of xournal-next. Should we keep it as a branch from master 
for now, polish it a bit and then deal with merging it into next?

I'm happy to work on this when I find time, but I don't know yet when 
that will be (and whether that will really happen).

Best,
      Immi




Am 09.10.2016 um 22:00 schrieb David:
> Hi Daniel,
>
> It is nice to hear someone likes the changes. By now my working on this has stalled, so if you want to write some stuff it would be awesome. I would also like to write some more but i have too many projects as it is so  it won't be much :(
> Answers to your questions below :
>
> On Sun Oct 9 01:35:23 2016 GMT+0200, D M German wrote:
>>  David van rijn twisted the bytes to say:
>>
>>
>>  David> Hello Xournal developers,
>>  David> I have been working on XournalDouble
>>  David> <https://github.com/unsanded/xournalDouble>. A version of xournal which has
>>  David> a separate *presentation window* for giving live presentations. I think
>>  David> with some work, it could be merged back into the original, making the
>>  David> second window an option.
>>  David> Can you please let me know wheter you are interested in this? So i can make
>>  David> proper preparations.
>>
>> Hi David,
>>
>> I am sorry it took me this long to reply. I am going to start using your
>> feature for presentations. I have a couple of questions: Let me call the
>> master window the one with the menus and the child window the other.
>>
>> 1. Is there a way to maximize the child window?
>>
> For now not really. I am not really in to window manager api, so i wasn't  not sure how to do this.
>> 2. how do you control the zoom factor in the child window?
> In the latest version on git there are some window-follow-modes (eg scroll together ) which are not all implemented. Also zoom buttons. Look for the toolbar at the bottom of the main window. There is also a button which shows the location of the child window.
>>
>> 3. Is there a way to distinguish the child window from the master
>>    window (from the point of view of the window manager?
>
> Same as 1.
>>
>> thanks again, this is a great feature that will certainly help me when I
>> present pdfs. I have simply mirror one screen into the other.
>>
>>
>>
>> --daniel
>>
>>
>>
>>
>>  David> Yours,
>>
>>  David> David
>>  David> ------------------------------------------------------------------------------
>>  David> Find and fix application performance issues faster with Applications Manager
>>  David> Applications Manager provides deep performance insights into multiple tiers of
>>  David> your business applications. It resolves application problems quickly and
>>  David> reduces your MTTR. Get your free trial!
>>  David> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>>  David> _______________________________________________
>>  David> Xournal-devel mailing list
>>  David> Xou...@li...
>>  David> https://lists.sourceforge.net/lists/listinfo/xournal-devel
>>
>> --
>> Daniel M. German                  "Don't try to be like Jackie.
>>                                    There is only one Jackie...
>>    Jackie Chan ->                  Study computers instead"
>> http://turingmachine.org/
>> http://silvernegative.com/
>> dmg (at) uvic (dot) ca
>> replace (at) with @ and (dot) with .
>>
>>
>>
>

Re: [Xournal-devel] Xournal double

[David <dav...@gm...>]

Hi Daniel, 

It is nice to hear someone likes the changes. By now my working on this has stalled, so if you want to write some stuff it would be awesome. I would also like to write some more but i have too many projects as it is so  it won't be much :( 
Answers to your questions below : 

On Sun Oct 9 01:35:23 2016 GMT+0200, D M German wrote:
>  David van rijn twisted the bytes to say:
> 
> 
>  David> Hello Xournal developers,
>  David> I have been working on XournalDouble
>  David> <https://github.com/unsanded/xournalDouble>. A version of xournal which has
>  David> a separate *presentation window* for giving live presentations. I think
>  David> with some work, it could be merged back into the original, making the
>  David> second window an option.
>  David> Can you please let me know wheter you are interested in this? So i can make
>  David> proper preparations.
> 
> Hi David,
> 
> I am sorry it took me this long to reply. I am going to start using your
> feature for presentations. I have a couple of questions: Let me call the
> master window the one with the menus and the child window the other.
> 
> 1. Is there a way to maximize the child window?
>
For now not really. I am not really in to window manager api, so i wasn't  not sure how to do this.  
> 2. how do you control the zoom factor in the child window?
In the latest version on git there are some window-follow-modes (eg scroll together ) which are not all implemented. Also zoom buttons. Look for the toolbar at the bottom of the main window. There is also a button which shows the location of the child window.  
> 
> 3. Is there a way to distinguish the child window from the master
>    window (from the point of view of the window manager?

Same as 1. 
> 
> thanks again, this is a great feature that will certainly help me when I
> present pdfs. I have simply mirror one screen into the other.
> 
> 
> 
> --daniel
> 
> 
> 
> 
>  David> Yours,
> 
>  David> David
>  David> ------------------------------------------------------------------------------
>  David> Find and fix application performance issues faster with Applications Manager
>  David> Applications Manager provides deep performance insights into multiple tiers of
>  David> your business applications. It resolves application problems quickly and
>  David> reduces your MTTR. Get your free trial!
>  David> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>  David> _______________________________________________
>  David> Xournal-devel mailing list
>  David> Xou...@li...
>  David> https://lists.sourceforge.net/lists/listinfo/xournal-devel
> 
> --
> Daniel M. German                  "Don't try to be like Jackie.
>                                    There is only one Jackie...
>    Jackie Chan ->                  Study computers instead"
> http://turingmachine.org/
> http://silvernegative.com/
> dmg (at) uvic (dot) ca
> replace (at) with @ and (dot) with .
> 
>  
>

-- 
Sent from my Jolla

Re: [Xournal-devel] Crash with xournal-next

[Immi H. <im...@ka...>]

Am 09.10.2016 um 00:55 schrieb D M German:
>  Immi Halupczok twisted the bytes to say:
>
>
>  Immi> Concerning -nan:
>  Immi> I can confirm that normal xournal doesn't crash, next does. And I just
>  Immi> tried: line-widths-optimized does not crash. (So chances are smaller
>  Immi> that it's my fault ;-) )
>
>          Immi
>
> It was :)

Ok, I found the bug. It has nothing to do with the -nan; instead, the 
problem is that my code doesn't handle fixed-width strokes properly. 
I'll fix it in a minute.

           Immi

>
> it crashes here in the code to unify the first two points. See below.
>
> I have commented on your patch. Let me know what you think.
>
> #0  __memmove_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:244
> #1  0x000000000042053b in memmove (__len=<optimized out>, __src=<optimized out>, __dest=<optimized out>)
>     at /usr/include/x86_64-linux-gnu/bits/string3.h:59
> #2  xoj_parser_text (context=<optimized out>, text=0xa6ec98 " \n", text_len=2, user_data=<optimized out>,
>     error=0x7fffffffdbf8) at xo-file.c:1032
> #3  0x00007ffff550121b in g_markup_parse_context_parse () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #4  0x0000000000421335 in open_journal (filename=filename@entry=0x984570 "/tmp/test2.xoj") at xo-file.c:1166
> #5  0x0000000000414af3 in init_stuff (clOptions=0x7fffffffe150) at main.c:377
> #6  0x0000000000413a69 in main (argc=2, argv=0x7fffffffe268) at main.c:552
>
>
>
>  Immi> Am 06.10.2016 um 20:01 schrieb dmg:
>  >> This is the stroke that is crashing xournal:
>  >>
>  >> <stroke tool="pen" color="red" width="1.41">
>  >> -nan -nan -nan -nan -nan -nan -nan -nan
>  >> </stroke>
>  >>
>  >>
>  >>
>  >> On Thu, Oct 6, 2016 at 10:42 AM, D M German <dm...@tu...
>  >> <mailto:dm...@tu...>> wrote:
>  >>
>  >> Romano Gtti twisted the bytes to say:
>  >>
>  Romano> I used the ruler a bit in the document, and yes, sometime I
>  >> use it with the mouse (to underline text etc. and make big
>  Romano> boxes, which are difficult to achieve with the mouse and
>  >> the shpe recognizer). So maybe this was the culprit.
>  >>
>  Romano> BTW, I removed that stroke from the file but I am still
>  >> unable to read it. Probably there is something more around. I
>  Romano> think that not saving such a 0-length segment is ok, but a
>  >> bit of defensive programming in reading it (like emit a
>  Romano> warning and ignoring it) could be nice to have...
>  >>
>  >> I presume that the best method to determine the culprit is to:
>  >>
>  >> - decompress the file: rename to file.xoj.gz and run gunzip on it
>  >> - do binary splicing of the file:
>  >> - remove half, does it load? If so, it the error is in the other half.
>  >> - do recursively until error found
>  >>
>  >> --dmg
>  >>
>  >>
>  >>
>  Romano> Romano
>  >>
>  Romano> Thanks for the effort
>  >>
>  >>
>  >>
>  Romano> --
>  Romano> --
>  Romano> Romano at http://www.rgtti.com/
>  >>
>  >>
>  >> --
>  >> Daniel M. German                  "Un libro es un amigo a voluntad...
>  >> puede convertirse en alacena
>  >> de recuerdos,en cántaro de deseos,o
>  >> Germán Dehesa ->               en ánfora de ensueños."
>  >> http://turingmachine.org/
>  >> http://silvernegative.com/
>  >> dmg (at) uvic (dot) ca
>  >> replace (at) with @ and (dot) with .
>  >>
>  >>
>  >>
>  >>
>  >>
>  >> --
>  >> --dmg
>  >>
>  >> ---
>  >> Daniel M. German
>  >> http://turingmachine.org
>
>  Immi> ------------------------------------------------------------------------------
>  Immi> Check out the vibrant tech community on one of the world's most
>  Immi> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>  Immi> _______________________________________________
>  Immi> Xournal-devel mailing list
>  Immi> Xou...@li...
>  Immi> https://lists.sourceforge.net/lists/listinfo/xournal-devel
>
> --
> Daniel M. German                  "In other studies you go as far as
>                                    others have gone before you,
>     ->                             and"
> http://turingmachine.org/
> http://silvernegative.com/
> dmg (at) uvic (dot) ca
> replace (at) with @ and (dot) with .
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Xournal-devel mailing list
> Xou...@li...
> https://lists.sourceforge.net/lists/listinfo/xournal-devel
>

Re: [Xournal-devel] Xournal double

[Immi H. <im...@ka...>]

Hi,

I'm also very interested in this feature, and I'm happy to help 
integrating it into next - though I cannot guarantee yet that I'll find 
time for that.

Best,
      Immi


Am 09.10.2016 um 01:35 schrieb D M German:
>  David van rijn twisted the bytes to say:
>
>
>  David> Hello Xournal developers,
>  David> I have been working on XournalDouble
>  David> <https://github.com/unsanded/xournalDouble>. A version of xournal which has
>  David> a separate *presentation window* for giving live presentations. I think
>  David> with some work, it could be merged back into the original, making the
>  David> second window an option.
>  David> Can you please let me know wheter you are interested in this? So i can make
>  David> proper preparations.
>
> Hi David,
>
> I am sorry it took me this long to reply. I am going to start using your
> feature for presentations. I have a couple of questions: Let me call the
> master window the one with the menus and the child window the other.
>
> 1. Is there a way to maximize the child window?
>
> 2. how do you control the zoom factor in the child window?
>
> 3. Is there a way to distinguish the child window from the master
>    window (from the point of view of the window manager?
>
> thanks again, this is a great feature that will certainly help me when I
> present pdfs. I have simply mirror one screen into the other.
>
>
>
> --daniel
>
>
>
>
>  David> Yours,
>
>  David> David
>  David> ------------------------------------------------------------------------------
>  David> Find and fix application performance issues faster with Applications Manager
>  David> Applications Manager provides deep performance insights into multiple tiers of
>  David> your business applications. It resolves application problems quickly and
>  David> reduces your MTTR. Get your free trial!
>  David> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
>  David> _______________________________________________
>  David> Xournal-devel mailing list
>  David> Xou...@li...
>  David> https://lists.sourceforge.net/lists/listinfo/xournal-devel
>
> --
> Daniel M. German                  "Don't try to be like Jackie.
>                                    There is only one Jackie...
>    Jackie Chan ->                  Study computers instead"
> http://turingmachine.org/
> http://silvernegative.com/
> dmg (at) uvic (dot) ca
> replace (at) with @ and (dot) with .
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Xournal-devel mailing list
> Xou...@li...
> https://lists.sourceforge.net/lists/listinfo/xournal-devel
>

Re: [Xournal-devel] Inclusion of PDFs

[D M G. <dm...@tu...>]

 Michael J Gruber twisted the bytes to say:


 Michael> That get's you only so far if you want to include, say, multiple graphs
 Michael> into your lecture notes. I can convert PDF to PNG, of course, but that
 Michael> seems to be moot if Xournal knows how to render PDFs (using poppler),
 Michael> and besides the unnecessary increase in file size (embedded PNG), this
 Michael> also makes it difficult to update an xoj with updated graphs.

 Michael> So, ideally I would like to "include" PDFs as links to the PDF (just
 Michael> like the annotated PDFs), multiple ones per xoj page. I don't mind
 Michael> editing an xoj by hand (vim to the rescue...).

I think it would be a nice feature to have (to be able to insert PDFs
into the pages). We will need a volunteer to do the coding though :)

--dm

--
Daniel M. German                  "None but those who have experienced
   Mary Shelley (Frankenstein) ->  them can conceive of the enticements of science."
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .

 

Re: [Xournal-devel] Xournal double

[D M G. <dm...@tu...>]

 David van rijn twisted the bytes to say:


 David> Hello Xournal developers,
 David> I have been working on XournalDouble
 David> <https://github.com/unsanded/xournalDouble>. A version of xournal which has
 David> a separate *presentation window* for giving live presentations. I think
 David> with some work, it could be merged back into the original, making the
 David> second window an option.
 David> Can you please let me know wheter you are interested in this? So i can make
 David> proper preparations.

Hi David,

I am sorry it took me this long to reply. I am going to start using your
feature for presentations. I have a couple of questions: Let me call the
master window the one with the menus and the child window the other.

1. Is there a way to maximize the child window?

2. how do you control the zoom factor in the child window?

3. Is there a way to distinguish the child window from the master
   window (from the point of view of the window manager?

thanks again, this is a great feature that will certainly help me when I
present pdfs. I have simply mirror one screen into the other.



--daniel




 David> Yours,

 David> David
 David> ------------------------------------------------------------------------------
 David> Find and fix application performance issues faster with Applications Manager
 David> Applications Manager provides deep performance insights into multiple tiers of
 David> your business applications. It resolves application problems quickly and
 David> reduces your MTTR. Get your free trial!
 David> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
 David> _______________________________________________
 David> Xournal-devel mailing list
 David> Xou...@li...
 David> https://lists.sourceforge.net/lists/listinfo/xournal-devel

--
Daniel M. German                  "Don't try to be like Jackie.
                                   There is only one Jackie...
   Jackie Chan ->                  Study computers instead"
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .

 

Re: [Xournal-devel] Few more patches for Xournal

[D M G. <dm...@tu...>]

Hi Gi,

 Ti> 2. Allow customizing the ruling parameters.

   I like different ruling spacing, and less harsh colors etc. My patch
   saves these ruling parameters into the journal itself in a backward
   compatible way. (If you open these journals with a vanilla xournal
   you don't get an error; but your custom ruling isn't shown of course.
   And a journal saved by a vanilla Xournal, will open just fine in the
   patched Xournal and it will use the default ruling parameters).

I will merge this feature into xournal-next, but I need some help from
you. Would you mind doing the following?

1. Split the code of this feature from the rest of your code.

2. Create a branch with this code on top of Denis' master.

once you have that, I'll integrate it into -next.

It will also allow Denis to integrate the changes much easier, if he
chooses to.

Regarding the other two:

--dmg

--
Daniel M. German                  "The problem in the old days
                                   when you were working with
                                   one piece of film is,
   Jeff Wall ->                    it's like triage, you had to take the least bad."
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .

 

Re: [Xournal-devel] Crash with xournal-next

[D M G. <dm...@tu...>]

 Immi Halupczok twisted the bytes to say:


 Immi> Concerning -nan:
 Immi> I can confirm that normal xournal doesn't crash, next does. And I just 
 Immi> tried: line-widths-optimized does not crash. (So chances are smaller 
 Immi> that it's my fault ;-) )

         Immi

It was :)

it crashes here in the code to unify the first two points. See below.

I have commented on your patch. Let me know what you think. 

#0  __memmove_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:244
#1  0x000000000042053b in memmove (__len=<optimized out>, __src=<optimized out>, __dest=<optimized out>)
    at /usr/include/x86_64-linux-gnu/bits/string3.h:59
#2  xoj_parser_text (context=<optimized out>, text=0xa6ec98 " \n", text_len=2, user_data=<optimized out>, 
    error=0x7fffffffdbf8) at xo-file.c:1032
#3  0x00007ffff550121b in g_markup_parse_context_parse () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x0000000000421335 in open_journal (filename=filename@entry=0x984570 "/tmp/test2.xoj") at xo-file.c:1166
#5  0x0000000000414af3 in init_stuff (clOptions=0x7fffffffe150) at main.c:377
#6  0x0000000000413a69 in main (argc=2, argv=0x7fffffffe268) at main.c:552



 Immi> Am 06.10.2016 um 20:01 schrieb dmg:
 >> This is the stroke that is crashing xournal:
 >> 
 >> <stroke tool="pen" color="red" width="1.41">
 >> -nan -nan -nan -nan -nan -nan -nan -nan
 >> </stroke>
 >> 
 >> 
 >> 
 >> On Thu, Oct 6, 2016 at 10:42 AM, D M German <dm...@tu...
 >> <mailto:dm...@tu...>> wrote:
 >> 
 >> Romano Gtti twisted the bytes to say:
 >> 
 Romano> I used the ruler a bit in the document, and yes, sometime I
 >> use it with the mouse (to underline text etc. and make big
 Romano> boxes, which are difficult to achieve with the mouse and
 >> the shpe recognizer). So maybe this was the culprit.
 >> 
 Romano> BTW, I removed that stroke from the file but I am still
 >> unable to read it. Probably there is something more around. I
 Romano> think that not saving such a 0-length segment is ok, but a
 >> bit of defensive programming in reading it (like emit a
 Romano> warning and ignoring it) could be nice to have...
 >> 
 >> I presume that the best method to determine the culprit is to:
 >> 
 >> - decompress the file: rename to file.xoj.gz and run gunzip on it
 >> - do binary splicing of the file:
 >> - remove half, does it load? If so, it the error is in the other half.
 >> - do recursively until error found
 >> 
 >> --dmg
 >> 
 >> 
 >> 
 Romano> Romano
 >> 
 Romano> Thanks for the effort
 >> 
 >> 
 >> 
 Romano> --
 Romano> --
 Romano> Romano at http://www.rgtti.com/
 >> 
 >> 
 >> --
 >> Daniel M. German                  "Un libro es un amigo a voluntad...
 >> puede convertirse en alacena
 >> de recuerdos,en cántaro de deseos,o
 >> Germán Dehesa ->               en ánfora de ensueños."
 >> http://turingmachine.org/
 >> http://silvernegative.com/
 >> dmg (at) uvic (dot) ca
 >> replace (at) with @ and (dot) with .
 >> 
 >> 
 >> 
 >> 
 >> 
 >> --
 >> --dmg
 >> 
 >> ---
 >> Daniel M. German
 >> http://turingmachine.org

 Immi> ------------------------------------------------------------------------------
 Immi> Check out the vibrant tech community on one of the world's most 
 Immi> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
 Immi> _______________________________________________
 Immi> Xournal-devel mailing list
 Immi> Xou...@li...
 Immi> https://lists.sourceforge.net/lists/listinfo/xournal-devel

--
Daniel M. German                  "In other studies you go as far as 
                                   others have gone before you,
    ->                             and"
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .