python-markdown-discuss — A general purpose discussion list

Re: [Python-markdown-discuss] colspan/rowspan for tables?

[Maurice v. d. P. <gri...@kf...>]

On Wed, Mar 23, 2016 at 07:26:33AM +0000, Dave Pawson wrote:
> > It might be, but I consider rowspan/colspan to be a content decision and
> > not a styling one.
> 
> I disagree. Presentation - spanning, is not, IMHO, content.

Ok, then I'm not sure how you would separate the content from spanning.
Would you always create all cells in the content and merge them in
presentation?

What would you expect to find in the content for a table that has a row
of which the first cell should span 2 columns?

And similarly, what would you expect in the content for a table that has
a cell in the first column that (when presented) should span 2 rows?

Best regards,
Maurice.

-- 
Maurice van der Pot

Kdiff3 developer   gri...@kf...   http://kdiff3.sourceforge.net
Tdiff3 developer                            https://github.com/Griffon26/tdiff3

Re: [Python-markdown-discuss] colspan/rowspan for tables?

[Waylan L. <way...@ic...>]

On 03/22/2016 02:57 PM, Maurice van der Pot wrote:
> My colleagues and I have been creating some tables for which a rowspan
> feature would have been useful, but unfortunately it's not supported by
> the current syntax.
>
> Before looking into writing my own extension, I wanted to ask you if
> you're open to changes in the existing tables extension to support
> colspan and rowspan.

Maurice,

Please see my response here: 
https://github.com/waylan/Python-Markdown/pull/74#issuecomment-3622297

So to answer your question, no I am not interested in making changes to 
th existing Extension. I would suggest you build your own.

Waylan

Re: [Python-markdown-discuss] colspan/rowspan for tables?

[Dave P. <dav...@gm...>]

On 22 March 2016 at 21:54, Maurice van der Pot <gri...@kf...> wrote:
> Hi Dave,
>
> On Tue, Mar 22, 2016 at 08:06:15PM +0000, Dave Pawson wrote:
>> || is overloading current markup? How to differentiate between
>> my 'empty' cell and your colspan?
>
> I don't believe it is. An empty cell already requires at least one space
> between two vertical bars. Adjacent vertical bars are currently treated
> as a single bar.

So it would just be the interpretation of two or more bars.
Sounds good, no change in semantic.


>
>> Is there a way to use meta markup?
>
> I'm not sure what you mean by that.

See below


>
>> id the table, id the row then the colspan (start / end)
>>   Perhaps steal the Xpath syntax for this?
>>
>> Is CSS capable of doing this?
>
> It might be, but I consider rowspan/colspan to be a content decision and
> not a styling one.

I disagree. Presentation - spanning, is not, IMHO, content.

But if you're talking about including css/xpath-style
> things in the markup, I think my proposal fits better with markdown's
> purpose of being "publishable as-is, as plain text, without looking like
> it’s been marked up with tags or formatting instructions".

No, I was not intending a content addition.
A separate file which specified spanning requirements,
which might use CSS, if possible.

Select the cells, then CSS created to style it for spanning.
This would address colspan also.

Especially since no colspan can be added without
disrupting present use?


regards





> --
> Maurice van der Pot
>
> Kdiff3 developer   gri...@kf...   http://kdiff3.sourceforge.net
> Tdiff3 developer                            https://github.com/Griffon26/tdiff3



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk

Re: [Python-markdown-discuss] colspan/rowspan for tables?

[Maurice v. d. P. <gri...@kf...>]

Hi Dave,

On Tue, Mar 22, 2016 at 08:06:15PM +0000, Dave Pawson wrote:
> || is overloading current markup? How to differentiate between
> my 'empty' cell and your colspan?

I don't believe it is. An empty cell already requires at least one space
between two vertical bars. Adjacent vertical bars are currently treated
as a single bar.

> Is there a way to use meta markup?

I'm not sure what you mean by that.

