From: rowlett@access.net   
      
   On 8/7/25 4:43 PM, Dirk Fieldhouse wrote:   
   > On 05/08/2025 10:14, Schugo wrote:   
   >> On 04.08.2025 14:53, Richard Owlett wrote:   
   >>> ....   
   >>> The content displayed when entering "composer" in the search box   
   >>> displays sparse content.   
   >>> ...   
   >>   
   >> ...  the offline F1 docs of Seamonkey [is/are] one of the best I have   
   > ever seen.   
      
   You'll get no argument from me on that!   
   What annoys me is that it does not have the capability to search for an   
   arbitrary word/phrase. And from comments made by frg it's impractical to   
   add that feature.   
      
   My tentative solution, being discussed in a another sub-thread, is to   
   decompress the SeaMonkey source and extract the Help System's text for   
   placement in a standard HTML framework accessible by any current browser   
   and their builtin fine search capabilities. Thus "I will have my cake   
   and eat it too" ;]!   
      
   >> ...   
   > Also demonstrating that sticking with a proven product design and not   
   > improving/breaking it makes it more likely that docs will not rot away.   
   >   
   > And on 04/08/2025 12:10, Richard Owlett wrote:>...>   
   >> I'm a tri-focal wearing octogenarian with perception[better term???]   
   >> issues. I use SeaMonkey's Edit->Preferences->Appearance->Fonts to force   
   >> a comfortably readable size. That forces a "large hunk" of some lines   
   >> off-screen. If a full sentence is not visible I have comprehension issues.   
   >   
   > As a work-around, maybe Ctrl+- to reduce the content size until it   
   > doesn't get cropped, then use the system's magnifier tool to make the   
   > text readable?   
      
   I've been working on another approach. Creating new HTML documents where   
   all paragraphs consist of arbitrarily long lines with appropriately   
   interspersed 
, 
 and 
 tags. I've done a small feasibility   
   example for fellow seniors at church putting a paragraph formatted   
   KJV[1] in a form acceptable to any browser and using a *user specified*   
   font *AND* screen width.   
      
   [1] _KJV Cambridge Paragraph Bible_ https://ebible.org/engkjvcpb/   
   >   
   > MX Linux comes with Magnus but others are available;   
      
   I'll stick with SeaMonkey and Debian as they both provide tools I don't   
   want to live without ;/   
      
   > also in the   
   > Accessibility tools of the last Windows that I used.   
   >   
   > /df   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)