I have confirmation of a problem with end of line with macro rendering
text, not with wiki parsing after the macro has done its job.
simply surrond the macro call by pre and /pre tags. And behold below!
[image: bug-no-lines.png]
There is clearly a bug or a missunderstanding from my part. If I put a
blank line after the header line and each line in the loop, within the
macro definition, this does not change anything.
Le samedi 10 octobre 2020 à 00:15:39 UTC+2, TW Tones a écrit :
> Yes, I see my mistake, it the caption. sorry.
>
>
> On Saturday, 10 October 2020 09:14:47 UTC+11, TW Tones wrote:
>>
>> Jean-Pierre,
>>
>> The first line of the table does not match what follows.
>>
>> |les <$count filter="[all[current]tagging[]butlast[]]"/> critères li
>> és aux {{!!title}}|c
>> | Code | Tests |Libellé|h
>>
>> ie
>> | |c
>> | Code | Tests |Libellé|h
>>
>> Unless you use > etc.. to define it correctly the table will not render
>> correctly.
>>
>> Otherwise I expect it would work (I have not looked at the other details.
>>
>> Personally I use HTML for complex tables the tr th td tags especially
>> containing lists as there are easier to debug. I no longer use the sort
>> table definition method
>>
>> Regards
>> Tony
>>
>> On Saturday, 10 October 2020 01:57:15 UTC+11, Jean-Pierre Rivière wrote:
>>>
>>> I'm wondering if the key of my problem is not this sentence at the end
>>> of the "Transclusion and Substitution" documentation:
>>>
>>> "Transclusions are processed independently, and cannot be combined with
>>> adjacent text to define WikiText constructions."
>>>
>>> Because I am laying out the title and headers ogf my table first, then
>>> I'm doing the list widget to repeat a mechanism of transclusion for each
>>> row.
>>>
>>> If this is the case, I suspect that I would need to write a javascript
>>> macro that would output the whole table in one row. An other possibility
>>> would be that my current macros output html, but I'm not keen on that idea
>>> within a wiki.
>>>
>>> Le vendredi 9 octobre 2020 à 16:48:28 UTC+2, Jean-Pierre Rivière a
>>> écrit :
>>>
>>>> Hi! In the pursuit of my goal, I am not wanting to build a table. I've
>>>> been able to get the raw wiki code I would have written, but I can't have
>>>> it correctly interpreted, despite my using the wikify widget with html
>>>> output. I'm inclined to thin that this is something to do with line breaks
>>>> within a variable. But let's see the code fiest!
>>>>
>>>> \define compter(tagg) <$count filter="[tag[critère $tagg$]butlast[]]"/>
>>>> tagués
>>>> \define listCriterions()
>>>> \whitespace trim
>>>>
>>>> |les <$count filter="[all[current]tagging[]butlast[]]"/> critères
>>>> liés aux {{!!title}}|c
>>>> | Code | Tests |Libellé|h
>>>> <$list filter="[all[current]tagging[]butlast[]]" variable="crit">
>>>> |<$link to=<<crit>>><$transclude tiddler=<<crit>>
>>>> field="code"/></$link>|<$count filter="[tag<crit>]butfirst[]"
>>>> />|<$transclude tiddler=<<crit>> field="criterion"/>|
>>>> </$list>
>>>> \end
>>>>
>>>> \define theme()
>>>> <$wikify name="line" text="""<<listCriterions>>"""
>>>> output="html"><<line>></$wikify>
>>>>
>>>> !!! Note
>>>> {{ETSI EN 301 549}}
>>>> \end
>>>>
>>>> ----
>>>> !! listCriterions
>>>>
>>>> <<listCriterions>>
>>>>
>>>> ----
>>>> !! theme
>>>>
>>>> <<theme>>
>>>>
>>>> And here is screen capture:
>>>>
>>>> [image: bug-table-build.png]
>>>> We get the same resut with or without wikify. We have links when they
>>>> are written in a tw syntax, sot I think those two clues really show that
>>>> the recurse to wikify may not be useful. I tried the same thing with a
>>>> blank line before closing the $list widget, but this changed nothing.
>>>>
>>>> I also notice that there is no space arount the numbers transcluded in
>>>> the legend of the table (except after the first number, where I set an
>>>> unbreakable space entity. This does not seem the usual comportment for me,
>>>> and that may be a clue as to what is wrong. But I habe no idea.
>>>>
>>>> two side notes:
>>>> 1) there is no example in the wikify widget documentation, to show what
>>>> effect it really has.
>>>> 2) it would be nice to be able to see the raw output of my macro, but
>>>> I'm not sure how to do this. javascript may help, especially via the
>>>> javascript console. What are you doing for this, folks?
>>>>
>>>> Regards and thaks in advance!
>>>>
>>>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/68be4ebc-b6ed-4629-8cb5-6ad930e738c4n%40googlegroups.com.
