Seafile Client

[trap000d]

Hi There,

I've made a very simple Seafile https://www.seafile.com/en/home/ client.

Currently it lives here:
https://github.com/trap000d/seafile-kindle-client

Known Issues/Bugs
- Only one way synchronization
- Client doesn't erase sub-directory (and it's contents) if it's not exist on the server
- Non-latin characters are not shown through eips
- Just rudimentary checks of internet/WiFi availability/file operations
- SSL certificate verification ignored (verify=False) just to make it work with self-signed SSL certs

So I've got some questions to developers:
1. Is it possible to put text to Kindle screen from bash/python script other then with eips (to use Unicode characters)?
2. Any suggestions in regarding to self-signed SSL certs, or just left it as is (verify=False)?

[knc1]

1) Yes.
What makes you think eips does not do Unicode (UTF-8 flavor)?
Tell us how you tested that, perhaps we can duplicate your problem.

2) For what purpose is the certificate to be used?
Your certificate or the servers?
Context please.

[trap000d]

1. Here the simplest test script (just some Cyrillic letters):
====
#! /bin/bash

ustring="Йцукенг"
eips 1 58 "$ustring"
====
When I run it either from terminal or KUAL menu, I got

eips: paint_char> character "�" not available

and no output at Kindle screen. The same reaction happens when string contains particular ASCII symbols, e.g. ' (apostrophe)

2. I'm keeping my own web server and using self-signed SSL certificate (too lazy to get one at Let's Encrypt). There are several options to handle it:
a) import certificate to OS (mntroot rw && cp ca.crt /etc/ssl/ && mntroot ro && update_ca [or something similar])
b) ignore it (possible MiTM attack)
c) put it into more convenient place, e.g. to the same directory as script, and then verify with 'verify=/path/to/cert/file.crt' option

[knc1]

1) Is that language on your Kindles list of languages it can be set to?
What is the Kindle's current language setting?
Do you have any localization and/or font add-ins in use?
What model Kindle?
What version firmware?

Please, all relevant context, do not turn this into a question and answer guessing game.

2) Do not be lazy or just use it at the "warm and fuzzy (plus bragging rights)" setting.

[trap000d]

1)

OK. No problem:

Russian language is available as system language

Current settings
Language - English (United States)

Language related environment variables:
LANG=en_US.UTF-8
LC_ALL=en_US.UTF-8

No any custom/non-standard localization packages/fonts/e.t.c. installed

Model: Kindle PW3

Firmware version 5.8.2.1

After some additional tests: eips also doesn't show the following ASCII symbols: ' ! $ % ^ { } ; ` \

So I suppose it's not a Unicode problem. It looks like eips takes an image of particular symbol in it's own font file and this font file contains only a partial subset of ASCII table (letters, numbers and some punctuation symbols). All other symbols seems not available.

P.S. I'll test it on two other devices I've got (PW1 and PW2 resp.) then let you know of results.


2) Added option in configuration file

Originally Posted by knc1

1) Is that language on your Kindles list of languages it can be set to?
What is the Kindle's current language setting?
Do you have any localization and/or font add-ins in use?
What model Kindle?
What version firmware?

Please, all relevant context, do not turn this into a question and answer guessing game.

2) Do not be lazy or just use it at the "warm and fuzzy (plus bragging rights)" setting.

[knc1]

After some additional tests: eips also doesn't show the following ASCII symbols: ' ! $ % ^ { } ; ` \

Surprise, surprise - those are all reserved characters in the shell and I think eips is a shell script.
Check that and check how you are escaping the characters.

Try setting it to Russian and then try Russian characters.
It should work - I do not know what escaping that needs to be used, if any.

[trap000d]

Your assumption seems wrong:

Indeed, some of these symbols forming a subset of shell escape symbols, but there are some exceptions: [ ] ( ) " : < > ? are shown by eips without any error

file eips
eips: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.3, for GNU/Linux 2.6.16, stripped

and I know how to cook shell escape characters properly.

Originally Posted by knc1

Surprise, surprise - those are all reserved characters in the shell and I think eips is a shell script.
Check that and check how you are escaping the characters.

