Touch Page numbers are not shown

[zztush]

I used to be able to see the page numbers in the margins. After I updated my firmware to 3.5.0, I see only boxes with X instead of the page numbers. Same thing happens on firmware 3.8.0 too.

I have clicked on the box of "show page numbers on the margins" in reading settings same as before.

Does anyone know any clue of this problem? Thank you very much in advance.

[DNSB]

Originally Posted by zztush

I used to be able to see the page numbers in the margins. After I updated my firmware to 3.5.0, I see only boxes with X instead of the page numbers. Same thing happens on firmware 3.8.0 too.

I have clicked on the box of "show page numbers on the margins" in reading settings same as before.

Does anyone know any clue of this problem? Thank you very much in advance.

Truly odd since the box with an x is used by some fonts as a placeholder for a glyph that does not exist in the font.

I'd be tempted to suggest a factory reset and update to 3.8.0 to see if this affects your problem.

Can you do a screenshot of the problem? Add the following lines to the Kobo eReader.conf file in the Kobo directory below the .kobo directory. Use a Unix end of line aware editor such as Notepad++ if doing this from a Windows computer. If the [FeatureSettings] line exists, just add the Screenshots line below it. One caution is that since you use the power switch to take a screenshot which is stored in the root of the internal storage as a .png file, it's best to enable the feature, take your screenshots and then edit the file to set Screenshots=false.

[FeatureSettings]
Screenshots=true

I've attached a sample image showing a page number and the font information.

[zztush]

Thank you for telling me how to take screenshots DNSB. I have taken the screenshots and they told me when this happened.

The page numbers only disappear on Japanese text with or without Japanese fonts (frist and second images). It doesn't happens on English text even with Japanese fonts (third image).

This result may give us a clue to solve this problem. Thanks again DNSB.