On Saturday, October 31, 2020 at 10:01:42 AM UTC+1, @TiddlyTweeter wrote:
Can you please clarify what you mean here!
>
> Do you mean that are TWO different Unicode glyphs for Underscore being
> used?
>
The default behaviour, should do the exact same thing as the existing
__underline__ does.
PMario wrote:
Inline nesting seems to have a problem.
Right. I noticed that. Hope its solvable!
Best wishes
TT
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an
On Saturday, October 31, 2020 at 1:44:27 AM UTC+1, TonyM wrote:
> This would allow redefinition of mark-up already in a text perhaps even
> making it behave like another mark-up language.
> and additions like
> \customise glyph="-" _element="li"
>
> - to accept bullets pasted from GitHub
>
>
I
TonyM wrote:
>
>
> *A line with〖 This inline 〗and more
>
The use of glyphs CLEARLY DIFFERENT from normal text is not just TT's issue!
It's important not to have any default glyphs that look like any common,
conventional single glyph. ANY character that renders in font like "( ...
)" is
PMario & TonyM
Can you please clarify what you mean here!
Do you mean that are TWO different Unicode glyphs for Underscore being used?
Best wishes
TT
On Saturday, 31 October 2020 09:14:29 UTC+1, PMario wrote:
>
> On Saturday, October 31, 2020 at 1:36:14 AM UTC+1, TonyM wrote:
>
> Just for
PMario wrote:
>
> @TiddlyTweeter wrote:
>
> P.S.: By the way the Pilcrow was originally used inline (often coloured
>> red) in Medieval manuscripts to indicate a ceasura / hiatus / pause in the
>> flow of a text.
>> Vellum / parchment was very expensive so text is as condensed as
>> possible.
On Saturday, October 31, 2020 at 1:36:14 AM UTC+1, TonyM wrote:
Just for clarification the double underscore (not underscore) is used, does
> this not clash with its existing use?, or is this intentional?
>
As default, it will do the same thing. So it shouldn't be a problem. But I
need to fix
On Saturday, October 31, 2020 at 11:05:06 AM UTC+1, @TiddlyTweeter wrote:
P.S.: By the way the Pilcrow was originally used inline (often coloured
> red) in Medieval manuscripts to indicate a ceasura / hiatus / pause in the
> flow of a text.
> Vellum / parchment was very expensive so text is as
TonyM
Minor footnote clarifying an issue that comes up often in understanding
Unicode font implementations.
There is masses to understand about Unicode!
My post mentioned that ...
None of the usual fonts European Language speakers would explicitly set in
> TW settings have any of them (the
TonyM wrote:
>
> ¶
> I would not bother with the use of pilcrow unless it was part of an end of
> line form of glyph only.
>
Pilcrow has a complex history before printing, in printing & on the net.
They all diverge & overlap.
Essentially the paragraph "mark" is a signal for a "longer pause"
On Saturday, October 31, 2020 at 11:05:06 AM UTC+1, @TiddlyTweeter wrote:
The use case I am thinking of is allow me to simplyfy & share with others
> an approach to correct manuscripts.
> I work often using specialist software to proof edit articles & books for
> publishers.
> This uses a
Ciao TonyM
Quick query.
When you suggest glyphs can you please also give the Unicode NUMBER!
In that way we can check where they have a chance of working (being in
fonts) across platforms & setups.
Best wishes
TT
On Saturday, 31 October 2020 02:03:36 UTC+1, TonyM wrote:
>
> Do note I found
Ciao PMario
It would be possible to use pilcrows as "start" and "end" of a paragraph,
> but I don't understand why.
> TW Pargraphs end with \n\n by default
> So the "reversed pilcrow" ⁋ <--- End String is redundant and for me
> personally it is confusing, since Libre Office and Word use: ¶ as
On Saturday, October 31, 2020 at 9:19:43 AM UTC+1, @TiddlyTweeter wrote:
>
> PMario wrote:
>
> Inline nesting seems to have a problem.
>
>
> Right. I noticed that. Hope its solvable!
>
V0.8.1 should have fixed it. If not please report!
-m
--
You received this message because you are subscribed
Ciao PMario
> @TiddlyTweeter wrote:
>
> The use case I am thinking of is allow me to simplyfy & share with others
>> an approach to correct manuscripts.
>> I work often using specialist software to proof edit articles & books for
>> publishers.
>> This uses a specific method and its own
TT,
I did read your history, it's Quite interesting. And to some extent I defer
to you, but in my return quote I pointed out the "modern" use of Pilcrow.
It is interesting to know where the indented 1st line of a paragraph comes
from, something I have never liked the aesthetics of, to be
16 matches
Mail list logo
