| 
			
			 | 
		#481 | 
| 
			
			
			
			 Connoisseur 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 68 
				Karma: 358058 
				Join Date: Aug 2019 
				Location: Serbia, former Yugoslavia 
				
				
				Device: Pocketbook InkPad 3 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			@pazos 
		
	
		
		
		
		
		
		
		
		
		
		
	
	Sir, thank you very much for your very competent observations and answers! And thanks for your work on KO!  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#482 | 
| 
			
			
			
			 Old Kaz 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 208 
				Karma: 1064151 
				Join Date: May 2010 
				
				
				
				Device: PocketBook Era 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			Help please. 
		
	
		
		
		
		
		
		
		
		
		
		
	
	On KOReader 2022.10 and PocketBook Touch HD 3 (632) button "Menu" does not work. Browsing buttons (KEY_PREV, KEY_NEXT) and "Home" (KEY_HOME) works, but on KEY_MENU there is no reaction. How it can be corrected?  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| Advert | |
| 
         | 
    
| 
			
			 | 
		#483 | 
| 
			
			
			
			 BLAM! 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506 
				Karma: 26047202 
				Join Date: Jun 2010 
				Location: Paris, France 
				
				
				Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			@kaznelson: Create an issue on github, *with* verbose debug logs, and on a current nightly. 
		
	
		
		
		
		
		
		
		
		
		
		
	
	And, also, what you were expecting the Menu key to do and where. And whether that worked in previous versions, and if so, when and how.  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#484 | |
| 
			
			
			
			 Old Kaz 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 208 
				Karma: 1064151 
				Join Date: May 2010 
				
				
				
				Device: PocketBook Era 
				
				
				 | 
	
	
	
		
		
		
		
		 Quote: 
	
 https://github.com/koreader/koreader/issues/9791 - KEY_HOME In a PocketBook the touch screen is traditionally a weak node (bad reaction) - I want to put more functions on the hardware buttons. [C.KEY_MENU] = "Press" - open the bottom (reading) menu; however [C.KEY_MENU] = "Menu" - does NOT open the top (settings) menu... I don't know, haven't tried it before... Last edited by kaznelson; 11-15-2022 at 05:59 AM.  | 
|
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#485 | 
| 
			
			
			
			 Old Kaz 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 208 
				Karma: 1064151 
				Join Date: May 2010 
				
				
				
				Device: PocketBook Era 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			NiLuJe 
		
	
		
		
		
		
		
		
		
		
		
		
	
	Please tell me, is it possible to change the font in the Alt Status Bar? I want to install Roboto Condensed...  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| Advert | |
| 
         | 
    
| 
			
			 | 
		#486 | 
| 
			
			
			
			 BLAM! 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506 
				Karma: 26047202 
				Join Date: Jun 2010 
				Location: Paris, France 
				
				
				Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			I have never ever used the header bar, as I despise it with a fiery passion  
		
	
		
		
		
		
		
		
		
		
		
		
	
	 .
		 | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#487 | 
| 
			
			
			
			 Old Kaz 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 208 
				Karma: 1064151 
				Join Date: May 2010 
				
				
				
				Device: PocketBook Era 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			NiLuJe 
		
	
		
		
		
		
		
		
		
		
		
		
	
	I would also despise, but the KOReader status bar cannot be moved up. ![]() Or?..  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#488 | 
| 
			
			
			
			 BLAM! 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506 
				Karma: 26047202 
				Join Date: Jun 2010 
				Location: Paris, France 
				
				
				Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			Nope, it's very much called ReaderFooter for a reason  
		
	
		
		
		
		
		
		
		
		
		
		
	
	 .
		 | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#489 | 
| 
			
			
			
			 Wizard 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,557 
				Karma: 5000046 
				Join Date: Feb 2012 
				Location: Cape Canaveral 
				
				
				Device: Kindle Scribe 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			In koreader/data/cr3.ini there is “crengine.page.header.font.face=Noto Sans”, but changing it does nothing.
		 
		
	
		
		
		
		
		
		
		
		
		
		
	
	 | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#490 | |
| 
			
			
			
			 Old Kaz 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 208 
				Karma: 1064151 
				Join Date: May 2010 
				
				
				
				Device: PocketBook Era 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			And it doesn't work either: 
		
	
		
		
		
		
		
		
		
		
		
		
	
	/applications/koreader/frontend/document/credocument.lua Quote: 
	
  | 
|
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#491 | 
| 
			
			
			
			 Old Kaz 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 208 
				Karma: 1064151 
				Join Date: May 2010 
				
				
				
				Device: PocketBook Era 
				
				
				 | 
	
	|
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#492 | 
| 
			
			
			
			 Wizard 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,190 
				Karma: 3592925 
				Join Date: Sep 2014 
				Location: Ukraine 
				
				
				Device: Kindle 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			Maybe because right alignment is useful for Arabic or Hebrew texts only? 
		
	
		
		
		
		
		
		
		
		
		
		
	
	"About text direction" help is self-explanatory.  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#493 | 
| 
			
			
			
			 Wizard 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,786 
				Karma: 731691 
				Join Date: Oct 2014 
				Location: Antwerp 
				
				
				Device: Kobo Aura H2O 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			Arguably it might make sense to show the same thing twice, but yeah.
		 
		
	
		
		
		
		
		
		
		
		
		
		
	
	 | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#494 | 
| 
			
			
			
			 Old Kaz 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 208 
				Karma: 1064151 
				Join Date: May 2010 
				
				
				
				Device: PocketBook Era 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			It's illogical - currently not all the settings related to the direction are in one place. And then why additionally separate the same type of settings? For justify align even when choosing RTL, you will have to go to another submenu...
		 
		
	
		
		
		
		
		
		
		
		
		
		
	
	 | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#495 | 
| 
			
			
			
			 Groupie 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 199 
				Karma: 195502 
				Join Date: Jan 2018 
				
				
				
				Device: Cybook Orizon, PocketBook Touch HD 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			Logically, they are two different things. LTR or RTL is not about margin alignment, but about text flow, including all the unicode bidi rules, when all three types of characters are present (L, R and direction-neutral). I rather see it as a labeling issue. [2] should be "Force left text flow for most text/for all elements", and accordingly down in the translations.
		 
		
	
		
		
		
		
		
		
		
		
		
		
		
			Last edited by EastEriq; 11-26-2022 at 12:33 PM.  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
![]()  | 
            
        
            
| Tags | 
| calibre, epub, koreader, pb742, pdf, pocketbook | 
            
  | 
    
			 
			Similar Threads
		 | 
	||||
| Thread | Thread Starter | Forum | Replies | Last Post | 
| KOReader: a document reader for PDF, DJVU, EPUB, FB2, HTML, ... (GPLv3) | hawhill | Kindle Developer's Corner | 1289 | 04-07-2025 11:18 AM | 
| CBZ plugin interaction with FB2/DjVu plugins - First try at pinpointing | MrWarper | iRex | 2 | 12-11-2011 06:46 AM | 
| Raccoon Reader - reads ePub, fb2, fb2.zip, txt on WP7 for free | Andrei_Shvydryk | Reading and Management | 0 | 10-31-2011 04:17 PM | 
| v3 vs. v3+ as a pdf/DjVu reader | hedonism_bot | HanLin eBook | 7 | 11-02-2010 09:16 PM | 
| New PDF to LRF Tool (for DJVU and CBZ files too) | RWood | Sony Reader | 0 | 08-29-2007 03:13 PM |