From: nunojsilva@invalid.invalid   
      
   On 2025-08-08, Richard Owlett wrote:   
      
   > On 8/5/25 9:12 AM, frg wrote:   
   >> Richard Owlett wrote:   
   >>> On 8/5/25 4:14 AM, Schugo wrote:   
   >>>> On 04.08.2025 14:53, Richard Owlett wrote:   
   >>>>> ....   
   >>>>> The content displayed when entering "composer" in the search box   
   >>>>> displays sparse content.   
   >>>>> ...   
   >>>>   
   >>>> No! It doesn't.   
   >>>   
   >>> Relax already. All I meant was I couldn't see details I wanted.   
   >>> I haven't yet downloaded the source tarballs due to the   
   >>> accessibility issues with   
   >>> https://archive.seamonkey-project.org/releases/2.53.21/README.txt I   
   >>> mentioned in my reply to frg.   
   >>>   
   >>>>   
   >>>> I hardly ever read documentation for simple software like browsers.   
   >>>> Now I checked the offline F1 docs of Seamonkey and I can tell you   
   >>>> it's one of the best I have ever seen.   
   >>>> Do you know how long it takes to write so many pages of docs?   
   >>>> Thousands of hours.   
   >>>   
   >>> It wasn't computer related, but I spent close to three decades in   
   >>> enginering support and/or helping end users. I *DO* understand ;]   
   >>>   
   >>>>   
   >>>> Now in 2025 with most software you are redirected to a   
   >>>> machine generated webpage with machine translations   
   >>>> and half the stuff doesn't make any sense.   
   >>>>   
   >>>> Be thankful to real developers and doc writers!   
   >>>>   
   >>>>   
   >>>> ciao..   
   >>>>   
   >>>   
   >>   
   >> The links for the latest tarballs are:   
   >> https://archive.seamonkey-project.org/releases/2.53.21/source   
   seamonkey-2.53.21.source.tar.xz   
   >>   
   >> https://archive.seamonkey-project.org/releases/2.53.21/source   
   seamonkey-2.53.21.source-l10n.tar.xz   
   >>   
   >   
   > Attempting to download sent me smashing into my relatively low data   
   > cap. I won't have full speed service again until next billing cycle in   
   > a few days. Meanwhile I was able to download them using local   
   > library's public WIFI.   
   >   
   > In another post you said the files I needed were in   
   >  /comm/suite/locales/en-US/chrome/common/help  *IF* I copied correctly   
   >   
   > I've never used tar to extract anything large.   
   > I can't figure out syntax to extract only contents of a specific directory.   
   >   
   > May I have the proper command?   
      
   The extract command takes an optional parameter. So in the dash-style   
   syntax I guess it could be   
      
       tar -f seamonkey-2.53.21.source.tar.xz -x seamonkey-2.53.21/   
   omm/suite/locales/en-US/chrome/common/help -kv   
      
   (The two final ones aren't necessary for this, but you may want to use them   
   anyway: avoid overwriting (-k) and (in this case) write out the name of   
   every file/directory extracted from the archive (-v).)   
      
   (This should not be a problem if you're on a Linux system, as these   
   usually have tar from GNU, but: for tars other than BSD or GNU, please   
   check that the dashed syntax is accepted and that the "k" command is   
   supported, as these are not in the version of POSIX I've checked.)   
      
   --   
   Nuno Silva   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)