Hi,
I'm pulling my hair because I don't manage to find a certain term to use in an
abstract.
We've talked about the issue over and over again, but how do we call it when
using proprietary software prevents us from changing the tools to work with our
data/documents? (Well, actually the same ef
locked-in?
-- Original Message --
From: "Urs Liska"
To: "lilypond-user"
Sent: 18/08/2018 10:53:32
Subject: Proprietary Software term
Hi,
I'm pulling my hair because I don't manage to find a certain term to
use in an abstract.
We've talked about the issue over and over again, but
Am 18. August 2018 12:25:25 MESZ schrieb Trevor :
>
>locked-in?
Strike!
"Vendor lock in" was it what I was looking for.
Thanks
Urs
>
>-- Original Message --
>From: "Urs Liska"
>To: "lilypond-user"
>Sent: 18/08/2018 10:53:32
>Subject: Proprietary Software term
>
>>Hi,
>>
>>I'm pullin
Incompatibility for the second term, vendor lock-in for the first.
https://en.wikipedia.org/wiki/Vendor_lock-in
Andrew
On Sat, 18 Aug 2018 at 20:17, Urs Liska wrote:
> Hi,
>
> I'm pulling my hair because I don't manage to find a certain term to use
> in an abstract.
>
> We've talked about the
Urs Liska writes:
> Hi,
>
> I'm pulling my hair because I don't manage to find a certain term to
> use in an abstract.
>
> We've talked about the issue over and over again, but how do we call
> it when using proprietary software prevents us from changing the tools
> to work with our data/documen
0
Am 18. August 2018 13:08:19 MESZ schrieb David Kastrup :
>Urs Liska writes:
>
>> Hi,
>>
>> I'm pulling my hair because I don't manage to find a certain term to
>> use in an abstract.
>>
>> We've talked about the issue over and over again, but how do we call
>> it when using proprietary softwar
Urs Liska writes:
> Am 18. August 2018 13:08:19 MESZ schrieb DK:
>>Urs Liska writes:
>>
>>> We've talked about the issue over and over again, but how do we
>>> call it when using proprietary software prevents us from changing
>>> the tools to work with our data/documents? (Well, actually the sam
Hi all
I want the bar numbers to remain close to the staff but things aren’t working
for me if I beam across the carline with overridden beam positions.
Any clues?
Thanks as always
Damian
{
\version "2.19.82"
\set Score.timing = ##f
\autoBeamOff
\voiceOne
\override BarNumber.outside-
On 8/18/2018 11:55 AM, damianlegassick wrote:
Hi all
I want the bar numbers to remain close to the staff but things aren’t working
for me if I beam across the carline with overridden beam positions.
Any clues?
Thanks as always
Damian
{
\version "2.19.82"
\set Score.timing = ##f
\autoB
Hi
I want bar 15 the same hight as bar 14
Damian
> On 18 Aug 2018, at 17:20, Ben wrote:
>
> On 8/18/2018 11:55 AM, damianlegassick wrote:
>> Hi all
>>
>> I want the bar numbers to remain close to the staff but things aren’t
>> working for me if I beam across the carline with overridden beam
Il giorno mar 7 ago 2018 alle 1:19, Simon Albrecht
<"simon.albrecht"@mail.de> ha scritto:
On 06.08.2018 17:34, ma...@masonhock.com wrote:
Is libportmidi0 installed?
Great catch, that was the culprit!
Should that be added to the wiki page? Federico?
Added to the wiki.
Thanks
On 2018-08-18 09:25, damianlegassick wrote:
I want bar 15 the same hight as bar 14
{
\version "2.19.82"
\set Score.timing = ##f
\autoBeamOff
\voiceOne
\override BarNumber.outside-staff-priority = #0
\override Stem.outside-staff-priority = #1
\override Beam.outside-staff-priority =
On 18/08/18 12:51, David Kastrup wrote:
>> Indeed, that wasn't expressed too well. What I meant is that
>> > CodaMusic's policy to use binary non-released (for some time even
>> > encrypted) file formats strongly discouraged anyone to make a program
>> > use these files.
> That's more than just lo
On Sat 18 Aug 2018 at 19:55:01 (+0100), Wols Lists wrote:
> On 18/08/18 12:51, David Kastrup wrote:
> >> Indeed, that wasn't expressed too well. What I meant is that
> >> > CodaMusic's policy to use binary non-released (for some time even
> >> > encrypted) file formats strongly discouraged anyone t
Hallo all,
I have a (rooted) Android tablet, on which I run Linux Debian by means of
an app called Linux Deploy. The debian repositories for the ARMv7 (or
armhf) chipset only contain Lilypond 2.18.2. That served me well for quite
some time. However, the Edition Engraver requires at least Lilyp
David Wright writes:
> On Sat 18 Aug 2018 at 19:55:01 (+0100), Wols Lists wrote:
>> On 18/08/18 12:51, David Kastrup wrote:
>> >> Indeed, that wasn't expressed too well. What I meant is that
>> >> > CodaMusic's policy to use binary non-released (for some time even
>> >> > encrypted) file formats
On 18/08/18 21:18, David Kastrup wrote:
>> "Undocumented proprietary format" doesn't express the intent which
>> > "lock-in" does. As David pointed out, patents can be used to protect
>> > a proprietary format, only I don't think that, for example, the exFAT
>> > filesystem is, in his words, a "str
Wols Lists writes:
> On 18/08/18 21:18, David Kastrup wrote:
>>> "Undocumented proprietary format" doesn't express the intent which
>>> > "lock-in" does. As David pointed out, patents can be used to protect
>>> > a proprietary format, only I don't think that, for example, the exFAT
>>> > filesyst
On 18/08/18 23:28, David Kastrup wrote:
> zip has been defined using patentable techniques (like
> https://www.google.com/patents/US5051745) but the implementations are
> usually unencumbered.
Just because it has been patented does not mean it is patentable :-(
Of course, the problem is persuadin
Wols Lists writes:
> On 18/08/18 23:28, David Kastrup wrote:
>> zip has been defined using patentable techniques (like
>> https://www.google.com/patents/US5051745) but the implementations are
>> usually unencumbered.
>
> Just because it has been patented does not mean it is patentable :-(
>
> Of
On 19/08/18 00:34, David Kastrup wrote:
> As any theoretical physicist will tell you, anything that involves
> actual hardware also is maths.
Are you telling me that maths PREscribes reality? Are you telling me
that Newton got it right?
If hardware is maths, then how comes physicists aren't creat
21 matches
Mail list logo
