Open webbedspace opened 2 years ago
One potential issue is that currently a Markup based link is the only means (1) available for generating a Connection between two Passage.
...even though there's no real onus on every story format to support it
Other that the fact that story format developers likely understand that many (most) Authors use the GUI application so they have access to a Passage Map, instead of a Text Editor plus TWEE Compiler,
(1) Other than embedding the Markup link within a comment, and relying on the fact that currently the application doesn't exclude the content of comments in its searching for "links".
Disagree a bit, because double brackets are the one lingua franca among story formats. @webbedspace, I know you're in favor of allowing story formats to replace Twine's link parser completely (I think you raised this originally in #942) but I think right now the negatives of that outweigh the positives.
I think there's no harm in allowing story formats to set their own placeholder text, though this means shifting the burden of localization onto them. Something along the lines of a placeholder: (language: string) => string
property, where language
is a locale code.
The problem here is that it lists a single syntax feature (simple links) even though there's no real onus on every story format to support it. As such, it's liable to be flat-out incorrect.
Possibly you could allow story formats to specify their own placeholder string (which is what I'd been doing for Harlowe 3.2 anyway). At worst, you could just remove the second sentence.
Presubmission checklist