> id the table, id the row then the colspan (start / end)
>   Perhaps steal the Xpath syntax for this?
> 
> Is CSS capable of doing this?

It might be, but I consider rowspan/colspan to be a content decision and
not a styling one. But if you're talking about including css/xpath-style
things in the markup, I think my proposal fits better with markdown's
purpose of being "publishable as-is, as plain text, without looking like
it’s been marked up with tags or formatting instructions".

Best regards,
Maurice.

-- 
Maurice van der Pot

Kdiff3 developer   gri...@kf...   http://kdiff3.sourceforge.net
Tdiff3 developer                            https://github.com/Griffon26/tdiff3

Re: [Python-markdown-discuss] colspan/rowspan for tables?

[Dave P. <dav...@gm...>]

|| is overloading current markup? How to differentiate between
my 'empty' cell and your colspan?

Is there a way to use meta markup?

id the table, id the row then the colspan (start / end)
  Perhaps steal the Xpath syntax for this?

Is CSS capable of doing this?

Just ideas.

HTH Dave



On 22 March 2016 at 18:57, Maurice van der Pot <gri...@kf...> wrote:
> My colleagues and I have been creating some tables for which a rowspan
> feature would have been useful, but unfortunately it's not supported by
> the current syntax.
>
> Before looking into writing my own extension, I wanted to ask you if
> you're open to changes in the existing tables extension to support
> colspan and rowspan.
>
> The syntax I had in mind uses adjacent pipes for signalling colspan and
> underscores for rowspan, e.g.:
>
> |col1        |col2    |
> |------------|--------|
> |colspan example     ||
> |rowspan ex. |        |
> |__          |        |
> |blah        |blah    |
>
> The second (or third, etc) adjacent pipe characters are currently
> ignored and do not lead to the creation of additional cells. The above
> example would currently have a single cell on second row that was as
> wide as the cell containing "col1". Only when there's a space in between
> the pipes will an additional cell be created. So for colspan I expect
> the change would not break a lot of documents.
>
> The syntax for rowspan could be in use at the moment, but the chance of
> breaking existing documents can hopefully be kept small by choosing a
> syntax that requires the cell to contain only underscores and spaces and
> optionally (to be more strict) requires the underscores to be on the
> first and/or last character position in the cell.
>
> Looking forward to hearing your thoughts on the matter.
>
> Best regards,
> Maurice.
>
> --
> Maurice van der Pot
>
> Kdiff3 developer   gri...@kf...   http://kdiff3.sourceforge.net
> Tdiff3 developer                            https://github.com/Griffon26/tdiff3
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk

[Python-markdown-discuss] colspan/rowspan for tables?

[Maurice v. d. P. <gri...@kf...>]

My colleagues and I have been creating some tables for which a rowspan
feature would have been useful, but unfortunately it's not supported by
the current syntax.

Before looking into writing my own extension, I wanted to ask you if
you're open to changes in the existing tables extension to support
colspan and rowspan.

The syntax I had in mind uses adjacent pipes for signalling colspan and
underscores for rowspan, e.g.:

|col1        |col2    |
|------------|--------|
|colspan example     ||
|rowspan ex. |        |
|__          |        |
|blah        |blah    |

The second (or third, etc) adjacent pipe characters are currently
ignored and do not lead to the creation of additional cells. The above
example would currently have a single cell on second row that was as
wide as the cell containing "col1". Only when there's a space in between
the pipes will an additional cell be created. So for colspan I expect
the change would not break a lot of documents.

The syntax for rowspan could be in use at the moment, but the chance of
breaking existing documents can hopefully be kept small by choosing a
syntax that requires the cell to contain only underscores and spaces and
optionally (to be more strict) requires the underscores to be on the
first and/or last character position in the cell.

Looking forward to hearing your thoughts on the matter.

Best regards,
Maurice.

-- 
Maurice van der Pot

Kdiff3 developer   gri...@kf...   http://kdiff3.sourceforge.net
Tdiff3 developer                            https://github.com/Griffon26/tdiff3

