View Single Post
Old 05-29-2018, 10:57 AM   #27
geek1011
Wizard
geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.
 
Posts: 2,736
Karma: 6990705
Join Date: May 2016
Location: Ontario, Canada
Device: Kobo Mini, Aura Edition 2 v1, Clara HD
Quote:
Originally Posted by Terisa de morgan View Post
I've done a script and I've converted all the patches for 4.8.11703 to the new format. I haven't applied yet to the reader but I've got some comments:
  • The demo example is wrong in Offset/Find/Replace indentation, it must be another level... or the token is not recognized
  • For keyboard patch there is some offset like this: FFFFFFD4, that is not accepted because it's said that it doesn't fit in Int32 (I'm using ReplaceString)
  • When you are using strings for Find and Replace, you have to escape " or ' (as you prefer the delimiter) or there are errors in the patching

Additionally, aside of supporting of having more than a set of overrides in the same patch file (Aura One and Aura Ed 2 have some differences), I would like to add the idea of Group of patches which should be applied together (there are a couple of examples).

I've uploaded the translation file too (I process it with lrelease.exe, so it generates the qm file).
Thanks! I'll update the demo later.


For the translations, would a section like this be good:
Code:
translations:
     src/whatever.ts: usr/local/Kobo/translations/whatever.qm
It would only work if lrelease can be found in the PATH, else, it would give an error.


Quote:
Originally Posted by oren64 View Post
I and I think others don't use the patches as is, the idea is to change the patch, to have the ability to replace the lines the patch, so if someone want to replace line in the patch, he will have add add the code to the conf file, If the patch change he will have to change the code, if not he will get an error.
OK. I see what you mean. What would be a consistent way to identify a line to replace, and be compatible with both patch formats?
geek1011 is offline   Reply With Quote