Re: [ANNOUNCE] Fmark markup language
José Lopes <jose.lopes <at> ist.utl.pt>
2012-09-19 02:29:31 GMT
I made a first draft of your letter example.
It is not exactly as you had written but I think you might like it.
It is the combination of a content document (letter) and a style
document (letter.style). You can see the results in the PDF, which
was created using the Latex backend and the letter document
On 19-09-2012 01:21, José Lopes wrote:
> Hey Richard,
> Regarding the languages, I think it is better to start with English
> and see how successful Fmark is. There's no point in trying to tackle
> lots of languages if we cannot solve the problem for one of them.
> But then again, keeping everything Unicode.
> In fact, in this matter, I think with Haskell we have an advantage
> because things like 'isSpace' and 'isPuncuation' work with Unicode.
> I now understand that the README.md is rather incomplete. I will
> add some more information about the markup. Although, things
> like bold, italics and so on are not implemented yet.
> I will also take a look at your letter example. I think the real
> challenge here is center alignment. I will think about a
> way to solve it in Fmark so we can discuss it later on.
> Thank you for the feedback.
> On 19-09-2012 00:37, Richard O'Keefe wrote:
>> On 19/09/2012, at 1:43 AM, Stefan Monnier wrote:
>>>> The problem with that is that some people DO end some headings with
>>>> a full stop; for them your special syntax is not natural.
>>> Markdown/ReST is already using the "no syntax" idea (e.g. compared to
>>> pre-wiki markup such a LaTeX or Texinfo), so he's simply trying to push
>>> this idea further.
>> Markdown is very heavy on syntax,
>> what it is *light* on is specification of what the
>> syntax actually is. As a result,
>> I'm aware of three different dialects,
>> and someone told me about having to reverse
>> engineer the syntax from a Perl implementation.
>> As a further result, I cannot write a program to
>> reliably *generate* Markdown.
>>> I suspect it'll be difficult.
>> Oh, more power to him for trying.
>> I just don't think it can be pushed very far.
>> Oh, there is a really *filthy* hack that could be pulled
>> for italics, bold face, and so on. Contrary to its original
>> principles, Unicode includes several copies of ASCII
>> (see http://unicode.org/charts/PDF/U1D400.pdf):
>> Mathematical bold,
>> Mathematical italic,
>> Mathematical bold italic,
>> Mathematical script,
>> Mathematical bold script,
>> Mathematical fraktur,
>> Mathematical double struck (blackboard-bold),
>> Mathematical bold fraktur,
>> Mathematical sans-serif,
>> Mathematical sans-serif bold,
>> Mathematical sans-serif italic,
>> Mathematical sans-serif bold italic,
>> Mathematical monospace,
>> and some similar sets of Greek.
>> So as long as you don't want strike-through or underlying,
>> and as long as you don't want italic Cyrillic &c, ...
>> Too bad if you want a bold italic capital Thorn...
>>>> What if I want to use indentation to express quotation instead?
>>> I think this one is solvable: a paragraph that's more indented than the
>>> previous heading can be considered a quote.
>> Ah, but the quotation might not end with a sentence terminator,
>> so that would be considered a new heading.
>> Haskell-Cafe mailing list
>> Haskell-Cafe <at> haskell.org
José António Branquinho de Oliveira Lopes
Instituto Superior Técnico
Technical University of Lisbon
123 Copper Road,
New Zealand 9999
31 February 2016
I am writing to you because I am tired of frobulating.
I am also tired of this and that.
Yours without wax,
Dr Strabismus of Utrecht
(whom God preserve!)
Haskell-Cafe mailing list
Haskell-Cafe <at> haskell.org