[Okular-devel] [okular] [Bug 321956] Make paragraphs look nicer (indent them properly)

2013-07-07 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=321956

Christoph Feck christ...@maxiom.de changed:

   What|Removed |Added

   Severity|normal  |minor

--- Comment #3 from Christoph Feck christ...@maxiom.de ---
The line and uneven letter spacing adds to the impression.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Okular-devel mailing list
Okular-devel@kde.org
https://mail.kde.org/mailman/listinfo/okular-devel


Re: [Okular-devel] Review Request 111410: Selection tool: copy/extract as vector graphic by calling pdftocairo

2013-07-07 Thread Thomas Fischer

---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111410/
---

(Updated July 7, 2013, 10:22 p.m.)


Review request for Okular.


Changes
---

 it's not in the correct place, why is all this exporting
 functionality in pageview.cpp? If at all this should be
 integrated with the File-Export functionality and not be
 coded in pageview.cpp but in the proper appropiate backend
This is a misunderstanding. My code does not export whole pages (which 
File-Export implies and what pdftocairo supports, too), but only the user's 
selection just like the existing text and image extraction. I made some 
screenshots which should clarify the situation: 
http://imgur.com/iHxAws1,Vgjbb5l,VavhqMv (img #1: new context menu when 
selecting a region of a PDF page; img #2: bitmap as extract with the current 
Image solution; img #3: PDF file extract using the Vector option, opened in 
Okular)
The location of the code in pageview.cpp is therefore justified as the image 
and text extract code is located in the same class. However, I agree that 
pageview.cpp is rather large and should be refactored.

Having a vector graphic extract is an serious feature. As my screenshots 
document, if you want to extract a tiny piece of a PDF file, the existing 
bitmap feature gives you an image of the size as you see it. Inserting such 
bitmaps in other documents or slides results in badly scaled images. Obviously, 
a vector graphic does not suffer from this problem.

 I don't think calling an external tool is a good idea,
 but it is true it's the only easy way to provide the
 functionality
Indeed. As pdftocairo's code is Gtk-based, inserting it into Okular may cause 
problems on its own. The best solution I would see is if the Qt4 backend would 
support this feature or if a solution using QPrinter-to-PDF would work. I could 
investigate those two options, but only if there is a realistic chance that the 
result will be included in Okular.


Description
---

This patch implements the feature request of bug 321350: if a PDF file is 
viewed, the selection tool offers the new extraction method vector which 
allows to save to a file (PDF, SVG, EPS, PostScript). The crop operation is 
performed by calling pdftocairo with matching arguments. The resulting file 
contains the original PDF file's content without rendering it to a pixmap.

I am not sure if calling an external program is an acceptable solution for this 
problem. However, it is tested if the program is available before showing the 
new option. Alternatively, the code of pdftocairo (as part of poppler) would 
had to be copied and integrated into Okular increasing the solution's 
complexity. I am not aware of a similar solution available using poppler-qt4 
only. Maybe using a QPrinter printing to PDF would have been an alternative, 
but again this seemed to be too complex.


Diffs (updated)
-

  ui/pageview.cpp 16b00ab 

Diff: http://git.reviewboard.kde.org/r/111410/diff/


Testing
---


Thanks,

Thomas Fischer

___
Okular-devel mailing list
Okular-devel@kde.org
https://mail.kde.org/mailman/listinfo/okular-devel


Re: [Okular-devel] Review Request 110003: Best-fit zoom

2013-07-07 Thread Thomas Fischer

---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/110003/
---

(Updated July 7, 2013, 11:04 p.m.)


Review request for Okular.


Changes
---

The patch reflects two changes based on comments in the Forum. First, it 
renames the feature to auto fit which a majority of comments support as a 
better name than best fit.
Second, I am trying to add Auto Fit as one of the default zoom settings in 
the configuration dialog. Although I was quite sure I did not miss a spot and 
the option turns up in the settings dialog, choosing Auto Fit does not get 
activated when restarting Okular. Any hints what goes wrong?


Description
---

Attached patch implements best-fit zoom for Okular. It is a refined version of 
the patch submitted in bug report 249364, attachment 51069. The refinement 
addresses the scrollbar issues as observed in continuous view mode.


This addresses bug 249364.
http://bugs.kde.org/show_bug.cgi?id=249364


Diffs (updated)
-

  conf/dlggeneralbase.ui f2c9efd 
  conf/okular.kcfg 1e23d61 
  part.rc 64aeffb 
  ui/pageview.h 5484cc5 
  ui/pageview.cpp 16b00ab 

Diff: http://git.reviewboard.kde.org/r/110003/diff/


Testing
---


Thanks,

Thomas Fischer

___
Okular-devel mailing list
Okular-devel@kde.org
https://mail.kde.org/mailman/listinfo/okular-devel