Try setting it to Russian and then try Russian characters.
It should work - I do not know what escaping that needs to be used, if any.

[knc1]

Originally Posted by trap000d

Your assumption seems wrong:

Indeed, some of these symbols forming a subset of shell escape symbols, but there are some exceptions: [ ] ( ) " : < > ? are shown by eips without any error

file eips
eips: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.3, for GNU/Linux 2.6.16, stripped

and I know how to cook shell escape characters properly.

Now that you have provided that additional information,
please try setting the machine's interface language to Russian and try some Russian character strings.
Report your result, including test environment (Kindle model as first six characters of the serial number and firmware version running).

[baf]

Looking into eips disassembly it seems that the only valid characters are
[a-z], [A-Z], [0-9], various space chars and one of ,":._-*~/,()@&+?<>=|[].

[knc1]

Originally Posted by baf

Looking into eips disassembly it seems that the only valid characters are
[a-z], [A-Z], [0-9], various space chars and one of ,":._-*~/,()@&+?<>=|[].

Thanks.
Looks like Lab126 missed that one when they went to UTF-8 on the Kindles.

Is there any signs that it calls out to a lower level routine to post the character(s)?
Perhaps the lower level routine can be accessed as an answer to this question.

[baf]

Originally Posted by knc1

Is there any signs that it calls out to a lower level routine to post the character(s)?
Perhaps the lower level routine can be accessed as an answer to this question.

It maps ascii characters to pixel representation and sends it to framebuffer device. To send unicode characters you will have to convert it first to image, then you can use eips as well. If you want to use low level framebuffer stuff there are people that have already done it here (geekmaster?).

[knc1]

Originally Posted by baf

It maps ascii characters to pixel representation and sends it to framebuffer device. To send unicode characters you will have to convert it first to image, then you can use eips as well. If you want to use low level framebuffer stuff there are people that have already done it here (geekmaster?).

Thanks.
Since the Kindles are language localized in, what, fifteen languages - there must be another way to write to the screen other than this one.

Probably have to go through the display manager (awesome).
Since we only use eips for short messages, such as status messages, this language shortcoming hasn't been noticed before (that I can recall).

[trap000d]

Yeah, I've found that magic string too:

DCB " ",0x22,":._-*~/,()@&+?<>=|[]",0
ALIGN 0x10
DCB "paint_char",0
ALIGN 0x10
DCB "main",0
ALIGN 4
DCB "eips: %s> bpp = %d not supported",0xA,0

Indeed, it can draw only a basic sub-set of ASCII (letters, numbers and some symbols). So I'll just put a simple spinner instead of typing file names.

Originally Posted by baf

Looking into eips disassembly it seems that the only valid characters are
[a-z], [A-Z], [0-9], various space chars and one of ,":._-*~/,()@&+?<>=|[].

[trap000d]

Thanks for a good piece of advice. I'll play a bit with awesome-client.

P.S. However such kind of mix (Python + Lua + bash ) looks a bit heavy for my little project.

Originally Posted by knc1

Thanks.
Since the Kindles are language localized in, what, fifteen languages - there must be another way to write to the screen other than this one.

Probably have to go through the display manager (awesome).
Since we only use eips for short messages, such as status messages, this language shortcoming hasn't been noticed before (that I can recall).

[knc1]

Neither Python nor Bash come pre-installed in the Amazon file system (the shell is Busybox Ash).
But Lua does (in all 5.x series devices).

You have never said WHAT you want to put on the screen, only what didn't work for you.
Without any clue to just what you are trying to achive . . . .

Write to tekUI - it has already been modified to play nicely with the Lab126 X11 installed.
The project page:
http://tekui.neoscientists.org/

The modified version (with examples):
https://github.com/janetizzy/KUAL-buttons

tekui does not have its own thread, the contribution starts here:
https://www.mobileread.com/forums/sho...9&postcount=15

And I have already set-up a 'standard practice' for extending the built-in Lua with <whatever> placed in visible USB storage.
A working example - look up (here) my CPU Report button thread.