From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Dolphin and adding a option, if it exists.
Date: Mon, 24 Oct 2022 23:08:32 +0100 [thread overview]
Message-ID: <2654305.mvXUDI8C0e@wstn> (raw)
In-Reply-To: <tj655q$5rj$1@ciao.gmane.io>
On Monday, 24 October 2022 14:49:46 BST Grant Edwards wrote:
> On 2022-10-23, Dale <rdalek1967@gmail.com> wrote:
> > That is true on Linux. Most linux software could care less what the
> > extension is or if it even has one. Heck, you could likely change a
> > .mp4 to .txt and it would open with a video player just by clicking on
> > it. Thing is, if I share a file with someone who uses windoze, I'm not
> > sure if it would work the same way. A wrong extension could cause
> > problems, either not opening at all or crashing something. It's
> > windoze, one can't expect much. ROFL
>
> A friend of mine once spent days trying to re-encode a video file into
> a format that could be handled by a particular windows app. No matter
> what codecs/parameters he tried, the app couldn't open the file. He
> finally figured out that the app in question had hard requirements for
> the filename suffix, and they chose a somewhat non-nstandard extension
> for that container format.
>
> It turned out that any of the codec/parameter combinations would have
> been fine, it was just the filename that was causing the problem.
So the hubris of those two college dropouts still haunts the Windows world.
What a legacy.
--
Regards,
Peter.
next prev parent reply other threads:[~2022-10-24 22:08 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 4:39 [gentoo-user] Dolphin and adding a option, if it exists Dale
2022-10-06 7:33 ` Michael
2022-10-06 7:52 ` Wol
2022-10-06 7:57 ` Michael
2022-10-06 8:10 ` Arve Barsnes
2022-10-06 12:45 ` Neil Bothwick
2022-10-06 15:19 ` Ramon Fischer
2022-10-06 15:22 ` Ramon Fischer
2022-10-06 15:24 ` Neil Bothwick
2022-10-06 17:41 ` Dale
2022-10-08 3:44 ` Dale
2022-10-08 8:05 ` Michael
2022-10-08 8:18 ` Dale
2022-10-08 21:02 ` Neil Bothwick
2022-10-08 22:15 ` Dale
2022-10-08 22:20 ` Mark Knecht
2022-10-08 23:20 ` Dale
2022-10-09 7:44 ` Neil Bothwick
2022-10-08 9:10 ` Wols Lists
2022-10-08 9:24 ` Dale
2022-10-10 0:53 ` [gentoo-user] " Grant Edwards
2022-10-08 20:58 ` [gentoo-user] " Neil Bothwick
2022-10-23 6:35 ` Dale
2022-10-23 9:41 ` Frank Steinmetzger
2022-10-23 11:16 ` Dale
2022-10-23 11:57 ` Frank Steinmetzger
2022-10-24 13:49 ` [gentoo-user] " Grant Edwards
2022-10-24 22:08 ` Peter Humphrey [this message]
2022-11-22 9:59 ` [gentoo-user] " Dale
2022-11-22 10:07 ` Frank Steinmetzger
2022-11-22 12:17 ` Dale
[not found] ` <7773a6e5-4b60-495f-8889-411c1a7def96@PRAP251MB0466.EURP251.PROD.OUTLOOK.COM>
2022-11-22 21:58 ` Undeliverable: " Dale
2022-11-23 0:06 ` Wols Lists
2022-11-23 4:32 ` Dale
2023-01-27 13:54 ` Peter Humphrey
2023-01-29 15:18 ` Peter Humphrey
2022-11-23 11:39 ` Frank Steinmetzger
2022-11-23 11:54 ` Dale
2022-11-23 12:00 ` Frank Steinmetzger
2022-11-23 12:16 ` Dale
2022-11-23 13:05 ` Frank Steinmetzger
2022-11-23 18:17 ` Dale
2022-11-24 14:37 ` Michael
2022-11-22 19:14 ` Wol
2022-10-08 20:32 ` Frank Steinmetzger
2022-10-09 6:58 ` Arve Barsnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2654305.mvXUDI8C0e@wstn \
--to=peter@prh.myzen.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox