How to avoid writing class attributes of links and inline code

How to avoid writing class attributes of links and inline code

[news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA]

[-- Attachment #1.1: Type: text/plain, Size: 1210 bytes --]

I am converting HTML to markdown. and I have trouble with the follwoing 
HTML snippet:

Here comes a <a class="superlink" href="hallo" >link with a class</a>.

I do not find a way to convdert this to plain markdown withouyt any 
attributes. I always get:

Here comes a [link with a class](hallo){.superlink}.

despite the fact that I ahve alreay switch off the  header_attributes and 
raw_attribute extensions. 

I have the same problem with  classes to the code tag in the HTML:

Here we have a some <code class="superclass">code with a class</code>.

How can I make pandoc not to write out the class attributes to the Markdown 
output?

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a3fe3bb2-b7a8-4a05-a5be-b76e2cc3c394%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 2039 bytes --]

Re: How to avoid writing class attributes of links and inline code

[Christophe Demko]

[-- Attachment #1.1: Type: text/plain, Size: 1426 bytes --]

You can write a pandoc filter for that

Le mercredi 1 août 2018 07:23:00 UTC+2, ne...-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org a 
écrit :
>
> I am converting HTML to markdown. and I have trouble with the follwoing 
> HTML snippet:
>
> Here comes a <a class="superlink" href="hallo" >link with a class</a>.
>
> I do not find a way to convdert this to plain markdown withouyt any 
> attributes. I always get:
>
> Here comes a [link with a class](hallo){.superlink}.
>
> despite the fact that I ahve alreay switch off the  header_attributes and 
> raw_attribute extensions. 
>
> I have the same problem with  classes to the code tag in the HTML:
>
> Here we have a some <code class="superclass">code with a class</code>.
>
> How can I make pandoc not to write out the class attributes to the 
> Markdown output?
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/5199a991-9533-48f0-a60b-2efcd64e1813%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 2334 bytes --]

Re: How to avoid writing class attributes of links and inline code

[news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA]

[-- Attachment #1.1: Type: text/plain, Size: 1723 bytes --]

So does this mean, this behaviour is the *minimal* output of the normal 
markdown writer? Are these additional attributes *not* caused by an 
extension (which I could switch off)?


On Wednesday, August 1, 2018 at 6:59:46 PM UTC+10, Christophe Demko wrote:
>
> You can write a pandoc filter for that
>
> Le mercredi 1 août 2018 07:23:00 UTC+2, ne...-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org a 
> écrit :
>>
>> I am converting HTML to markdown. and I have trouble with the follwoing 
>> HTML snippet:
>>
>> Here comes a <a class="superlink" href="hallo" >link with a class</a>.
>>
>> I do not find a way to convdert this to plain markdown withouyt any 
>> attributes. I always get:
>>
>> Here comes a [link with a class](hallo){.superlink}.
>>
>> despite the fact that I ahve alreay switch off the  header_attributes and 
>> raw_attribute extensions. 
>>
>> I have the same problem with  classes to the code tag in the HTML:
>>
>> Here we have a some <code class="superclass">code with a class</code>.
>>
>> How can I make pandoc not to write out the class attributes to the 
>> Markdown output?
>>
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/2b1d187d-c12e-4ae3-a566-1e670d2e72ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 2778 bytes --]

Re: How to avoid writing class attributes of links and inline code

[John MacFarlane]

Here's what you want:

% pandoc -t markdown-raw_html-link_attributes -f html
<a class="superlink" href="hallo" >link with a class</a>
^D
[link with a class](hallo)

You just had the wrong extension (raw_attributes
rather than link_attributes).

news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org writes:

> I am converting HTML to markdown. and I have trouble with the follwoing 
> HTML snippet:
>
> Here comes a <a class="superlink" href="hallo" >link with a class</a>.
>
> I do not find a way to convdert this to plain markdown withouyt any 
> attributes. I always get:
>
> Here comes a [link with a class](hallo){.superlink}.
>
> despite the fact that I ahve alreay switch off the  header_attributes and 
> raw_attribute extensions. 
>
> I have the same problem with  classes to the code tag in the HTML:
>
> Here we have a some <code class="superclass">code with a class</code>.
>
> How can I make pandoc not to write out the class attributes to the Markdown 
> output?
>
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a3fe3bb2-b7a8-4a05-a5be-b76e2cc3c394%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Re: How to avoid writing class attributes of links and inline code

[news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA]

[-- Attachment #1.1: Type: text/plain, Size: 2632 bytes --]

Thanks John, this works indeed for classes in the anchor tag, but it does 
not work for classes in code tags:

<code class="supercode">code with a class</code> 

is converted to

`code with a class`{.supercode}

How can I get rid of the superfluous class attribute here?

Many thanks!


On Thursday, August 2, 2018 at 5:27:53 AM UTC+10, John MacFarlane wrote:
>
>
> Here's what you want: 
>
> % pandoc -t markdown-raw_html-link_attributes -f html 
> <a class="superlink" href="hallo" >link with a class</a> 
> ^D 
> [link with a class](hallo) 
>
> You just had the wrong extension (raw_attributes 
> rather than link_attributes). 
>
> ne...-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org <javascript:> writes: 
>
> > I am converting HTML to markdown. and I have trouble with the follwoing 
> > HTML snippet: 
> > 
> > Here comes a <a class="superlink" href="hallo" >link with a class</a>. 
> > 
> > I do not find a way to convdert this to plain markdown withouyt any 
> > attributes. I always get: 
> > 
> > Here comes a [link with a class](hallo){.superlink}. 
> > 
> > despite the fact that I ahve alreay switch off the  header_attributes 
> and 
> > raw_attribute extensions. 
> > 
> > I have the same problem with  classes to the code tag in the HTML: 
> > 
> > Here we have a some <code class="superclass">code with a class</code>. 
> > 
> > How can I make pandoc not to write out the class attributes to the 
> Markdown 
> > output? 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "pandoc-discuss" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org 
> <javascript:>. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pandoc-discuss/a3fe3bb2-b7a8-4a05-a5be-b76e2cc3c394%40googlegroups.com. 
>
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/e2e814c8-a8bb-4cd9-a2bb-8ece85b1cfee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 4993 bytes --]

Re: How to avoid writing class attributes of links and inline code

[John MacFarlane]

Disable the inline_code_attributes extension.

Re: How to avoid writing class attributes of links and inline code

[Jeff Payne]

That doesn’t seem to help.  Here’s the command line I’m using:

time pandoc -f markdown-inline_code_attributes -t latex -o stp.tex CRL_STP_V20191.md

Below is an example of the data causing the issue.  If I remove the table, the problem goes away.

Thanks again for your help,

Jeff Payne

## Test: c/embedded/runtesti/test063.c {#c-embedded-runtesti-test063.c}

_Test Files:_

