*** Bug 13441 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters change when selecting text
Status in Poppler:
F
*** Bug 9608 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters change when selecting text
Status in Poppler:
Fi
(In reply to comment #54)
> I'm not convinced this bug is fixed; see the attachment images from my
> evince 3.10.3 in Ubuntu 14.04.
>
> Or is this a different issue?
That is a different issue. Please open a new bug, attach the PDF, and
include your libpoppler version.
--
You received this bug
Created attachment 104776
Selected/Corrupted text with evince 3.10.3 (Ubuntu 14.04)
I'm not convinced this bug is fixed; see the attachment images from my
evince 3.10.3 in Ubuntu 14.04.
Or is this a different issue?
--
You received this bug notification because you are a member of Desktop
Packa
Created attachment 104775
Unselected text with evince 3.10.3 (Ubuntu 14.04)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters change when selecting text
Status i
This bug was fixed in the package poppler - 0.22.4-0ubuntu1
---
poppler (0.22.4-0ubuntu1) saucy; urgency=low
* New upstream release 0.22.4 (LP: #1135995).
- Should fix the text selection problems (LP: #39890).
- Should fix issues with PDF forms (LP: #1153517).
* Drop all u
** No longer affects: evince (Ubuntu)
** Changed in: poppler (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters ch
** Branch linked: lp:ubuntu/saucy-proposed/poppler
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters change when selecting text
Status in Poppler:
Fix Released
** Branch linked: lp:~mitya57/ubuntu/saucy/poppler/0.22.4
** Branch unlinked: lp:~mitya57/ubuntu/saucy/poppler/0.22.3
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
chara
Unfortunately, this bug is still present in Poppler 0.20.5 on Ubuntu
13.04.
When I open my test case (attachment 66101) in Evince and try to select
the "2m+α" part, it changes to "20+=" every time. Should I reopen this
bug or file a new one instead?
--
You received this bug notification because
(In reply to comment #51)
> Unfortunately, this bug is still present in Poppler 0.20.5 on Ubuntu 13.04.
Please ignore that, it seems that Poppler version is too old in Ubuntu.
Will prepare an update now :)
--
You received this bug notification because you are a member of Desktop
Packages, which
** Branch linked: lp:~mitya57/ubuntu/saucy/poppler/0.22.3
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters change when selecting text
Status in Poppler:
Fix Re
** Changed in: poppler
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters change when selecting text
Status in Poppler:
(In reply to comment #47)
> I've commited this patch to master (what will be 0.22) and not to 0.20 since
> it
> breaks the public glib api
Really? why? I agree with not committing it to the stable branch, but I
don't think the patch breaks the API, or am I missing something?
Breaking the API shou
(In reply to comment #49)
> Oh, wait, didn't realize the functions it's adding new parameters are private,
> ignore my "breaks API" part.
No problem :-) but please, ask me before committing any change that
might break the public glib API even in master.
--
You received this bug notification beca
Oh, wait, didn't realize the functions it's adding new parameters are
private, ignore my "breaks API" part.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters chang
I've commited this patch to master (what will be 0.22) and not to 0.20
since it breaks the public glib api
I'm closing this bug since it fixes the original reported issue. If
there are issues not fixed by this bug please open a new one, big bugs
get difficult to keep track of otherwise.
--
You r
Created attachment 66450
Check for NaN in TextPage::addChar
I don't think this is related to my earlier patch. For me, this pdf
crashes both with and without it. This document is doing very strange
things with the current transformation matrix (CTM) and inline images.
Pages 6 and 15 are filled wi
Created attachment 66163
Change default fallback character width
Also, I don't know how you feel about fixing something caused by
violating the PDF specification, but this patch changes the default
width for a missing character, making the gamma symbol selectable in the
minimal pdf.
--
You recei
Created attachment 66375
The pdf where the patch crashes
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters change when selecting text
Status in Poppler:
Confirm
Created attachment 66454
Allow multiple fonts in a TextWord
Updated patch to apply to current git master.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters change
(In reply to comment #37)
> Created attachment 65992 [details] [review]
> Allow multiple fonts in a TextWord
>
> It was possible for a TextWord to have fonts for both horizontal and vertical
> writing modes. This version of the patch starts a new word when the WMode
> changes.
When running pdfto
Yes, please review the patch as it is.
I have looked at the document from Dmitry. It exposes two issues, but
these are separate from minimal pdf. 1) TextLines may be drawn over
each other, obscuring other text. 2) In
CairoOutputDev::updateFillColor, the color may not be set correctly.
--
You
Jason want me to have another look at your patch or you want to try to
fix the issue by Dmitry first?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters change when
Created attachment 66101
Another small test case
The patch doesn't fully solve the problem for me. I have attached
another PDF file (which only contains one math formula) with which I
still can reproduce the issue.
When I try to select the Sigma ("∑") in Evince, limits ("m=0" and "∞")
disappear;
Created attachment 65992
Allow multiple fonts in a TextWord
It was possible for a TextWord to have fonts for both horizontal and
vertical writing modes. This version of the patch starts a new word
when the WMode changes.
--
You received this bug notification because you are a member of Desktop
I am not sure how to fix the problem with the Gamma glyph not being
selectable. It is not selectable because it has a zero width, because
there is no Widths array in the file. This is a violation of the spec.
Poppler has a mechanism to provide default widths, but this does not
work for symbols.
I tried patched poppler with the minimal example and I don't get the
change of the glyphs anymore under the selection, which is VERY GOOD!!
But I can't select the Gamma glyph...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ub
(In reply to comment #33)
> I understand why they are not merged (by code not, why the code is put there),
> but why the "i" has a different width that makes it overlap with the "K" when
> previously didn't?
Before being merged, the width of the 'i' is 0.923076. In
TextWord::merge, the right edge
Ok, let's not worry about that for the moment. I'm more concerned about
Carlos not being able to verify this indeed fixes the problem it's
supposed to be fixing.
Carlos can you give it a second try?
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
(In reply to comment #32)
> The difference in character width is because of this change:
>
> @@ -863,7 +839,7 @@ void TextLine::coalesce(UnicodeMap *uMap) {
> word0->spaceAfter = gTrue;
> word0 = word1;
> word1 = word1->next;
> - } else if (word0->font == word1->font &&
> +
The difference in character width is because of this change:
@@ -863,7 +839,7 @@ void TextLine::coalesce(UnicodeMap *uMap) {
word0->spaceAfter = gTrue;
word0 = word1;
word1 = word1->next;
- } else if (word0->font == word1->font &&
+ } else if (word0->font[word0->l
There's also a weird thing.
If i get all the character positions and dump them to file, sometimes
there's minor changes, e.g. in
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/881407/+attachment/2571595/+files
/Manning-ExtJS_in_Action.pdf
the diff says
--- old/foo 2012-08-17 01:16:21
(In reply to comment #29)
> Note i have *not* verified it fixes the problem mentioned in this bug. Carlos
> can you do that part?
it's weird, I don't see any difference with and without the patch with
poppler-glib-demo and the minimal example attached to this bug.
--
You received this bug notif
Good news first, it does not change the output of pdftotext (well it
does it in a file, but i don't consider it a regression)
Yay :-)
Now onto the review of the code itself.
>From what i can read it seems it is possible to have in the same word
fonts with different WMode (i.e. fonts written vert
Sure, on my todo (man i'm behind again in poppler :-()
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters change when selecting text
Status in Poppler:
Confirmed
Sure, no hurry, thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters change when selecting text
Status in Poppler:
Confirmed
Status in “evince” package in
(In reply to comment #25)
> Created attachment 65449 [details] [review]
> Allow multiple fonts in a TextWord
>
> This patch modifies TextWord so that each character can be a different font.
> Function poppler_page_get_text_attributes is updated to allow for attributes
> to
> change mid-word.
Th
Albert: given the lack of a space ( ) in the input, there's shouldn't be
one in the output! :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters change when select
Created attachment 65449
Allow multiple fonts in a TextWord
This patch modifies TextWord so that each character can be a different
font. Function poppler_page_get_text_attributes is updated to allow for
attributes to change mid-word.
--
You received this bug notification because you are a membe
An interesting thing:
When I select the "Wrong" line in PDF from comment 2, BCDГ is changing not to
ABC, but to ABC, and when I then
copy-paste that line, I get "Wrong:BCD", without the last letter.
@José: Please, do something with this! Sometimes selecting text does
really terrible things (take
Dmitry please to not modify those fields, that's not for users to
choose.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters change when selecting text
Status in P
Paul: Of course, i never said this is an acceptable behaviour. (What
makes you think i did?)
I only said that from the technical point of view you can argue that ":"
is of course a different word since you won't find the word "strike:" in
a dictionary.
--
You received this bug notification becau
As there been any additional progress on this issue? I must say I have
been encountering it quite frequently for a long time, and for one would
be very happy to see a fix applied.
Anyway, thanks to anyone working on this.
--
You received this bug notification because you are a member of Desktop
I tend to agree with Paul that is fine for a word to have different
fonts, but on the other hand one can argue if the ":" in that situation
is part of the word or not.
I'd say 1 is a better solution but if you can get 2 with a "clean
enough" code i won't be oposed to it either.
Personally i think
It's perfectly natural that every letter in a word be in a different
font, colour, or style so that needs to be allowed for (the text could
even a scan of some handwriting, or several scans), . ...what pdftotext
is trying to do is to replicate what would be found in a Tagged PDF
(Section 9.7 of th
Thanks for the regression. The problem here is that "bold:" has two
fonts since "bold" is italicised and ":" not, so before the patch,
"bold:" is a TextWord and pdftotext get the text right, but drawing the
selection is bad since the selected ":" would be drawn italicised.
After the patch, "bold:
Created attachment 43455
The pdf with the pdftotext regression
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters change when selecting text
Status in Poppler:
C
The patch changes (breaks) the behaviour of pdftotext so that is not
acceptable. You can see that in the attached pdf
"bold strike:"
changes to be extracted to
"bold strike :"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ub
Created attachment 43421
updated alternate patch
I apologize for the spam. Previous patch was clearly wrong. Updated
patch.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
Created attachment 43420
alternate patch comparing gfxFont instead of pointers to FontInfos
Even if what I say in last comment may be true, I followed your advice and
updated the patch to compare the gfxFonts instead of the pointers to the
TextInfos.
--
You received this bug notification becau
I assumed that the only code that is updating the curFont is
TextPage::updateFont. If this is true, from what I understood from the
code, the fonts array holds unique FontInfos, so it would be safe to
compare pointers instead of FontInfos. So, is this right? If so, and you
still want me to rework t
You are comparing the pointers of the font infos, shouldn't you be
comparing the contents of the pointers?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters change
The last patch does not fix either some problems when selecting
ligatures in some fonts, see
http://java.sun.com/docs/books/jvms/second_edition/ClassFileFormat-
final-draft.pdf, page 54 and look for the word "reflective" which is
rendered as "reßective" (althought the text select is indeed
"reflect
Created attachment 43360
Patch fixing the issue
Actually, All the chars in a TextWord MUST share the same font, so I
added a check so we also create a new word when the font changes. The
attached patch fixes the bug in the minimal example and many other
problems when selecting text in PdfLatex-gen
For the problem in the minimal example, the culprit seems to be in
TextSelectionPainter::visitWord, which assumes that all the chars in a
word use the same font. This is demonstrated by adding a space After
"Word:" in the bad line. This also explain why this bug is very common
with LaTeX files.
--
** No longer affects: evince
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters change when selecting text
Status in Poppler:
Confirmed
Status in “evince” packag
Bug still there in Ubuntu 12.04, Evince 3.4.0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/39890
Title:
characters change when selecting text
Status in Evince document viewer:
Unk
58 matches
Mail list logo