[Python-markdown-discuss] (no subject)

[<rmi...@ya...>]

[Python-markdown-discuss] Adding source line information to HTML nodes

[Dmitry S. <mi...@gm...>]

Hi Waylan and all,

In ReText, we (Maurice van der Pot and I) want to implement the synchronized
scrolling of editor and preview areas. For that, we need to add the information
about source line numbers to the HTML.

Maurice has implemented an extension (attached below) that:

  * Has a preprocessor that inserts placeholders with text '$posmapmarker$N' to
    empty lines, where N is line number.

  * Has a block processor that parses these placeholders, gets the previous
    element, and sets an HTML attribute on it.

This works, but is a bit hacky, and also works only on top-level elements (for
example this way it's impossible to set source information on list items).

Does anybody know of a better way of implementing such a thing using our
extension API?

--
Dmitry Shachnev

Re: [Python-markdown-discuss] Autogenerated ids in Russian

[Dmitry S. <mi...@gm...>]

Hi,

On Sat, Jan 30, 2016 at 08:59:43PM +0300, 73budden . wrote:
> Hi!
>   I have my repo on Bitbucket. I have titles in Russian, but all
> Russian characters are wiped away in autogenerated header ids, so
> header ids are just "markdown-header-_1" and so on.
>   Bitbucket uses safe mode for my md files.
>   Could it be arranged so that Russian characters are not ignored?

You can't use cyrillic letters in HTML node IDs, so you need some kind of
transliteration.

There is a transliterate package on PyPI [1], though I have never used it
myself. Maybe it's possible to make toc extension use it (if it's available,
of course), or make it possible for extension users to hook their own custom
text processing functions (which will use i.e. that module)?

[1]: https://pypi.python.org/pypi/transliterate

--
Dmitry Shachnev (aka Дмитрий Шачнев :))

[Python-markdown-discuss] Autogenerated ids in Russian

[73budden . <bud...@gm...>]

Hi!
  I have my repo on Bitbucket. I have titles in Russian, but all
Russian characters are wiped away in autogenerated header ids, so
header ids are just "markdown-header-_1" and so on.
  Bitbucket uses safe mode for my md files.
  Could it be arranged so that Russian characters are not ignored?
  Thanks!

[Python-markdown-discuss] Adding more advance control like textbox or textarea with markdown

[Jaimin P. <jp...@tu...>]

I would like to add textbox into the content, not a generic custom solution
but very specific to the usecase. Currently using markdown to render the
basic HTML content, and want to continue using the same. However, in some
of the use cases I need to extend it and add the control to get the user
response. Does python markdown extension make sense for this change? I am
thinking to add specific identifier pattern to recognize the textbox and
render the replacement input text control.

Any suggestion?

Thanks.
-- 
Jaimin

[Python-markdown-discuss] Linux, emacs, file encoding

[Dave P. <dav...@gm...>]

I've a few Unicode utf-8 characters in a md file.
I set the emacs buffer to Unix, utf-8
but when I save the file, a script 'convert-markdown.sh'
seems to be called and the buffer is converted to DOS

Is it possible to stop this please?

error is

Traceback (most recent call last):
  File "/files/python/mymarkdown.py", line 13, in <module>
    text = input_file.read()
  File "/usr/lib64/python2.7/codecs.py", line 668, in read
    return self.reader.read(size)
  File "/usr/lib64/python2.7/codecs.py", line 474, in read
    newchars, decodedbytes = self.decode(data, self.errors)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xb1 in position
4999: invalid start byte

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk

Re: [Python-markdown-discuss] Em-dash extension

[Kalle R. <kal...@ho...>]

Waylan,

This addressed my problem exactly; thank you.

Regards,
Kalle

