- Original Message -
From: "Urs Liska"
To:
Sent: Wednesday, January 15, 2014 11:30 PM
Subject: Re: Pre-review questions about image(s) and translations
Hm, now I see that I can't use a LilyPond example on the website (I mean
to let it auto-generate), this works only
Am 16.01.2014 12:45, schrieb Marc Hohl:
Am 16.01.2014 09:08, schrieb Urs Liska:
Am 16.01.2014 08:58, schrieb Graham Percival:
On Wed, Jan 15, 2014 at 08:33:37AM -0500, Carl Peterson wrote:
My first instinct is to prepare an SVG file that could be
processed with
inkscape or another prog
Am 16.01.2014 09:08, schrieb Urs Liska:
Am 16.01.2014 08:58, schrieb Graham Percival:
On Wed, Jan 15, 2014 at 08:33:37AM -0500, Carl Peterson wrote:
My first instinct is to prepare an SVG file that could be
processed with
inkscape or another program as part of the make process.
That i
Am 16.01.2014 08:58, schrieb Graham Percival:
On Wed, Jan 15, 2014 at 08:33:37AM -0500, Carl Peterson wrote:
My first instinct is to prepare an SVG file that could be processed with
inkscape or another program as part of the make process.
That is not do-able for the website due to our
On Wed, Jan 15, 2014 at 08:33:37AM -0500, Carl Peterson wrote:
>My first instinct is to prepare an SVG file that could be processed with
>inkscape or another program as part of the make process.
That is not do-able for the website due to our hosting&build
situation. I've commented on this
Am 15.01.2014 18:32, schrieb Paul Morris:
Carl Peterson wrote
Maybe not texidoc-wise, but it's something I thought about on its own
merits. I'm personally not crazy about is as it would basically result in
us creating a very specialized set of CSS parameters for a very specific
thing that could
Am 15.01.2014 18:32, schrieb Paul Morris:
Those are good points. Using inline styles would be a way to address these
issues, while raising others... but maybe it wouldn't work with texidoc
anyway.
I gave a markup version a try:
That's great! Thanks.
I will play around with this and integrate
\rounded-box \pad-markup #1
{"LilyPond"}
\combine
\draw-line #'(0 . 4)
\arrow-head #Y #DOWN ##f
\box \pad-markup #1 {
\line \box \pad-markup #1 \with-color #blue
{ "PDF" "SVG" "PNG" "MIDI" "More..." }
}
On Wed, Jan 15, 2014 at 10:15 AM, Urs Liska wrote:
> Am 15.01.2014 16:13, schrieb Paul Morris:
>
> Urs Liska wrote
>>
>>> a) in what form should I provide such an image that it can be translated
>>> and modified in the future?
>>>
>>
>> Since your image is simply boxes with text and arrows conne
Another possibility would be to do it as a LilyPond snippet using markup
commands. That would keep it as close as possible to the usual LilyPond
docs/website process.
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Pre-review-questions-about-image-s-and
Am 15.01.2014 16:13, schrieb Paul Morris:
Urs Liska wrote
a) in what form should I provide such an image that it can be translated
and modified in the future?
Since your image is simply boxes with text and arrows connecting them, one
possibility might be to do it with html and css rather than
://lilypond.1069038.n5.nabble.com/Pre-review-questions-about-image-s-and-translations-tp157874p157917.html
Sent from the Dev mailing list archive at Nabble.com.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On Tue, Jan 14, 2014 at 11:51 AM, Urs Liska wrote:
>
>
> As you can see I have created a flowchart to visualize the relation
> between the different parts of the editing cycle.
>
> If it were simple the two PNG files I knew that I would have to add them
> to lilypond-extra and open a pull request
Hi,
I'm going to continue my website work.
As discussed earlier I have written an additional page about the
editing->compiling concept. While this is essentially self-evident it
seems that we need an additional step to get new users on the right
track here. The page will be added between "Text
14 matches
Mail list logo
