Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > alt.usage.english > #1060135

Re: RAW vs. raw image format

From Anton Shepelev <anton.txt@gmail.com>
Newsgroups alt.usage.english
Subject Re: RAW vs. raw image format
Date 2023-02-20 00:39 +0300
Organization A noiseless patient Spider
Message-ID <20230220003936.ca90df6f8848a095271a0cbe@gmail.com> (permalink)
References (10 earlier) <700fe9f1-688d-43db-970d-ba913b973549n@googlegroups.com> <20230219163456.9a02598f92e282b633f4b59e@gmail.com> <f5a15ad4-4faf-440a-a59f-c5890d395961n@googlegroups.com> <20230219220058.8d3d14741e18cce1bf19e256@gmail.com> <51151e80-a719-46ef-8095-6535309e7d02n@googlegroups.com>

Show all headers | View raw


Peter T. Daniels to Anton Shepelev:

> > Had you access to the
>
> (Did you have access to)
>
> > InDesign support and user community for consultation?
>

c.f. "Have you a match?" from Sherlock Holmes.

> > > You hate Microsoft. Whoop-de-doo.
> >
> > Is that supposed to be the ultimate argument of a
> > Microsoft advocate?
>
> No, it's the ultimate argument of the Microsoft-hater --
> as you made clear in the preceding paragraph.

*You* wrote `Whoop-de-doo'.  I did not write it.

> > > Nonetheless, in 1994 FrameMaker could output .rtf
> > > files.
> >
> > So what?
>
> You claimed it was proprietary, or something.

And rightly so, for it /is/ proprietary.

> > > > I think it wrong to capitalise file extensions if
> > > > they occur at start of sentence.
> > >
> > > I think it is wrong to all-caps them in the middle of
> > > a sentence.
> >
> > I agree.
>
> See what you did above!

Whatever I did above, it was not to "all-cap" a file
extension.  Where I wrote:

> RTF is an early proprietary Microsoft document format

RTF is not an a file extension, but the initialism for Rich
Text Format.  The extension is .rtf .

-- 
()  ascii ribbon campaign -- against html e-mail
/\  www.asciiribbon.org   -- against proprietary attachments

Back to alt.usage.english | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Re: RAW vs. raw image format Anton Shepelev <anton.txt@gmail.com> - 2023-02-19 16:34 +0300
  Re: RAW vs. raw image format "Peter T. Daniels" <grammatim@verizon.net> - 2023-02-19 07:19 -0800
    Re: RAW vs. raw image format Anton Shepelev <anton.txt@gmail.com> - 2023-02-19 22:00 +0300
      Re: RAW vs. raw image format "Peter T. Daniels" <grammatim@verizon.net> - 2023-02-19 13:21 -0800
        Re: RAW vs. raw image format Anton Shepelev <anton.txt@gmail.com> - 2023-02-20 00:39 +0300
          Re: RAW vs. raw image format Madhu <enometh@meer.net> - 2023-02-20 12:11 +0530
            Re: RAW vs. raw image format lar3ryca <larry@invalid.ca> - 2023-02-21 15:54 -0600
              Re: RAW vs. raw image format Madhu <enometh@meer.net> - 2023-02-22 06:48 +0530
                Re: RAW vs. raw image format Snidely <snidely.too@gmail.com> - 2023-02-21 18:35 -0800
                Re: RAW vs. raw image format Anton Shepelev <anton.txt@gmail.moc> - 2023-02-23 19:34 +0300
                Re: RAW vs. raw image format "Peter T. Daniels" <grammatim@verizon.net> - 2023-02-23 08:39 -0800
                Re: RAW vs. raw image format Anton Shepelev <anton.txt@gmail.moc> - 2023-02-24 00:18 +0300
                Re: RAW vs. raw image format "Peter T. Daniels" <grammatim@verizon.net> - 2023-02-23 14:41 -0800
                Re: RAW vs. raw image format Snidely <snidely.too@gmail.com> - 2023-02-23 15:25 -0800
                Re: RAW vs. raw image format Jerry Friedman <jerry.friedman99@gmail.com> - 2023-02-23 15:48 -0800
                Re: RAW vs. raw image format Snidely <snidely.too@gmail.com> - 2023-02-23 14:38 -0800
                Re: RAW vs. raw image format "Peter T. Daniels" <grammatim@verizon.net> - 2023-02-23 14:46 -0800
                Re: RAW vs. raw image format Snidely <snidely.too@gmail.com> - 2023-02-23 14:45 -0800
                Re: RAW vs. raw image format lar3ryca <larry@invalid.ca> - 2023-02-21 22:12 -0600
              Re: RAW vs. raw image format Tak To <takto@alum.mit.eduxx> - 2023-02-22 11:30 -0500
                Re: RAW vs. raw image format lar3ryca <larry@invalid.ca> - 2023-02-22 11:15 -0600
                Re: RAW vs. raw image format Snidely <snidely.too@gmail.com> - 2023-02-22 09:36 -0800
                Re: RAW vs. raw image format Anton Shepelev <anton.txt@gmail.moc> - 2023-02-23 19:21 +0300
                Re: RAW vs. raw image format Anton Shepelev <anton.txt@gmail.moc> - 2023-02-23 00:31 +0300
                Re: RAW vs. raw image format Tak To <takto@alum.mit.eduxx> - 2023-02-23 15:40 -0500
                Re: RAW vs. raw image format lar3ryca <larry@invalid.ca> - 2023-02-23 15:03 -0600
                Re: RAW vs. raw image format Snidely <snidely.too@gmail.com> - 2023-02-23 14:50 -0800
                Re: RAW vs. raw image format lar3ryca <larry@invalid.ca> - 2023-02-23 22:42 -0600
                Re: RAW vs. raw image format Anton Shepelev <anton.txt@gmail.moc> - 2023-02-23 19:31 +0300
                Re: RAW vs. raw image format Rich Ulrich <rich.ulrich@comcast.net> - 2023-02-23 18:53 -0500
              Re: RAW vs. raw image format Anton Shepelev <anton.txt@gmail.moc> - 2023-02-23 00:23 +0300
            Re: RAW vs. raw image format Anton Shepelev <anton.txt@gmail.moc> - 2023-02-23 00:21 +0300
      Re: RAW vs. raw image format TonyCooper <tonycooper214@gmail.com> - 2023-02-19 16:30 -0500

csiph-web