1.5.2015, 3:27, Waylan Limberg kirjoitti:
> Kalle,
>
> Sorry for the delayed response.
>
> You may be interested to know that the Smarty Extension [1] exists 
> which already implements what you are trying to achieve along with all 
> the various other parts of SmartyPants.
>
> However, if you would prefer to not have all of SmartyPants, but only 
> your specific feature, then you need to be aware that HTML entities 
> (like `—`) are considered raw HTML and will get escaped by the 
> serializer when you insert them into an ElementTree Element. 
> Therefore, you will need to avoid them going through the serializer, 
> which can be accomplished with the HtmlStash [2], an instance of which 
> is available at `self.markdown.htmlStash` within an Inlinepattern. 
> Note that you will want to pass you HTML entity to the `store` method 
> which will return a placeholder. Your `handleMatch` method will then 
> need to return that placeholder. Something like this:
>
> def handleMatch(self, m):
> placeholder = self.markdown.htmlStash.store('—')
> return placeholder
>
> Then, after the ElementTree is serialized, the parser will go through 
> the entire document and swap out all the placeholders for the raw HTML 
> in the stash.
>
> I hope this helps.
> Waylan Limberg
> [1]: https://pythonhosted.org/Markdown/extensions/smarty.html
> [2]: https://github.com/waylan/Python-Markdown/blob/master/markdown/util.py#L131
>
> On Apr 29, 2015, at 07:57 AM, Kalle Rutanen 
> <kal...@ho...> wrote:
>
>> Hi everyone,
>>
>> I'm trying to extend Python Markdown so that --- would be converted to
>> an em-dash. For this, I built up an inline-pattern which matches --, and
>> returns "&mdash;" from handleMatch(). Unfortunately, this gets to
>> converted to "&amp;mdash;" by Python Markdown. How can I get the &mdash;
>> through without changes?
>>
>> Kalle
>>
>>
>> ------------------------------------------------------------------------------
>> One dashboard for servers and applications across Physical-Virtual-Cloud
>> Widest out-of-the-box monitoring support with 50+ applications
>> Performance metrics, stats and reports that give you Actionable Insights
>> Deep dive visibility with transaction tracing using APM Insight.
>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>> _______________________________________________
>> Python-markdown-discuss mailing list
>> Pyt...@li... 
>> <mailto:Pyt...@li...>
>> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss

Re: [Python-markdown-discuss] Em-dash extension

[Waylan L. <way...@ic...>]

Kalle,

Sorry for the delayed response. 

You may be interested to know that the Smarty Extension [1] exists which already implements what you are trying to achieve along with all the various other parts of SmartyPants.

However, if you would prefer to not have all of SmartyPants, but only your specific feature, then you need to be aware that HTML entities (like `—`) are considered raw HTML and will get escaped by the serializer when you insert them into an ElementTree Element. Therefore, you will need to avoid them going through the serializer, which can be accomplished with the HtmlStash [2], an instance of which is available at `self.markdown.htmlStash` within an Inlinepattern. Note that you will want to pass you HTML entity to the `store` method which will return a placeholder. Your `handleMatch` method will then need to return that placeholder. Something like this:

    def handleMatch(self, m):
        placeholder = self.markdown.htmlStash.store('—')
        return placeholder

Then, after the ElementTree is serialized, the parser will go through the entire document and swap out all the placeholders for the raw HTML in the stash.

I hope this helps.
Waylan Limberg
[1]: https://pythonhosted.org/Markdown/extensions/smarty.html
[2]: https://github.com/waylan/Python-Markdown/blob/master/markdown/util.py#L131

On Apr 29, 2015, at 07:57 AM, Kalle Rutanen <kal...@ho...> wrote:

Hi everyone,

I'm trying to extend Python Markdown so that --- would be converted to 
an em-dash. For this, I built up an inline-pattern which matches --, and 
returns "&mdash;" from handleMatch(). Unfortunately, this gets to 
converted to "&amp;mdash;" by Python Markdown. How can I get the &mdash; 
through without changes?

Kalle


------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Python-markdown-discuss mailing list
Pyt...@li...
https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss

