It would be wonderful to have this feature - I found myself constantly switching between a few presets for different books (especially for books of different languages, where different fonts / spacing / margins / etc. are desired).

Some ebook readers I used in the past had this feature (I imagine it's maybe not too difficult to implement?) They also offer some sort of default preset to bootstrap a book when it's imported (in freda's case, I guess it would just be the global settings).

P.S. This is my first post here, big thanks to the devs who have done excellent job on the app (I use the Windows app, I notice that there's Android now as well, which is good to know!).

Getting "System does not support 'windows-1251' encoding" on Android (FB2).

On Windows, the same file opens just fine.

Is there any way to enable support for this encoding?

Freda update 4.36, 3rd September 2020: Change Log

• Render PDF files, displaying the pages as PNG images, using the built-in Windows and Android PDF components.
  
• Better fallback logic for cases where the advanced parser barfs; first try simplified layout, then try flattened – which should basically just emit the text without formatting or aligning it in any way at all
  
• Fix 'float' and 'clear' logic to align better with CSS standards (e.g. force a move below the float(s) in response to an applicable 'clear').  Generally trying to do the best job I can, without (yet) implementing the Block Formatting Context in all its gory horror.
  
• Better handling of block elements embedded inside inline elements.
  
• Better treatment of start-of-paragraph in justified text.
  
• (Android) Ask for permission when it's required for storage card access / save log file / backup (save/restore/merge)
  
• BUG FIX: When the Mobi-parser (or any other thing) creates an epub having elements with HTML that sets width and height attributes, ignore these, unless they are on images.  Such attributes should only be set by CSS not by HTML.
  
• (Windows) BUG FIX: Fix an issue with multi-line text boxes – where keyboard characters like []{}\|’@#~ were getting ignored. 
  
• BUG FIX: Fix odd behaviour (and some stack overflow crashes) with getting/selecting paragraphs, sentences and sections, including when this is done by the 'read aloud' function.
  
• BUG FIX: ‘Read Aloud’ function now starts at the beginning of the selected text (a regression bug meant that it was starting from the start of the paragraph instead)
  
• (Windows) BUG FIX: Fixed an issue where the BookReaderPage menu ribbons would get into in a funny state, where they can’t be popped out (because they immediately close again). 
  

Hi, i've been using the app for a while but yesterday the translation tool stopp working.

Whatever the word input is the translation I get as an output is '???'

I've tried with different languages, different books, words that i had previously translated but nothing seems to get it back to normal.

Even tried reinstalling the app. Any hint on how to solve this?

Hi Jim,

Would it be a difficult thing to make the bottom "Chapter Graph" pinnable in a similar way to the color/theme change buttons?

Thanks

John Whitten

It would be great if Freda can support S Pen on Galaxy Note to change the page ("next page").

I put in a nice plug for FREDA on this YouTube review

Best E-Readers in 2020
https://www.youtube.com/watch?v=FwnLGrzyQNM


JWhitten

When you tap on the 'premium features' button, you will be taken to the Microsoft Store to make a payment.  After that, Freda will enable the premium features.  It can happen that the premium features are not enabled, or that they are enabled, but it then stop working some time in the future.  That can happen particularly after re-installing Freda.  This is the result of something going wrong with the Microsoft Store - it forgets that you've paid for the 'Freda: premium features' item, or else it fails to tell Freda that you have paid for it.

To get the Microsoft Store working right again, you can try the following things:

• Check that you're logged on to your computer using the same Microsoft ID (email address) as you used when you made the payment.
  
• Check that the PC's time and time-zone are set correctly
  
• Run the Microsoft Store troubleshooter (just type 'troubleshoot store' into the type-to-search box in the start menu)
  
• If none of these work, try the suggestions at https://www.makeuseof.com/tag/5-tips-fix...indows-10/
  

Freda update 4.35, 27th July 2020: Change Log

• Reworked the CSS code, to handle long chains of selectors better, and to deal with pseudos more correctly (:nth-child variants and :not, in particular).
  
• Fixed a bug affecting the specificity of the lower border style of tables (and other things)
  
• Text-to-speech no longer applies emphasis (the Android TTS engines ignore the SSML emphasis tag, and the Windows TTS engine pronounces emphasis in a way that no-one could like)
  
• Improved the reliability of loading bookmarks/highlights created by earlier versions of Freda: when loading bookmarks / highlights, if the number of words in the chapter does not match the saved numbers, and if there is a CFI available, use that rather than trying to interpolate a new word position.
  
• The ‘download’ action on a book that has a ‘folder’ source will no longer delete the book (because we won’t be able to get to the file again, because system permissions).  It will now just clear and refresh all the cache files.
  
• The ‘copy to clipboard’ function now includes new-lines for paragraph breaks.
  
• (Android) Fix an issue seen with Gutenberg, around https downloads, caused by the use of an untrusted certificate by Gutenberg.
  
• (Android) Fix problem with Dropbox login (by switching to using the system browser and a custom URI scheme)
  
• (Windows) Accessibility fix: When the selected text range is cleared, keep it hanging around in the background, so that if the user does something ‘resumey’ it will start with that selection, not the first word on the page.  ‘something resumey’ would mean hitting an arrow key for example.
  
• (Windows) Accessibility fix: Images are selectable, and when selected they say their image description alt text (via the speak-selected-text setting, and/or Narrator, and/or read-aloud).
  
• (Windows) Accessibility fix: Image viewer control shows the media description alt text content, if there is any.
  
• (Windows) Accessibility fix: Dialog boxes announce their names when displayed.  The close button, when selected says ‘close popup <dialog name>”.
  
• (Windows) Accessibility fix: Reader page control button says the name of the book, and “reader page controls”.
  
• (Windows) Accessibility fix: Reader page control ribbons buttons and close/minimise/pin/unpin buttons now say something making it clear which ribbon and which function they represent.
  
• (Windows) Accessibility fix: added an item to the ‘accessible’ menu, to do ‘go back to bookshelf’.
  

Hello 

Thank you for letting me join.  I have used Freda for many years and have really likes it until yesterday when Freda was open in the background and suddenly a small pic popped up near the top left of the foreground which I could not remove.  It interfered with everything on screen.  I tried to include an image for your info bur unfortunately do not know how.

I closed Freda in the hope this image would disappear but it did not so I rebooted my PC and the dratted thing came back without me even opening Freda!  I then shut down the PC and left it off for a few mins.  Switched back on and again the image came back.  I then ran cleaning progs and again shut PC and restarted it but again it came back which brought me here in the hope somebody can help.  

Whilst typing this the image has disappeared but I have had this problem in the past but not so bad.

Please help if you can.

Many thanks

tinlizzy

Attached Files

Thumbnail(s)