tounicode | easiest Laravel package to convert Zawgyi

I was able to get access to sftp.

I run the below script and use filezilla to download the files.

Because the files where named after their ID's, we are able to link to the actual parent record

The user simply needs to parse the URL first:

The problem is that you're continuously creating a new instance of the MainWindow, so the spinbox used for tracking the number of processes always has the default initial value, 1.

You're also doing the same error more than once, and you're not even using the cached_property for the TaskManager.

A possible solution is to pass the main window instance to the task manager, so that it will use the actual value of the spinbox. Consider that this is not a very elegant solution, as the task manager should probably know nothing about the main window, and all communication should happen using more signals and slots.

Here is a way to do it:

If you want to terminate the connection when the window closes then do it in the closeEvent method:

Virtual key to character conversion depending on the locale:

PDFBox text extraction works according to Algorithm presented in section 9.10.2 "Mapping Character Codes to Unicode Values" of the PDF specification ISO 32000-1. When trying to apply this algorithm to your file, it fails to extract the text drawn with the SimSun font embedded subset (F2):

• "If the font dictionary contains a ToUnicode CMap" - F2 does not have a ToUnicode CMap.
• "If the font is a simple font" - F2 is not a simple font.
• "If the font is a composite font" - F2 indeed is a composite font, but ...
  • "that uses one of the predefined CMaps listed in Table 118 (except Identity–H and Identity–V)" - F2 uses Identity-H.
  • "or whose descendant CIDFont uses the Adobe-GB1, Adobe-CNS1, Adobe-Japan1, or Adobe-Korea1 character collection" - F2 uses the PDFXC30-Identity character collection.
• If these methods fail to produce a Unicode value, there is no way to determine what the character code represents in which case a conforming reader may choose a character code of their choosing.

Thus, text extraction as implemented in PDFBox cannot extract that Chinese text.

An alternative source for text information during text extraction presented in the PDF specification are ActualText entries for structure elements or marked-content sequences. But your PDF does not have any such ActualText entries either.

Thus, Adobe Acrobat copy&paste (which uses a combination of the algorithm mentioned before and ActualText analysis) cannot extract that Chinese text.

So "copy with formating" in Adobe Acrobat Pro apparently must use some information beyond those mechanisms proposed by the PDF specification.

Inspecting the embedded font resource itself one can see that it neither contains own mappings to Unicode nor any standard names. It is notable, though, that the glyph numbers are not consecutively numbered but have gaps. Probably these numbers have been retained from the full font during subsetting.

Adobe Acrobat Pro, therefore, appears to do either of the following options during "copy with formating" of your Chinese text:

• They know the details of the PDFXC30-Identity character collection, either officially from PDF-XChange or by reverse-engineering, and extract using that information.
• (If the assumption is correct that glyph numbers have been retained from the full font during subsetting:) They know the SimSun font and have a glyph number to Unicode mapping to use for extraction.
• They take a full copy of the SimSun font (either provided internally or by the host OS), compare the glyphs therein with those in the embedded subset, and derive a mapping to Unicode from that for text extraction.
• They apply OCR to the individual glyphs of the embedded font and derive a mapping to Unicode from the results.

Googling around for the PDFXC30-Identity character collection one sees that there are numerous text extraction tools having issues with it, e.g. on the Aspose forums one can read:

Our team has looked into this issue and I would like to share with you that the software you used to create the sample PDF files used PDFXC30 character collection. This character collection is not standard and we don’t have any information about this encoding. This makes correct text extraction impossible at the moment.

(shahzadlatif most recent response in the PdfExtractor encoding issue thread)

If you can provide PDFXC30 character collection mapping files from a trustable source, PDFBox development may include them into PDFBox to enable text extraction for files like yours.

In general I think pdf text can be compressed/encoded by different algorithms hence pdfrw doesn't decode text by itself. So you can't know what is the correct way in general, 'cause it is different for each case. I've tried simple pdf from here and it contains just plain text inside.

Probably you didn't figure out what is the correct correspondence between characters and hex codes is due to the fact that it may be a compressed stream - it means each code depends on the position of character in whole stream plus on the value of all previous characters. E.g. text may be zlib compressed.

Also pdf text is a sequence of commands for positioning/formatting/outputing text, so in general you have to be able to decode/encode all these commands to be able to process really any text. Your format may contain symbol table where all used symbols are mapped to hex value. To figure out correct mapping all symbols should be present in example text.

For your case you might probably use next table, for conversion, I use the fact that letter R has hex value 0x34:

Try it online!

First of all, what you call letter conjunctions usually is known as ligatures. Thus, I will use that term here from now on.

Unicode discourages the use of specific code points for ligatures:

The existing ligatures exist basically for compatibility and round-tripping with non-Unicode character sets. Their use is discouraged. No more will be encoded in any circumstances.

Ligaturing is a behavior encoded in fonts: if a modern font is asked to display “h” followed by “r”, and the font has an “hr” ligature in it, it can display the ligature. Some fonts have no ligatures, while others (especially fonts for non-Latin scripts) have hundreds of ligatures. It does not make sense to assign Unicode code points to all these font-specific possibilities.

(Unicode FAQ on ligatures)

Thus, you should not use the existing ligature code points.

You appear to attempt to find the correct ToUnicode mapping for ligature glyphs. For this simply remember that the values of ToUnicode mappings do not need to be single code points but may be multiple ones:

n beginbfchar
srcCode dstString
endbfchar
where dstString may be a string of up to 512 bytes.

(ISO 32000-1, section 9.10.3 ToUnicode CMaps)

Concerning your example, therefore:

For example, <012E> Tj will print fi like attached picture. But in its corresponding Font's ToUnicode CMap: <012E> <0001>, which is meaningless.

Simply use