[Python-markdown-discuss] Em-dash extension

[Kalle R. <kal...@ho...>]

Hi everyone,

I'm trying to extend Python Markdown so that --- would be converted to 
an em-dash. For this, I built up an inline-pattern which matches --, and 
returns "—" from handleMatch(). Unfortunately, this gets to 
converted to "—" by Python Markdown. How can I get the — 
through without changes?

Kalle

[Python-markdown-discuss] Version 3.0 Road Map

[Waylan L. <way...@ic...>]

FYI, I've posted a plan for moving toward version 3.0 of Python-Markdown:

https://github.com/waylan/Python-Markdown/issues/391

Any and all feedback is welcome. 

Waylan Limberg 

[Python-markdown-discuss] Version 2.6 Released

[Waylan L. <way...@ic...>]

Python-Markdown 2.6 has just been released. Please, install, test and report bugs.

Extension authors will want to read the release notes carefully. There are a number of deprecated things that will break with the next release.  You may want to run Python with deprecation warnings turned on (they are off by default) to see if your code raises any. And while I'm on the subject, I will point out that a new tutorial for creating extensions has been created and includes instructions on how to provide installation in a proper way (may extensions have been observed instructing their users to use weird, hacky, unpythonic methods  -- which will likely stop working with the next release). Get your fixes in now and your users shouldn't notice anything.

The relevant links:
https://pypi.python.org/pypi/Markdown/2.6
https://pythonhosted.org/Markdown/release-2.6.html
https://github.com/waylan/Python-Markdown/wiki/Tutorial:-Writing-Extensions-for-Python-Markdown

Waylan Limberg

[Python-markdown-discuss] Re: Specifying language for code blocks in lists

[Waylan L. <way...@ic...>]

Szabolcs,

You appear to be using fenced code blocks. However, as stated in the [docs][1], they "are only supported at the document root level. Therefore, they cannot be nested inside lists or blockquotes."

As a reminder, fenced code blocks are not part of the Markdown specification. They are an unofficial add on. The standard way of adding code blocks is to indent them. When nested in a list, you need to double indent them, once to nest them in a list, and once to format them as code blocks. It appears that you have done that in your example.

Of course, that doesn't identify the language. However, the [docs][2] for the CodeHilite extension describe three different ways to identify the language of a given code block. I suspect you will find that helpful.
Waylan Limberg

[1]: https://pythonhosted.org/Markdown/extensions/fenced_code_blocks.html#syntax
[2]: https://pythonhosted.org/Markdown/extensions/code_hilite.html#syntax


On Feb 06, 2015, at 01:33 PM, Szabolcs Horvát <szh...@gm...> wrote:

Hello,

I am (indirectly) using Python Markdown with the codehilite extension.

When writing markdown compatible with this processor, is there a way to specify the highlighting language for a code block contained within a list?

Take for example,

----

 1. List element one
 
 2. List element two has a code block
 
        <some> "code" here()

----

When the code block is not in a list, I can use

```langspec
<some> "code" here()
```

but the ``` doesn't seem to be allowed within lists.

Is there a workaround?  I don't expect that there will be, but I thought I'd ask, just in case.

 -- Szabolcs
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Python-markdown-discuss mailing list
Pyt...@li... 
https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss 

[Python-markdown-discuss] Specifying language for code blocks in lists

[Szabolcs H. <szh...@gm...>]

Hello,

I am (indirectly) using Python Markdown with the codehilite extension.

When writing markdown compatible with this processor, is there a way to
specify the highlighting language for a code block contained within a list?

Take for example,

----

 1. List element one

 2. List element two has a code block

        <some> "code" here()

----

When the code block is not in a list, I can use

```langspec
<some> "code" here()
```

but the ``` doesn't seem to be allowed within lists.

Is there a workaround?  I don't expect that there will be, but I thought
I'd ask, just in case.

 -- Szabolcs

Re: [Python-markdown-discuss] Question about top-level module extensions

