@tshering
Well, good news is that library view has now nice big font and it all came after the 1st test (see below).
"Bad" news is that it came with 1MB conf_ file which seems like a lot of tries to pin-point the responsible part (I realize that bisection search will allow to make it in about 11 iterations, but still ;-)
I personally did not see any negative effect on overall font increase - quite the opposite - you can be sure that in whatever part of Kobo you might need to look at it will all look "eye-comfortable".
Results of Test 1:
Aside from the lower Menu font (which as expected did not have any change) everything else is as it should have been made from start. Even the Top Menu, Reboot, PC connection, etc screens were welcoming with easy to read font-sizes.
[Image violates guidelines for size - MODERATOR]
Results of Test 2:
Looks like zlib in not being used here - I did not see any changes from the original state wherever I looked...
Results of Test 3:
Menu is back with big font, and the search field shows big nice font.
[Image violates guidelines for size - MODERATOR]
Now the question is: is it worth the effort to locate the exact strings responsible for each particular change of would it make more sense to keep this total change approach and enjoy the overall effect (without any noticeable side effect, unless of course there is an allergy to big font-sizes).
Perhaps a cool thing would be to have a script increasing font-sizes to other than 50% values in conf_ files, but I don't know how easy it is for you to make it available.