[twdev] Re: Custom markup (continued)

*1. Why use Json in TiddlyWiki by standard?* 1. "JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language

[twdev] Re: Custom markup (continued)

Hi all! *1. Question* 1. Would it be possible to have a better abstraction in the custom markup? So that we could separate the logical layer from the application, the interface/interaction layer from the data layer? - An example of the application logic layer: includes keywords like

[twdev] Re: [side topic] The Scratch programming language and UI

Well yeah ... but while you're contemplating the syntactic sugar of Scratch, consider Snap! which is a cleaner implementations. But if one has to implement turtle graphics -- similar to SVG -- anyway, then why not provide turtle graphics sooner rather than later during any development cycle

[twdev] Re: [side topic] The Scratch programming language and UI

Hi mat! How are you? great idea! On Sunday, September 4, 2016 at 4:15:15 PM UTC-3 Mat wrote: > Scratch is a programming language + > environment made to make kids learn how to code. It is one of the most > successful and recommended languages for this, and has been

[twdev] Re: Tiddloid Lite - another new android editor

love it! great tool ;D On Friday, October 11, 2019 at 8:35:25 AM UTC-3 donmor3000 wrote: > > > > > I made this version 'cause of the scoped

[twdev] Re: Need help to create a javascript library & invoke this.wiki.xxxx() from it

Much more activity at https://talk.tiddlywiki.org/. Try over there. :) On Wednesday, October 27, 2021 at 1:14:54 AM UTC-7 vpl.p...@gmail.com wrote: > Hi guys, > > I need a bit of help to understand how to access getTiddler method from > a javascript library > > When I develop *macro*

[twdev] Re: Adding client-specific appearance tweaks panel under Control Panel -> Appearance

donmor, Thanks for continuing development on tiddloid. It is a valuable contribution. I was wondering if you are joining us on discourse?. I would like to initiate a private conversation on something that may be of interest and it would be easier over there because we can avoid emails.

[twdev] Re: Tiddloid - A new android editor is to be released

