Draft: go-text rendering support#298
Conversation
be23e85 to
8628e8a
Compare
|
So far, I have go the glyph identifiers from the |
|
Hi, I think you need to convert from runes to shaped glyphs first, using Then, you loop through the |
All right, I made adjustments but now I'm getting a weird issue where one of the glyphs do not appear. Seems like it might be because it is https://en.wikipedia.org/wiki/Visarga which in Unicode is a "placeholder glyph character". This is the PostScript that is generating the above image: BT
10.00 814.62 TD
/F1 14 Tf 0 Tc
[43<0093>47<0098>37<00E8>43<008F>0<022F>] TJ
ETI used |
|
Is there any progress? |


A couple of months ago MayankFawkes posted about a rendering issue with Hindi #293 which prompted a discussion on font rendering go-text/typesetting#159.
Related Issues:
[QUESTION] Can we use it with gopdf go-text/typesetting#159
Support for Other languages 01walid/goarabic#8
I can not use Arabic language in pdf #50
Right to Left language support #96
Displaying proper malayalam text on PDF using Go lang gopdf #126
Print glyph #143
Incorrect Rendering of Devanagari #153
gopdf not support RTL and Persian (Farsi) language #178
how to get ttl file that support chinese charactor well? #251
Right to Left does not work properly on multicell, Works correctly on Text #291
HIndi Rendering Problem #293
I have created a draft pull request to explore integrating go-text as a separate renderer besides the gopdf one and would love some guidance on how to proceed in completing this feature.
Below is an image of a test implementation with
go-text/renderon the top and the typical rendering on the bottom. It only renders an image though, so the text cannot be selected as intended:Edit:
The test file no longer renders with
go-text/render, as it became apparent I needed to use the low-leveltypesettingcore module instead, so my process now involves adapting thefont.Facestructure to update glyph positioning in the native font rendering.