Native FBInk: Another small tool to print crap on your screen!

[sherman]

Hi

Just a couple of notes for those using the new OpenType/TrueType functionality, as there are some differences compared to the traditional FBInk printing methods.

Unicode linebreaking is used for wrapping lines. This means, that when printing OT/TT, the line will try to avoid breaking mid-word.

OT support uses margins, instead of cells, for positioning. That means you can set a printable area with top, bottom, left and right margins. The margins are specified in pixels, so at the moment API users may want to use the fbink_get_state() function to get the current screen resolution.

You can also align text WITHIN the printable area defined by the margins. This allows for both horizontal and vertical alignment. With the combination of alignment and margins, some creative positioning can be obtained...

Bold and Italics support is enabled via a simple markdown syntax (eg *italic*, **bold**, ***bold italic***). This is a very simplistic parser, so I would advise doing anything to complicated with it. EDIT: and it will abort if you don't have the appropriate bold and/or italic font loaded, so beware!

Other than that, have fun!

Huge thanks to NiLuJe for letting me play in the FBInk sandbox, and for graciously polishing my code.

(Also, if NiLuJe ever offers you a copy of Bookerly, run far far away. It is an evil version of the font, which made my code blow up...)

[NiLuJe]

Just my luck that the second font I'd try would blow up in fun and interesting ways .

[PoP]

Yet another...

Spoiler:

#!/bin/sh
#FUNtastic.sh:
# Play with OpenType fonts and transparencies to write an appreciation message

cd /mnt/us
#expects PATH=$PATH:.:..

#Fill a background of karma
fbink -c  -C gray8 -t regular=/mnt/us/pantspatrol.ttf,size=8 "K2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2uK2Uk2u"

#Write over "FUNtastic"
fbink -t regular=/mnt/us/poplarstd.otf,size=86 "FUN" -M --bgless
fbink -t regular=/mnt/us/pantspatrol.ttf,size=48,left=280 "tastic"  -M --bgless

#Add text 3D Shadow effect showing « yet another fbink evolution »
fbink -O -y 20 -S 1 -m -C gray5 -F block EVOLUTION
fbink -O -y 20 -S 1 -m          -F block evolution
                                                                                                            
#save for posting
screenshot

[codex-hex]

hi folks, could you post simple working OT/TT command?ı'm so idiot and cannot run the OT/TT examples on the fbink 1.8 manual page.
By the way sorry for my fcking freaking bad english.

[PoP]

@codex-hex see in the FUNtastic spoiler 2 posts above.

[NiLuJe]

The example is using custom fonts, with a fixed Kobo path. In hindsight, that was probably not a fantastic idea .

EDIT: On Kindle, using this instead should actually do something:

fbink -t regular=/usr/java/lib/fonts/Caecilia_LT_65_Medium.ttf,bold=/usr/java/lib/fonts/Caecilia_LT_75_Bold.ttf,size=24,top=100,bottom=500,left=25,right=50,format "Hello **world**!"

[PoP]

What am I missing?

I am trying

fd=/mnt/us/fonts/
fbink -c -t regular="$fd"unscii-8.otf,size=60 -m -M "        "
#\uEC2B \uEC2D \uEC2E \uEC2F \uEC30 \uEC31 \uEC32 \uEC35 \uEC36

accessing the unscii-8.otf Private Area

fbink prints the 9 characters:

[root@kindle us]# fd=/mnt/us/fonts/
[root@kindle us]# fbink -c -t regular="$fd"unscii-8.otf,size=60 -m -M "? ? ? ? ? ? ? ? ?"
[FBInk] Clock tick frequency appears to be 100 Hz
[FBInk] Screen density set to 300 dpi
[FBInk] Variable fb info: 1072x1448, 8bpp @ rotation: 3 (Counter Clockwise, 270°)
[FBInk] Fontsize set to 32x32 (IBM base glyph size: 8x8)
[FBInk] Line length: 33 cols, Page size: 45 rows
[FBInk] Vertical fit isn't perfect, shifting rows down by 4 pixels
[FBInk] Fixed fb info: ID is "mxc_epdc_fb", length of fb mem: 6782976 bytes & line length: 1088 bytes
[FBInk] Pen colors set to #000000 for the foreground and #FFFFFF for the background
Loading font '/mnt/us/fonts/unscii-8.otf' for the Regular style
[FBInk] Font '/mnt/us/fonts/unscii-8.otf' loaded
Printing string '        ' @ 60pt, honoring the following margins { top: 0px, bottom: 0px, left: 0px, right: 0px } (formatted: false, overlay: false, backgroundless: false, foregroundless: false, inverted: false, flashing: false, centered: true, halign: 0, halfway: true, valign: 0, clear screen: true)
[root@kindle us]#

But only the first 5 aliens show up:

[NiLuJe]

@PoP: That's probably #21 .

Will be fixed in the next release .

(For now, you can add bogus padding characters at the end of your string to get stuff to show up).

[PoP]

^ Yep

fdsys=/usr/java/lib/fonts/
#Qapla'
fbink -c -t regular="$fdsys"code2000.ttf,size=60 -m -M "          "
screenshot

[codex-hex]

Please help me to show on my kobo
İ need simple universal command to show OT/TT fonts.
İ must know What i am missing.
Your funtastic script parts doesnt show anything on my screen and fbink doesnt give me any error message interestingly.

[PoP]

@codex-hex

The example you refer to reads

        fbink -t regular=/mnt/onboard/fonts/NotoSans-Regular.ttf,bold=/mnt/onboard/fonts/NotoSans-Bold.ttf,size=24,top=100,bottom=500,left=25,right=50,format "Hello **world**!"
                Will use NotoSans to print 'Hello world!' at 24pt in a display area starting from 100px down the top of the screen to 500px before the bottom of the screen,
                from 25px of the left edge of the screen until 50px before the right edge.
                Honoring the MarkDown syntax, 'Hello' will be printed with the Regular font style, while 'world' will use the Bold font style.

Meaning that you must have the NotoSans-Regular.ttf and NotoSans-Bold.ttf fonts in your /mnt/onboard/fonts/ directory.

Can you verify this on your device.

Otherwise, if the font files are located in another path, change the command to use that one.

Please post the session log if that still doesn't work.

[NiLuJe]

@codex-hex: what PoP said, plus your exact device and FW version, and the full fbink output (with the -v flag).

The paths on Kobo should be something like...

fbink -t regular=/usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/fonts/Caecilia.ttf,bold=/usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/fonts/Caecilia-Bold.ttf,size=24,top=100,bottom=500,left=25,right=50,format "Hello **world**!"

EDIT: Except, yeah, that segfaults .
EDIT²: Because they're encrypted or obfuscated or something. Yaaaaaay. -_-".

TL;DR: Can't use system fonts on Kobo!

[NiLuJe]

Released v1.8.1!

Mainly bugfixes, among which the UTF-8 issue discussed above .
The OT/TTF renderer now also honors AA when using bgless/fgless/overlay rendering mode (... even on 4bpp devices, which I hate with a renewed fiery passion. I nearly threw the K3 out the window ).

It also fixes a regression in the fixed-cell font rendering, which happened to choose a smaller scaling multiplier than it should have on devices with a non-HD screen...

[sherman]

Originally Posted by NiLuJe

I nearly threw the K3 out the window ).

I'm sure it would have been no great loss if you had

*Runs and hides back in Kobo land*

[PoP]

Originally Posted by NiLuJe

Released v1.8.1!

Mainly bugfixes...

Indeed, no more padding spaces needed:

Remember?


Now revived on my K3!


(Which *will* be a great loss when it dies )