Quote:
Originally Posted by jgoguen
Well that explains a lot. There's perhaps one problem though, the custom CSS file is specific to each device. You can put it on yours, but if you give the coveted book to someone else you either have to also put the custom CSS on their device (assuming they're also using Kobo readers). It's more work for you, but you may be better off if I understand you correctly to edit each ePub file to either remove the hyphenation or add the custom CSS to disable hyphenation to each content file.
One thing I could perhaps do is to add some code to give a "disable all hyphenation" option to modify the book and add the custom CSS to a book's content files for you. That'll be a few days for me to do and test, I don't have a lot of time each day.
|
The readers we use in the elderly people home are mine.. my wife is a nurse there but it is hard to explain to people why their readers don't work the way they did,with the kepubs they don't even know that they get another format as they had before.
The same with the tv's... they use a simple version of the Logitech Harmony.
If the tv broke, I just re-program the Harmony.. they know how to use it,that it sending a total different code to the new tv they don't understand,as long as they can use the Harmony it is fine, all "dangerous" codes to get into menu where they can change the frequency's are removed.
Sometimes we have to bend our reality to theirs.
I have my normal work,after that I work sometimes 4 hours a day to build new epubs..there are some people that don't understand the tapping on the screen,for them we have a couple of sony 600 and 650 with the < and > phisical buttons so I can't change all to kepub,if that was the case it was simple.. but I am stuck between two formats now.. I think the project is grown to big