[c/embedded/runtesti/test063.c](http://svn2.ghs.com/cgi-bin/viewvc.cgi/tools/branches/release-branch-2019-1-comp/val3/c/embedded/runtesti/test063.c?view=markup)


### Case 1: stack\_protector {#c-embedded-runtesti-test063.c-1}

+----------------------------+---------------------------------------------------------------------------------------------------+
| Test Rating                | Functional                                                                                        |
+============================+===================================================================================================+
| Requirements               | [COMP.libsys](CRL_SRD_V20191.pdf#COMP.libsys)                                                     |
+----------------------------+---------------------------------------------------------------------------------------------------+
| Design Elements            | [COMP.Design.libsys.StackCanaryAddress](CRL_SDD_V20191.pdf#COMP.Design.libsys.StackCanaryAddress) |
+----------------------------+---------------------------------------------------------------------------------------------------+
| Prerequisite Conditions    | None                                                                                              |
+----------------------------+---------------------------------------------------------------------------------------------------+
| Test Inputs                | See test procedure                                                                                |
+----------------------------+---------------------------------------------------------------------------------------------------+
| Expected Test Results      | Standard test results.                                                                            |
+----------------------------+---------------------------------------------------------------------------------------------------+
| Result Evaluation Criteria | Standard Criteria                                                                                 |
+----------------------------+---------------------------------------------------------------------------------------------------+
| Assumption / Constraint    | None                                                                                              |
+----------------------------+---------------------------------------------------------------------------------------------------+


**Procedure**:


The test verifies that the it is possible to use the function
`__ghs_get_stack_chk_guard_address` to determine the address of the "stack
canary" and set its value. It does this by:

1.  Defining `__ghs_set_stack_chk_guard()`, which uses 
    `__ghs_get_stack_chk_guard_address`  to set the guard
    value to a known value (`0xdeadbeef12345678`)
2.  Defining a test function `func` which: 
    1.  takes a pointer to an integer from its caller's stack frame,
    2.  declares its own stack-allocated buffer,
    3.  uses volatile memory reads/writes to ensure the compiler doesn't
        reorder the remaining code, and ensures that the parent stack
        allocated variable is incremented,
    4.  checks between the address of its own buffer (known to be on its
        stack frame) and the address known to be on its caller's stack
        frame, looking for the known stack guard value, and finally
    5.  if it finds the stack guard value, the test passes. Otherwise 
        the test fails.
3.  The `main()` function calls `func` and checks that the stack-allocated
    integer was incremented.



## Test: c/gcc31/gcc.dg/c99-math-float-1.c {#c-gcc31-gcc.dg-c99-math-float-1.c}

_Test Files:_

[c/gcc31/gcc.dg/c99-math-float-1.c](http://svn2.ghs.com/cgi-bin/viewvc.cgi/tools/branches/release-branch-2019-1-comp/val3/c/gcc31/gcc.dg/c99-math-float-1.c?view=markup)


### Case 1: int fpclassify\(float\) {#c-gcc31-gcc.dg-c99-math-float-1.c-1}

+----------------------------+---------------------------------------------------------------------------------------------+
| Test Rating                | Boundary Value,                                                                             |
|                            | Functional                                                                                  |
+============================+=============================================================================================+
| Requirements               | [COMP.MiscCLib.math](CRL_SRD_V20191.pdf#COMP.MiscCLib.math),                                |
|                            | [COMP.boundaryval](CRL_SRD_V20191.pdf#COMP.boundaryval)                                     |
+----------------------------+---------------------------------------------------------------------------------------------+
| Design Elements            | [COMP.Design.Math.fpclassify](CRL_SDD_V20191.pdf#COMP.Design.Math.fpclassify),              |
|                            | [COMP.Design.boundaryval.fpclassify](CRL_SDD_V20191.pdf#COMP.Design.boundaryval.fpclassify) |
+----------------------------+---------------------------------------------------------------------------------------------+
| Prerequisite Conditions    | None                                                                                        |
+----------------------------+---------------------------------------------------------------------------------------------+
| Test Inputs                | See test procedure                                                                          |
+----------------------------+---------------------------------------------------------------------------------------------+
| Expected Test Results      | Standard test results.                                                                      |
+----------------------------+---------------------------------------------------------------------------------------------+
| Result Evaluation Criteria | Standard Criteria                                                                           |
+----------------------------+---------------------------------------------------------------------------------------------+
| Assumption / Constraint    | None                                                                                        |
+----------------------------+---------------------------------------------------------------------------------------------+


**Procedure**:

An input is provided for each defined boundary value below.
It is tested to ensure that for each input, the appropriate defined
outputs is returned.  Note that parallel test cases exist for double and long double
values (c99-math-double-1.c, c99-math-long-double-1.c).

##### Test Data {-}

| Equivalence class   | Input                | Output      |
| ------------------- | -------------------- | ----------- |
| Zero                | 0.0                  | FP_ZERO     |
| Min Float           | FLT_MIN              | FP_NORMAL   |
| Large Normal        | HUGE_VALF            | FP_NORMAL   |
| Positive Infinity   | INFINITY             | FP_INFINITE |
| Positive NaN        | NAN                  | FP_NAN      |



## Test: c/kanjilib/ansi001.c {#c-kanjilib-ansi001.c}

_Test Files:_

[c/kanjilib/ansi001.c](http://svn2.ghs.com/cgi-bin/viewvc.cgi/tools/branches/release-branch-2019-1-comp/val3/c/kanjilib/ansi001.c?view=markup)


### Case 1: wctomb {#c-kanjilib-ansi001.c-1}

+----------------------------+-------------------------------------------------------------------------------+
| Test Rating                | Functional                                                                    |
+============================+===============================================================================+
| Requirements               | [COMP.libind.IntStdWC](CRL_SRD_V20191.pdf#COMP.libind.IntStdWC)               |
+----------------------------+-------------------------------------------------------------------------------+
| Design Elements            | [COMP.Design.libind.IntStdWC](CRL_SDD_V20191.pdf#COMP.Design.libind.IntStdWC) |
+----------------------------+-------------------------------------------------------------------------------+
| Prerequisite Conditions    | None                                                                          |
+----------------------------+-------------------------------------------------------------------------------+
| Test Inputs                | See test procedure                                                            |
+----------------------------+-------------------------------------------------------------------------------+
| Expected Test Results      | Standard test results.                                                        |
+----------------------------+-------------------------------------------------------------------------------+
| Result Evaluation Criteria | Standard Criteria                                                             |
+----------------------------+-------------------------------------------------------------------------------+
| Assumption / Constraint    | None                                                                          |
+----------------------------+-------------------------------------------------------------------------------+


**Procedure**:

Test that converting wide characters to multi-byte characters works correctly
using `wctomb`. Do this by populating wide character buffers with known values,
calling `wctomb` on the buffers, and verifying that the result matches a known
multi-byte character result.




> On Aug 2, 2018, at 10:47 AM, John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> wrote:
> 
> 
> Disable the inline_code_attributes extension.
> 
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/m27el8lkxy.fsf%40johnmacfarlane.net.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/87400B29-4EDA-4FE1-97C1-C7FF60FA6AC8%40paynesplace.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to avoid writing class attributes of links and inline code

[John MacFarlane]

Can you pare this down to a minimal test case that
isolates the issue?

Re: How to avoid writing class attributes of links and inline code

[leo]

This is a multi-part message in MIME format.

--_----------=_15332986027559850
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"

Thanks John. Work ror me!

Your advice is much appreciated.


On Fri, 3 Aug 2018, at 3:47 AM, John MacFarlane wrote:
>
> Disable the inline_code_attributes extension.
>


--_----------=_15332986027559850
Content-Transfer-Encoding: 7bit
Content-Type: text/html; charset="utf-8"

<!DOCTYPE html>
<html>
<head>
<title></title>
<style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style>
</head>
<body><div style="font-family:Arial;">Thanks John. Work ror me!<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">Your advice is much appreciated.<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">On Fri, 3 Aug 2018, at 3:47 AM, John MacFarlane wrote:<br></div>
<div style="font-family:Arial;">&gt;<br></div>
<div style="font-family:Arial;">&gt; Disable the inline_code_attributes extension.<br></div>
<div style="font-family:Arial;">&gt;<br></div>
<div style="font-family:Arial;"><br></div>
</body>
</html>

--_----------=_15332986027559850--

Re: How to avoid writing class attributes of links and inline code

[news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA]

[-- Attachment #1.1: Type: text/plain, Size: 781 bytes --]

Thanks John,

This works for me.

Your patient advice is much appreciated. :-)


On Friday, August 3, 2018 at 3:47:52 AM UTC+10, John MacFarlane wrote:
>
>
> Disable the inline_code_attributes extension. 
>
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/c5f2a51f-329e-40d2-a720-6cac1f4277f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 1392 bytes --]