- edited description
Error: Illegal entry in bfchar block in ToUnicode CMap
During import from an IMAP Server:
Error: Illegal entry in bfchar block in ToUnicode CMap
ist displayed. Reading http://www.linuxquestions.org/questions/linux-software-2/pdftotext-returns-illegal-entry-in-bfchar-block-in-tounicode-cmap-4175517312/ this can be a problem with the local settings.
My local settings are:
LANG=de_DE.UTF-8
LC_CTYPE="de_DE.UTF-8"
LC_NUMERIC="de_DE.UTF-8"
LC_TIME="de_DE.UTF-8"
LC_COLLATE="de_DE.UTF-8"
LC_MONETARY="de_DE.UTF-8"
LC_MESSAGES="de_DE.UTF-8"
LC_PAPER="de_DE.UTF-8"
LC_NAME="de_DE.UTF-8"
LC_ADDRESS="de_DE.UTF-8"
LC_TELEPHONE="de_DE.UTF-8"
LC_MEASUREMENT="de_DE.UTF-8"
LC_IDENTIFICATION="de_DE.UTF-8"
LC_ALL=
Can it be that this is the problem? I have tested:
LANG=en_US.utf8 && cd /tmp && pilerimport -i 192.168.130.191 -u mailarchive@*******.de -p *******l
without any success. How can get detailed information about the imported message which is producing the error? Was this mail archived?
Piler 1.1.0, build 884,
Comments (4)
-
reporter -
repo owner Well, it's a pdftotext issue, not a piler one. If you can identify the problematic message, then export the pdf file, and test it with pdftotext to figure out whether it can process it or not. Fortunately pilerimport can archive the message, worst case (very worst case) the contents of the pdf won't be indexed and can't be searched. Anyway not sure how to fix it on piler's side.
-
reporter Okay, thanks. Can work with this, thats ok for me.
Good job man!
-
reporter - changed status to closed
- Log in to comment