Now the new Tiddloid 2.0.0 is available! Click here Update details: - Refactored file system implementation and now it mainly use Storage Access Framework (lecacy file:// mode still initially supported). - Now supports SAF folder

[twdev] Re: Tiddloid - A new android editor is to be released

Finally I got ready to merge all good things of Tiddloid Lite into Tiddloid, which will implement new APIs and work well on new devices. Here's a link to the latest pre-release page: https://github.com/donmor/Tiddloid/releases/tag/2.0.0a2 在2021年5月12日星期三 UTC+8 下午1:17:27 写道： > @TonyM I'm glad

[twdev] Re: [TW5] Trying to keep my unique parse tree

Hi Jeremy, Parse rule is working (parse tiddler/haystack for needles) and completing with: return [{ type: "action-setfield", tag: "$action-setfield", params: params attributes: {

[twdev] Re: [TW5] - Help creating macro / widget for an existing javascript tool

Hey Mario: Following your pointer to that "Open Source Javascript Gantt " library, I have to say that this is the slickest implementation of interactive Gantt chart functionality i've been able to find anywhere. That's me speaking from naive user perspective, of

[twdev] Re: [TW5] - Help creating macro / widget for an existing javascript tool

Hey @ank.m... Long time no action in this discussion thread, but i'm curious: Have you managed to get something working that satisfies your need? It was via this more recent discussion thread in the TW Users group that i learned of

[twdev] Re: Saving on Dropbox with TiddlyWiki5 in the Sky?

Ops, wrong Dl---blame gmail autocompletion...or my short attention span. Sorry for the noise devs, keep up the good work! On Mon, May 17, 2021 at 11:26 AM stefano franchi wrote: > I have recently come back to my TW5 files after a couple of years hiatus > and I cannot get the save to Dropbox to

[twdev] Re: Tiddloid - A new android editor is to be released

@TonyM I'm glad to see someone tend to support me. There's a Liberapay link on my homepage(https://donmor.top), so feel free to visit my site and, If you'd like, buy me a can of soda :) 在2021年5月12日星期三 UTC+8 上午7:23:58 写道： > Donmor, > > Please see if you can get this into a store and charge a

[twdev] Re: Tiddloid - A new android editor is to be released

Donmor, Please see if you can get this into a store and charge a few bucks so we can return something for your effort. Even if you leave the apks for the poorer amongst us :) Love your work Tones On Monday, 10 May 2021 at 09:36:36 UTC+10 donmor3000 wrote: > A new version (1.4.0) is coming.

Re: [twdev] Re: Tiddloid - A new android editor is to be released

Hi donmor3000, Many thanks for the update! Downloaded and tested the Lite version on ANdroid 10 and works just great! Side Note: Please post here https://github.com/Jermolene/TiddlyWiki5/discussions The Tiddlywikidev is not read by many users! Best wishes Mohammad On Mon, May 10, 2021 at

[twdev] Re: Tiddloid Lite - another new android editor

A new version (1.2.0) is coming. Go to the GitHub Release page to get the testing packages. *Update details:* - Main activity and splash now supports landscape mode - Now showing size of each files - Fixed the problem

[twdev] Re: Tiddloid - A new android editor is to be released

A new version (1.4.0) is coming. Go to the GitHub Release page to get the testing packages. *Update details:* - Main activity and splash now supports landscape mode - Now showing size of each files - Fixed the problem that

[twdev] Re: Migrating to GitHub discussions

Strongly agree, I use Github alot, and use tiddlywiki google group sometimes, and rarely come to tiddlywikidev for a time. 在2020年12月12日星期六 UTC+8 上午1:26:01<@TiddlyTweeter> 写道： > Ciao Jeremy > > Good idea. (1) GG is becoming a big pain to use. Especially if you need to > add code blocks or edit

[twdev] Re: Awesome Starred Tiddlywiki Tools

I discuss alot with bourgeoa about store tw content to solid last year, and I finally choose Github as my BaaS instead of choosing SoLiD. Glad to see bourgeoa is still carry this on. 在2021年4月15日星期四 UTC+8 下午3:36:47 写道： > Also see > >

[twdev] Re: Awesome Starred Tiddlywiki Tools

Look here Tiddlywiki in the Pod Store https://solidproject.org/apps Best wishes Mohammad On Thu, Apr 15, 2021 at 12:06 PM Mohammad Rahmani < mohammad.rahm...@gmail.com> wrote: > Also see > > Tiddlywiki SyncAdaptorModules for node-solid-server > https://github.com/bourgeoa/solid-file-widget >

[twdev] Re: Awesome Starred Tiddlywiki Tools

Also see Tiddlywiki SyncAdaptorModules for node-solid-server https://github.com/bourgeoa/solid-file-widget Store your Tiddlywiki in a Pod! Awesome! Best wishes Mohammad On Thu, Apr 15, 2021 at 12:00 PM Mohammad Rahmani < mohammad.rahm...@gmail.com> wrote: > I came over the

[twdev] Re: New backend for TiddlyWiki5 based on Firebase

Hi Peter The zero response you're getting is probably because this group has been replaced; TW dev discussions are held at https://github.com/Jermolene/TiddlyWiki5/discussions Your project looks interesting and you've certainly made an impressive presentation! Forgive me for asking the stupid

[twdev] Re: Node: Tiddler corrupted with full linux path

Saq and Chris, Apologies for the slow reply, and Saq really appreciate your quick response to my original inquiry. I think you have nailed it, *the issue seems to be the multi-line fields*. It seems tiddlers with line breaks in a field were being converted to json and/or corrupted. Not

[twdev] Re: Migrating to GitHub discussions

Ciao Jeremy Good idea. (1) GG is becoming a big pain to use. Especially if you need to add code blocks or edit messages. (2) Github style Discussion IS approachable even if you are not a dev. Best wishes TT On Thursday, 10 December 2020 at 16:18:54 UTC+1 Jeremy Ruston wrote: > We are

[twdev] Re: Custom markup (continued 4)

Hi Folks, We continue at: https://github.com/wikilabs/plugins/discussions/56 have fun! mario -- 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 email to

[twdev] Re: Custom markup (continued 4)

TonyM Thanks for the codes & ranges! TT On Thursday, 10 December 2020 at 23:50:33 UTC+1 TonyM wrote: > TT, > > Here is a summary of the existing glyphs > I established this with this site https://unicode-table.com/en/ > > Latin-1 Supplement › Acute Accent > ´ tick > ´ Acute Accent > U+00B4 > >

[twdev] Re: Custom markup (continued 4)

TonyM wrote: > Here is a summary of the existing glyphs > I established this with this site https://unicode-table.com/en/ > Just FYI I use the program BabelMap on Win to investigate Unicode Font Support. Excellent program that has no registry

[twdev] Re: Custom markup (continued 4)

TT, Here is a summary of the existing glyphs I established this with this site https://unicode-table.com/en/ Latin-1 Supplement › Acute Accent ´ tick ´ Acute Accent U+00B4 Latin-1 Supplement › Degree Sign ° ° Degree Sign U+00B0 Small Form Variants › Small Left Parenthesis ﹙ ﹙ Small Left

[twdev] Re: Custom markup (continued 4)

*Problems Of Working In The Dark* One of the biggest issues I have had is getting a CONSISTENT approach to both determining "Candidate Markup Glyphs" AND sharing them. I mean, before we go too far, would it not be a good idea to identify by U+0023 numbers what we are talking about? Both for

[twdev] Re: Custom markup (continued 4)

*Candidate Source Font(s)* I been doing testing with the Google NOTO SANS font (sets) to see what the coverage is like... Up points ... --- The Licensing is permissive and would allow extraction of glyphs to a new font. --- The *Unicode coverage is very good *(the aim of Noto is to eventually

[twdev] Re: Custom markup (continued 4)

*Note on KATEX plugin* Tony's explore of Katex is useful! Tx! Studying it: it holds several fonts. WE don't need that complexity. Rather, i think what we need is just *one *"Regular" font. What impressed ME studying Katex is it totally clarifies HOW to embed a font in TW. Jeremy provides a

[twdev] Re: Custom markup (continued 4)

*Note On Custom Embedded Font* Frankly I think that ultimately a custom (very small) font of ONLY markup glyphs is the BEST solution. TonyM has shown that much of the time the normal font cascade on Windows will usually (but not determinately) work. However there are additional issues even

[twdev] Re: Custom markup (continued 4)

Ciao TonyM & PMario Sorry for my absence. I'm ill and not achieved yet what I was aiming it. That said, I have followed the discussion and done a bunch of background research which I will comment on next. TT, x -- You received this message because you are subscribed to the Google Groups

[twdev] Re: Custom markup (continued 4)

Mario, Perhaps I should have emphasised obtain or build our own WOFF file for a last resort font. In the Katex plugin the $:/plugins/tiddlywiki/katex/fonts/KaTeX_Math-Italic.woff

Re: [twdev] Re: How to navigate to ids within a tiddler? Or How to add refresh between two steps of a widget

Hi! uplight-dev posted a nice way to catch anchor links in story.js, and ids can easily added in heading.js , so the problem I guess, as

[twdev] Re: Custom markup (continued 4)

On Wednesday, December 9, 2020 at 4:58:35 AM UTC+1 TonyM wrote: Many of the additional characters for maths is available inside the Katex > plugin with the use of Woff files, this plugin is less than 1mb in size. > If a font is about 1 MByte I'd add it to my PC, but in now way I would want to

[twdev] Re: Custom markup (continued 4)

Observation, Many of the additional characters for maths is available inside the Katex plugin with the use of Woff files, this plugin is less than 1mb in size. *The Web Open Font Format (WOFF) is a font format for use in web

[twdev] Re: Node: Tiddler corrupted with full linux path

The original description of the problem reminds me of what happens if you have non .tid format files in the tiddler directory. @clutterstack do note that the multiline fields issue is now patched in the latest pre-release. Cheers, Saq On Tuesday, December 8, 2020 at 4:19:02 PM UTC+1

[twdev] Re: Node: Tiddler corrupted with full linux path

Hi Phil, if you're still here..following on from Saq's response, do you have any custom fields containing multiple lines of text? There was an issue with this in 5.1.22 running on node. Saq wrote a patch to fix it. See this thread for more

[twdev] Re: Peer Review please Cheat sheet

Hi Tony, Just seeing this now. I suspect that if I'd had this as a reference in the summer, collecting so many gotchas in one place, it would have saved me a lot of time thinking in circles. Thanks for sharing it! Best, Chris On Wednesday, September 30, 2020 at 10:17:43 PM UTC-4 TonyM wrote:

[twdev] Re: Peer Review please Cheat sheet

@Tones *Just as {{||template}} is not supported as a widget attribute, > {{{filter||template}}} is not supported for filtered attributes. * > > I am not so sure about this statement. I understood the template > pre-processes the result then delivers the value(s) to the attribute. I > will look

[twdev] Re: Peer Review please Cheat sheet

Saq, As you are aware the wikification process is linked to the render process. I am trying to keep this issue focused and fix the gap I have highlighted. The term I try and use is "evaluate", basically to resolve a value from the wikitext elements and use it in logic and other tests, ideally

[twdev] Re: Peer Review please Cheat sheet

@Tones wiki syntax for transclusions, and syntax for indirect and filtered attributes for widgets, are two entirely different things and changing them would not be backwards compatible. Refer to this thread that explains the same difference but with regards to double brace transclusions and

[twdev] Re: Peer Review please Cheat sheet

Saq, In effect are you a saying in the latter the reference to the value is the result rather than the value?, I understand the complexities here (I think) however I expect 99% of users - Do not understand this distinction - Think the value is returned, and expects it in filter logic

[twdev] Re: Peer Review please Cheat sheet

An important distinction to make is that between filtered transclusions in wikitext, and filtered attributes for widgets. In the former, the {{{ filter || template }}} format is supported because the output gets wikified. In the latter, this is not supported as the literal value of the filter

[twdev] Re: Peer Review please Cheat sheet

codaCoda, I have updated the content of "&" to return text only <$text text={{{ [all[current]split[ ]] +[join[]] }}}/> *Important guidance* is - the "filter" given to the transclusion needs each value to be treated as a title hence - $:/string/ [] / [{!!fieldname}] [[/suffix/]]

[twdev] Re: Peer Review please Cheat sheet

Tony - Looks good on a first pass... I'll need to look at it properly tomorrow (it's late here). On Wednesday, December 2, 2020 at 6:59:28 PM UTC-6 TonyM wrote: > And using codaCodas examples prior; > > <$wikify name=style-value text="""color: {{!!color}}"""> > style=<> > > > Check this

[twdev] Re: Peer Review please Cheat sheet

And using codaCodas examples prior; <$wikify name=style-value text="""color: {{!!color}}"""> style=<> Check this in devtools Check this in devtools Again great for attribute values and parameters, but still need another step to get the result into a filter. Tony Tones On Thursday,

[twdev] Re: Peer Review please Cheat sheet

Saq et al, Thinking a little further on this issue of "inline concatenation of various tiddlywiki values", I believe I have just found a quite elegant solution. Given your complaint about Wikification performance this returns the "evaluated text" Create a tiddler called "&" for concatenate

[twdev] Re: Peer Review please Cheat sheet

@codacoder There are issues on github discussing both approaches, using backticks to wikify OR using them to do substitution. I strongly prefer the latter due to the performance penalty associated with wikify. See - https://github.com/Jermolene/TiddlyWiki5/issues/5121 -

[twdev] Re: Peer Review please Cheat sheet

Just dreaming out loud... my span Note - *backticks*. They become a request for wikification. Of course, they could be any sensible alternative (though I don't support treading on/overloading quotes, either ' or " . And if a substitution run could happen *first*... >:{{!!field}}`>my span

[twdev] Re: Peer Review please Cheat sheet

Yep, it is interesting. I do try to avoid wikify until I prove it's the only way. In essence, even though the goal is simply stated, transclusion-filters (to me) seem to cloud the simplicity - leaving a lot of syntax noise behind. Wikify seems to read simpler, because it's "broken down" I

[twdev] Re: Peer Review please Cheat sheet

@codacoder interesting! While both syntaxes leave a lot to be desired, I personally find wikify so much uglier. Personally I use a filter that does something like this: Check this in devtools Anyway be warned that depending on the complexity of the contents of the element you assign a

[twdev] Re: Peer Review please Cheat sheet

On Wednesday, December 2, 2020 at 12:40:17 AM UTC-6 saq wrote: > FYI, the solution using join[] (or addsuffix[]) is *substantially* > faster... addsuffix - duh! - Jeez... thanks for the face-palm, Saq! There's only so long I can stare at something (sometimes, anyway). -- You received this

[twdev] Re: Peer Review please Cheat sheet

Yes. But following along with your thinking was kinda slow. I had to reread a few times to "get" what you were saying. It was probably me - too tired at the time. On Tuesday, December 1, 2020 at 11:11:15 PM UTC-6 TonyM wrote: > CodaCoda, > > Yes I understand that, but I will review the cheat

[twdev] Re: Peer Review please Cheat sheet

Agreed. But syntax noise is... well, noisy :/ On Wednesday, December 2, 2020 at 12:40:17 AM UTC-6 saq.i...@gmail.com wrote: > FYI, the solution using join[] (or addsuffix[]) is *substantially* faster > than using wikify to assign widget attributes. > > You: > > <$wikify name=style-value

[twdev] Re: Peer Review please Cheat sheet

FYI, the solution using join[] (or addsuffix[]) is *substantially* faster than using wikify to assign widget attributes. You: <$wikify name=style-value text="""color: {{!!color}}"""> style=<> Me: Check this in devtools -- You received this message because you are subscribed to the

[twdev] Re: Node: Tiddler corrupted with full linux path

Are you running the latest code from Git or version 5.1.22 from npm? On Monday, November 30, 2020 at 9:10:46 PM UTC+1 phil...@gmail.com wrote: > Hi All, > > After uploading a bunch of Tiddlers to a local server in my home and > running TW, the TW on the server thinks some existing tiddlers

[twdev] Re: Custom markup (continued 4)

Sorry Wrong link in my reply, part of my development. See https://www.unicode.org/Public/UCD/latest/ucd/BidiBrackets.txt for open and close pairs. Tony On Wednesday, 2 December 2020 at 16:26:45 UTC+11 TonyM wrote: > *TT, et al* > > Yes lets start "* Unicode and Font Support in TW* " thread,

[twdev] Re: Custom markup (continued 4)

*TT, et al* Yes lets start "* Unicode and Font Support in TW* " thread, however I was keen to make it easier for us to finalise on our glyphs to support closing that issue., thus relevant to this thread. This may be a possibility to build our own targeted font, but its looking to me like most

[twdev] Re: Peer Review please Cheat sheet

CodaCoda, Yes I understand that, but I will review the cheat sheet to see if I give it sufficient weight. Did you look at the online version https://anthonymuscio.github.io/#Standard%20Nomenclature the filtered transclusions section could promote its use more. Tony On Wednesday, 2 December

[twdev] Re: Peer Review please Cheat sheet

Hi Tony Bold effort! I spotted something in there that I do quite often, but I do it a little differently: You: <$wikify name=style-value text="""color: {{!!color}}"""> style=<> Me: Check this in devtools Not sure which you might prefer... On Thursday, October 1, 2020 at 8:13:01

[twdev] Re: Custom markup (continued 4)

On Tuesday, December 1, 2020 at 6:42:53 PM UTC+1 @TiddlyTweeter wrote: *...* It would be *a very minimal font embedded in TW for JUST markup > glyphs. It would be kilobytes, not megabytes*. To get to the point of > proof-of-concept I need some days yet, but I'm getting close. Its just > trudge

[twdev] Re: Custom markup (continued 4)

Ciao TonyM & PMario TonyM wrote: > Here is my initial draft Glyphs 5.1.23-prerelease — Identifying reliable > Unicode Glyphs on TiddlyWiki Build Date (anthonymuscio.github.io) > > *TonyM*: That demo shows the issues arising over font

[twdev] Re: Custom markup (continued 4)

> > On Thursday, November 26, 2020 at 11:17:50 AM UTC+1 @TiddlyTweeter wrote: > >> *BUG? v.0.8.1 -- Block Nesting Broken?* >> > On Sunday, 29 November 2020 at 14:16:34 UTC+1 PMario wrote: > See _mode=block !! > RIGHT! I AM an idiot! Thanks for your patience. That admitted, I do think the

[twdev] Re: Custom markup (continued 4)

https://wikilabs.github.io/editions/custom-markup/#Global%20Pragma%20Definitions Perfect. Thanks, Mario. On Sunday, November 29, 2020 at 7:55:01 AM UTC-6 PMario wrote: > On Saturday, November 28, 2020 at 6:44:01 PM UTC+1 > codacoder...@outlook.com wrote: > > *Scoping rules* >> What is the

[twdev] Re: Custom markup (continued 4)

On Saturday, November 28, 2020 at 6:44:01 PM UTC+1 codacoder...@outlook.com wrote: *Scoping rules* > What is the scope of \somepragma? Is it possible to globally define them > easily? I feel like I'm missing something obvious here. Wondering if > $:/tags/Macro might do the job - it shouldn't

[twdev] Re: Custom markup (continued 4)

On Sunday, November 29, 2020 at 2:13:53 AM UTC+1 TonyM wrote: > CodaCode > > Nice to see someone else buying into the vision. > +1 > > *Scoping rules* >> What is the scope of \somepragma? Is it possible to globally define them >> easily? I feel like I'm missing something obvious here.

[twdev] Re: Custom markup (continued 4)

On Thursday, November 26, 2020 at 11:17:50 AM UTC+1 @TiddlyTweeter wrote: > *BUG? v.0.8.1 -- Block Nesting Broken?* > Try: \\ CUSTOM POETRY \\ -- container - \customize angle=POEM _element="div" _endString="/POEM" _mode=block _classes=".poem-c" \\ -- components --- \\ \customize

[twdev] Re: Custom markup (continued 4)

TonyM I looked more closely at the macro that constructs the Unicode charts you made from: https://anthonymuscio.github.io/PreReleaseGlyphs.html#New%20Tiddler Man, that is brilliant! Beyond its immediate use for our explore, it could be used well to illustrate in some docs how to solve a

[twdev] Re: Custom markup (continued 4)

codacoder...@outlook.com wrote: > Wow - I mean just WOW! I just spent I-don't-know-how-long reading all > this stuff - yes, ALL four threads My own sense is that what PMario initiated is very significant in potentiating/expanding WikiText to become a proper full-html/css methodology that

[twdev] Re: Custom markup (continued 4)

CodaCode Nice to see someone else buying into the vision. *Scoping rules* > What is the scope of \somepragma? Is it possible to globally define them > easily? I feel like I'm missing something obvious here. Wondering if > $:/tags/Macro might do the job - it shouldn't but I'd understand if it

[twdev] Re: Custom markup (continued 4)

On Saturday, November 28, 2020 at 11:44:01 AM UTC-6 coda coder wrote: > > Joshua - your guidance and background on unicode codepoints and the > potential disconnect with font support is second to none. Excellent > diligence! > > Face-palm - JOSIAH. Blame post-thanksgiving brainfog and a new

[twdev] Re: Custom markup (continued 4)

Wow - I mean just WOW! I just spent I-don't-know-how-long reading all this stuff - yes, ALL four threads (I managed to resist hunting down any off shoots to the main forum but if there's anything over there I SHOULD read, please let me know!) Joshua - your guidance and background on unicode

[twdev] Re: Custom markup (continued 4)

Ciao TonyM TonyM wrote ... > > Here is my initial draft Glyphs 5.1.23-prerelease — Identifying reliable > Unicode Glyphs on TiddlyWiki Build Date (anthonymuscio.github.io) > > * Very good! *Hots off. Definite step in the right

[twdev] Re: Custom markup (continued 4)

TonyM wrote: > This article lists glyphs supported by an intersection of a set of fonts > . > > Perhaps we could take this list and present it in a tiddler, in a large > font size and put it out to the user

[twdev] Re: Custom markup (continued 4)

TT, This article lists glyphs supported by an intersection of a set of fonts . Perhaps we could take this list and present it in a tiddler, in a large font size and put it out to the user forum for people

[twdev] Re: Custom markup (continued 4)

Ciao TonyM TonyM wrote: > The thing I find frustrating is fonts seem not to document the "code > pages" they include. There must be Unicode rich ones available for linux > and apple and other devices as there is for Windows. > I agree. *Frustrating* is the word. It is one of those areas of

[twdev] Re: Custom markup (continued 4)

TonyM wrote: > It would be interesting to look at a selective font, as a last resort, > that we could embed in tiddlywiki with only the symbols we need. I have > seen font builders around but it remains a bit of a dark art to me. Most > users such as myself have most of the Unicode covered (as

[twdev] Re: Custom markup (continued 4)

TT, It would be interesting to look at a selective font, as a last resort, that we could embed in tiddlywiki with only the symbols we need. I have seen font builders around but it remains a bit of a dark art to me. Most users such as myself have most of the Unicode covered (as I use Windows

[twdev] Re: Custom markup (continued 4)

*Font-ish Thoughts ... * Ciao TonyM & PMario TonyM wrote: > What I did discover is the following > > includes > the letter symbols  -  and other sets. Some of which will show a color > icon with

[twdev] Re: Custom markup (continued 4)

*BUG? v.0.8.1 -- Block Nesting Broken?* Ciao PMario Below is example that fails to render nested elements. Code first. Render second. Normal WikiText also fails within the scope of the "POEM" div. Failed part of example render in RED. Best wishes TT --- CODE - \\ CUSTOM POETRY \\ \\ --

[twdev] Re: Custom markup (continued 4)

Gentlemen, Sometimes one can fall into a Unicode rabbit hole. Here however I present a few desirable forms, for which we should consider if their font support is robust. Using this link one can see a set of brackets. https://keyboard.cool/db/search?q=bracket To me some share a likeness to

[twdev] Re: Custom markup (continued 4)

*"Braille" Has Advantage It is SINGLE Characters With Wide Font Support * PMario ⠒ braille⠶ ... I did play around with "braille" a little bit and for me it is _not_ visible enough in plain text. ... So I'm inclined to remove it for the initial (beta) release. ... The INLINE "⠒ braille⠶ " pair

[twdev] Re: Custom markup (continued 4)

*Goodbye ﹙ little﹚, Hello Font Supported Unicode* PMario ... "little" causes unicode problems. ... I'd like to remove it. I agree. (1) because of Unicode support; (2) because it is visually ambiguous. However , worth noting,Tony's push for it can be addressed by other types of bracket IF

[twdev] Re: Custom markup (continued 4)

PMario wrote The advanced usecase of the plugin is difficult enough to explain. Right. And the *ordinary* usecase needs time too. FWIW, after a week away from Custom Markup I had to relearn it. We really need a "crib sheet"--a one tiddler complete overview--I think, eventually. I would be

[twdev] Re: Custom markup (continued 4)

TonyM wrote: > A quick look for "safe Unicode characters" gave me this > https://qntm.org/safe > I don't pretend to understand it fully but perhaps TT does. > Ciao TonyM. It is interesting and matches my understanding. Its actually reads more "scary" that we need. Most of the mentioned

[twdev] Re: Custom markup (continued 4)

*The Problem With _Underscore_* PMario... I do like "underscore" because it's easy to see in plain text, but it needs more internal code :/. Hi Mario. In previous posts I have tried to show, with examples, why I think underscore is NOT a good idea. Basically, IF it were not already used in

[twdev] Re: Custom markup (continued 4)

PMario wrote: > > My main point is, that I don't what to deal with the unicode support > problems. The advanced usecase of the plugin is difficult enough to > explain. > Right. In any case the DEFAULT glyphs in the standard plugin I hope are finite in number and (pretty sure to be) in fonts

[twdev] Re: Custom markup (continued 4)

Mario, I understand your concern in relationship to Unicode. But given TiddlyWiki has the content type; And most systems have fonts for symbols, beyond the old ASCII sets I am sure we can find safe Unicode characters. TT may be the best to provide guidance here. - The dream would be

[twdev] Re: Custom markup (continued 4)

Sorry for the late reply. ... I Wasn't aware, that I can only see, if something is going on, if I change the group :/ On Wednesday, November 18, 2020 at 11:48:23 PM UTC+1 TonyM wrote: ... > So perhaps we now need to ask > >- How do we go about a degree of rationalisation >- code pages

[twdev] Re: Custom markup (continued 4)

Ciao TonyM - Determine if Unicode is present in a given wiki (higher Unicode character search?) Tech point. To use regular expressions for higher Unicode (it would go through JS) in TW is simplest if one uses single Unicode code points in RANGES. JS regex ranges for Unicode are

[twdev] Re: Custom markup (continued 4)

TT, I was thinking on this matter of unicode support, which could have consequences both for and in the use of custom wikitext. In many ways tiddlywiki "supports" Unicode, however for example no Unicode is usable in fieldnames, yet it is in titles, text and field values etc... However there

[twdev] Re: Custom markup (continued 4)

Ciao Tony & PMario TonyM wrote: > > > I had not tested Android, although a big user. > I think Android matters. Though personally I never use it for heavy edit, its clear that lots of people do. It DOES raise an interesting issue of relevance to PMario too. I think it got clear through the 4

[twdev] Re: Custom markup (continued 4)

TonyM wrote: > > > determining one freely available that can ensure the lions share of > Unicode is available, this is what we must do. > Right! I been looking at various methods for doing that. I use BabelMap Portable, which is pretty good, to examine the font substitution process. It is

[twdev] Re: Warning when creating PluginLibrary in TW 5.1.23 pr

Thank you Saq! I hope Jeremy have a look and correct the issue! Mohammad On Wednesday, November 18, 2020 at 2:53:18 AM UTC+3:30 saq.i...@gmail.com wrote: > I think I have narrowed the problem down to lines 3-15 in the arabic > translation: > > >

[twdev] Re: Warning when creating PluginLibrary in TW 5.1.23 pr

I think I have narrowed the problem down to lines 3-15 in the arabic translation: https://github.com/Jermolene/TiddlyWiki5/blob/master/languages/ar-PS/ControlPanel.multids#L3 To reproduce the problem using just the core: node tiddlywiki.js editions/pluginlibrary/ --build library -- You

[twdev] Re: Warning when creating PluginLibrary in TW 5.1.23 pr

I can confirm that the problem exists. It seems to arise at this commit though I don't see anything problematic in it: https://github.com/Jermolene/TiddlyWiki5/commit/72c07a3f81233384623ed6293d7f93bdb3104db0#diff-097629654b32250326a4e5bb6faa3b4a3c2fe2a66b1eea2bbcf9c5984c72bf27 On Monday,

[twdev] Re: Warning when creating PluginLibrary in TW 5.1.23 pr

Hi Jeremy, To make sure I have downloaded the latest TW 5.1.23 again from GitHub, deleting the previous version and install the new one on my computer. The error is still there. So, it seems something going wrong with core! p.s: My test with TW 5.1.22 works fine with no warning. Best Mohammad

  1   2   3   4   5   6   7   8   9   10   >