Skip to main content

GIMP 2.10.6 Released with Vertical Text Support + More
#grafik #gimp #software #alternative



#oop #bash #stdlib

Translation for the 2018.08 release
It is August already and among many other things this also means that ~friendica ~friendica is going to have the next release soon
... mostra di più

Nuitka is a Python compiler I never heard of. It just achieved 3.7 compatibility. Cool!

> Right now Nuitka is a good replacement for the Python interpreter and compiles every construct that all relevant CPython version, and even irrelevant ones, like 2.6 and 3.2 offer. It translates the Python into a C program that then is linked against libpython to execute in the same way as CPython does, in a very compatible way.

> It is somewhat faster than CPython already, but currently it doesn't make all the optimizations possible, but a 258% factor on pystone is a good start (number is from version 0.3.11).

#python #programming #compiler #softwareengineering

The explosion was the most impressive thing. A disaster.


YouTube: AT&T Archives: The UNIX Operating System (AT&T Tech Channel)






updated #friendica to last dev.. let's see..

? It seem I have some problem with unicode in old messages body (emoticons and like), but not in new ones like this.

You have to set the DB encoding explicitely in the config file to match the one from your DB.

can I set it in .htconfig or I need to switch to ini config?
and if I can set it in .htconfig, how?
(sorry, I didn't followed last development...)

Yes you can set it in htconfig. Something like

$a->config["system"]["db_charset"] = 'utf8mb4';

Here is the thread in the forum about it.

Fixed, thank you 👍😎

@Tobias how do you set it if the tables have different encoding? I never touched that manually but saw some table are different.

Probably there is different encodings used for some reason?

Here was the post were I mentioned the encoding differences between tables:

I don't think so. Some time ago we switched the default encoding from utf8 to utf8mb4 and the collation from utf8_general_ci to utf8mb4_general_ci. So, new tables and fields probably are utf8mb4 encoded and old stuff is still utf8. That's not a problem as long as you don't change the encoding setting of your database server.

You could try setting $a->config['system']['db_charset'] = "latin1";. MySQL had "latin1" as default for a long time.






Sbrinato il congelatore. Un lavoro che da soddisfazioni, e permette di giocare col ghiaccio in pieno luglio. Che non è male..