[Dmitry S. <mi...@gm...>]

Hi Waylan,

On Mon, 02 Feb 2015 23:13:25 +0000, Waylan Limberg wrote:
> That is a bug, which I just pushed a fix for.

Thank you! Works fine now.

--
Dmitry Shachnev

[Python-markdown-discuss] Question about top-level module extensions

[Dmitry S. <mi...@gm...>]

Hi,

When working on my [math extension][1] I noticed that Python-Markdown
refuses to import it when it is installed as a top-level Python module.

The failing check is one that is introduced in [commit 8f878c37][2].

The extension imports sucessfully (using `import_module('math')`),
but it does not contain `extendMarkdown` function at module level.
There is `MathExtension.extendMarkdown` function, though.

Is it possible to change the `hasattr(module, 'extendMarkdown')` to
something like `hasattr(module, 'makeExtension')`? Then the check
will look like

    (hasattr(module, 'makeExtension') or (class_name and hasattr(module, class_name)))

which should be true for any Python-Markdown extension, right?

[1]: https://github.com/mitya57/python-markdown-math
[2]: https://github.com/waylan/Python-Markdown/commit/8f878c37dc3613b7

--
Dmitry Shachnev

Re: [Python-markdown-discuss] Summary page & links

[Dave P. <dav...@gm...>]

Not quite what you want.
I convert all files in current directory to html from md
then generate an index file (top level) but use the file
names.

You may be able to build on that and iterate through directories?
Assumes using Linux / bash.
If that's the case, see below
here=`pwd`
pysource=/files/python/mymarkdown.py
idx="index.html"
idxbn="index"
# Create top of index file

echo "<html><head><title>Index of Markdown files</title> <meta
http-equiv=\"Content-Type\" content=\"text/html; charset=utf-8\" />
</head><body>
<h2>Index of files</h2>
<ol>
" >$idx


clear
for fil in *.md
 do
bn=`nameonly $fil`
#echo processing ${bn}.md to  ${bn}.html
python ${pysource} ${bn}.md ${bn}.html
echo "<li><a href='${bn}.html'>${bn}.html</a></li> ">>$idx
done


# finish of index file

echo "</ol></body></html>
" >>$idx

On 31 January 2015 at 12:25, Albert Williams <alb...@my...> wrote:
> Hi all,
> Apologies if this was asked before...also apologies if my understanding is
> incorrect.
> I have a directory/folder structure that has one detail.md file in each
> folder.
> I am required to parse these .md files & generate a summary.md file at the
> root folder level.
> The summary.md file should include the some headers from the content of the
> detail.md files.
> It's to include these in summary.md a different layout format (i.e. a table
> format with each detail.md content as a row).
> These files are to be generated into static html files with links between
> summary.html & detail.html & links back also.
>
> I've a few questions that I'm hoping someone will be able to help with.
> PLEASE!
>
> 1. Is Python-Markdown the tool for doing this? It looks class, but I just
> haven't seen the use cases that allows me to create new .md files from
> current .md files.
>
> 2. Can I generate a summary.md file from parsing certain fields from many
> detail.md files. Python/Java would be the preferred languages.
> Sorry, I've searched but I haven't seen a use case like this as an example.
>
> 3. I'll need to generate a static html site from all these .md files. I see
> there are a few options here.
> I see a few options here, pelican & jekyll being 2.
> But can I generate links from summary.md files to detail.md files & also
> create links from detail.md files to the root folder summary.md files?
> I expect I'd have to code this in .md before converting to .html.
>
> Thanks again for any support, very much appreciated!!!
> Regards,
> ACW
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk

[Python-markdown-discuss] Summary page & links

[Albert W. <alb...@my...>]

Hi all,
Apologies if this was asked before...also apologies if my understanding is
incorrect.
I have a directory/folder structure that has one detail.md file in each
folder.
I am required to parse these .md files & generate a summary.md file at the
root folder level.
The summary.md file should include the some headers from the content of the
detail.md files.
It's to include these in summary.md a different layout format (i.e. a table
format with each detail.md content as a row).
These files are to be generated into static html files with links between
summary.html & detail.html & links back also.

