Bug 247393 - Characters with accents not correctly handled
Characters with accents not correctly handled
Product: Fedora
Classification: Fedora
Component: poppler (Show other bugs)
All Linux
low Severity high
: ---
: ---
Assigned To: Kristian Høgsberg
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-07-08 17:53 EDT by Laurent Aguerreche
Modified: 2008-06-16 21:49 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-06-16 21:49:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
LaTeX file to reproduce a PDF with accentuated characters (407 bytes, text/x-tex)
2007-07-08 17:53 EDT, Laurent Aguerreche
no flags Details
Obtained PDF with pdflatex (27.27 KB, application/pdf)
2007-07-08 17:54 EDT, Laurent Aguerreche
no flags Details
Result from pdftotext (267 bytes, text/plain)
2007-07-08 17:55 EDT, Laurent Aguerreche
no flags Details

  None (edit)
Description Laurent Aguerreche 2007-07-08 17:53:31 EDT
Description of problem:
Accents not correctly handled by pdftotext.

How reproducible:

Steps to Reproduce:
1. execute pdftotext on a PDF containing some accents
2. open result and see what happened to characters with accents...

Actual results:
Characters with accents are replaced only by their accent or a strange character.

Expected results:
Characters with correct accents.

Additional info:
I send a test.tex to compile with pdflatex, the produced PDF and a text file
obtained with pdftotext.
Comment 1 Laurent Aguerreche 2007-07-08 17:53:31 EDT
Created attachment 158738 [details]
LaTeX file to reproduce a PDF with accentuated characters
Comment 2 Laurent Aguerreche 2007-07-08 17:54:35 EDT
Created attachment 158739 [details]
Obtained PDF with pdflatex
Comment 3 Laurent Aguerreche 2007-07-08 17:55:15 EDT
Created attachment 158740 [details]
Result from pdftotext
Comment 4 Bug Zapper 2008-05-14 09:27:29 EDT
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 5 Bug Zapper 2008-06-16 21:49:26 EDT
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 is no longer maintained, which means that it will not 
receive any further security or bug fix updates. As a result we 
are closing this bug. 

If you can reproduce this bug against a currently maintained version 
of Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.