To avoid a deal of errors with autokey (QT) in LibreOffice 7 (and KDE 5.20) it could be necessary install the KDE Frameworks 5 integration.
Here, at least, it worked.
An epub book has multiple chapters. What method to split it into multiple files, each of them consist one chapter, effectively?
For example as the following:
<hr class="sigil_split_marker" /><h2
3) Then select Edit > Split at markers.
You can use this mysql query code:
ALTER TABLE mytable MODIFY mycol VARCHAR(20) CHARACTER SET utf8;
You can create a your own palette file,
- with .soc extension
- and with a content like the following:
<?xml version="1.0" encoding="UTF-8"?>
<ooo:color-table xmlns:office="urn:oasis:names:tc:opendocument:xmlns:office:1.0" xmlns:draw="urn:oasis:names:tc:opendocument:xmlns:drawing:1.0" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:svg="http://www.w3.org/2000/svg" xmlns:ooo="http://openoffice.org/2004/office">
<draw:color draw:name="panna" draw:color="#faf7d2"/>
<draw:color draw:name="mattone" draw:color="#bc5a1f"/>
<draw:color draw:name="OldLace" draw:color="#FDF5E6"/>
<draw:color draw:name="Cornsilk" draw:color="#FFF8DC"/>
- then you have to put it (also as symlink) in /libreoffice/share/palette.
You will be able to choose that palette (with the same name of the file .soc), and you will be able to use your preferred colors highlighting words in LibreWriter, for example.
The problem of Innodb is that you can’t copy the database tables from a PC to another or from localhost to an online website, because of the file “ibdata1”, which is out of the tables folder.
So I think that the best solution, if you need to sync your database between different locations, is to convert Innodb tables into MyIsam tables, which can be copied without problems.
Unfortunately I didn’t find a way to convert a whole database with a single mysql command, but I had to convert each table, with this code:
ALTER TABLE table_name ENGINE=MyISAM.
But at the end the result was any way good.
This is the code:
SET `field_name` = replace(field_name, 'old_text', 'new_text')
That is avoiding “data truncated” error. You must avoid to replace a value in use.
The right way, if a given value is already applied to some items, is
- to add the new value (supposed similar to the old) to the table structure
- search for all the items with old value
- replace in each item the old value with the new one
- delete the old value in the table structure
It can happen that the ID autoincrement goes wrong; in this case my solution is very simple: I delete the ID column, and afterwards I re-create it (with the same parametres). It works.
You can link within the css (in Calibre it is within the file “viewer-webengine.json”, in markdown-viewer browser extension is the css file you yourself have chosen) your external css file, with something like
Provided you have a apache/php server in localhost, of course.