I've a few questions that I'm hoping someone will be able to help with.
PLEASE!

1. Is Python-Markdown the tool for doing this? It looks class, but I just
haven't seen the use cases that allows me to create new .md files from
current .md files.

2. Can I generate a summary.md file from parsing certain fields from many
detail.md files. Python/Java would be the preferred languages.
Sorry, I've searched but I haven't seen a use case like this as an example.

3. I'll need to generate a static html site from all these .md files. I see
there are a few options here.
I see a few options here, pelican & jekyll being 2.
But can I generate links from summary.md files to detail.md files & also
create links from detail.md files to the root folder summary.md files?
I expect I'd have to code this in .md before converting to .html.

Thanks again for any support, very much appreciated!!!
Regards,
ACW

[Python-markdown-discuss] Summary page & links

[Albert W. <alb...@gm...>]

Hi all,
Apologies if this was asked before...also apologies if my understanding is
incorrect.
I have a directory/folder structure that has one detail.md file in each
folder.
I am required to parse these .md files & generate a summary.md file at the
root folder level.
The summary.md file should include the some headers from the content of the
detail.md files.
It's to include these in summary.md a different layout format (i.e. a table
format with each detail.md content as a row).
These files are to be generated into static html files with links between
summary.html & detail.html & links back also.

I've a few questions that I'm hoping someone will be able to help with.
PLEASE!

1. Is Python-Markdown the tool for doing this? It looks class, but I just
haven't seen the use cases that allows me to create new .md files from
current .md files.

2. Can I generate a summary.md file from parsing certain fields from many
detail.md files. Python/Java would be the preferred languages.
Sorry, I've searched but I haven't seen a use case like this as an example.

3. I'll need to generate a static html site from all these .md files. I see
there are a few options here.
I see a few options here, pelican & jekyll being 2.
But can I generate links from summary.md files to detail.md files & also
create links from detail.md files to the root folder summary.md files?
I expect I'd have to code this in .md before converting to .html.

Thanks again for any support, very much appreciated!!!
Regards,
ACW

Re: [Python-markdown-discuss] Order of precedence, inlines?

[Waylan L. <way...@ic...>]

Note that this tutorial is not the definitive documentation for the
extension API. This is simply an example of how to use it. The actual
documentation lives at https://pythonhosted.org/Markdown/extensions/api.html
and is linked from the tutorial. I suspect that will answer most of your
questions. As for where the specific inline patterns are defined, a quick
read of the source code would answer that. Everything is organized in a
self-explanatory way (I think - although I may be bias). So
`markdown/inlinepatterns.py` would give you what you want. In fact the
`build_inlinepatterns` function starts on line 59:
https://github.com/waylan/Python-Markdown/blob/master/markdown/inlinepattern
s.py#L59

I hope that helps.

Waylan

-----Original Message-----
From: Dave Pawson [mailto:dav...@gm...] 
Sent: Sunday, January 25, 2015 5:09 AM
To: PythonMD list
Subject: [Python-markdown-discuss] Order of precedence, inlines?

https://github.com/waylan/Python-Markdown/wiki/Tutorial:-Writing-Extensions-
for-Python-Markdown

has an example
"we are inserting a new inline pattern named 'del', using our pattern
instance del_tag after the pattern named "not_strong" (thus the
'>not_strong')."

The code is
md.inlinePatterns.add('del', del_tag, '>not_strong')

Questions
1. Where is this order defined please?
2. I never use ___emph__ and would like
to remove it, then extend to provide __
for underscore (<u>).
   How to find the 'key' to use for __ emphasis please to remove this markup
using del md.inlinePatterns['????']

TiA



--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk

----------------------------------------------------------------------------
--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Python-markdown-discuss mailing list
Pyt...@li...
https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss