LiveCode Forums.

I would like the ability to both superscript and subscript text without resizing the individual glyphs,
and the ability to set individual character sizes.

Manual kerning!

This is manual kerning in the sK1 project, and were it implemented in Livecode that
would be a great strength for anybody who wanted to work with text.

From a purely personal point of view I would like manual kerning to implement
a system to digitise Grantha script [a script used for many languages throughout southern India].
This image shows a subscripted character that is both below the "parent" glyph" and size reduced.
Grantha can 'stack' glyphs up to 3 deep.

Something other than this?

Something other than this?

Flipping amazing . . .

AND, why is this SO under-documented / publicised that . . . ?

AND . . . how will one line a glyph up directly underneath another glyph? Is that "one step beyond"?

Use the textShift property to subscript and superscript chunks of text in a field.

That's wonderful, BUT what I am now looking for is not JUST shifting up and down, but also back and forwards.

Refer back to my image of Grantha script and look at the subpercscripted glyph that is tucked underneath another glyph;
this would involve not just a textShift command for up and down, but also one for left and right (?) so that an individual glyph can be either
displaced, or involve no "carriage advance" when it is input into a field.

I very much doubt if one could leverage textDirection to achieve this.

Ultimately textShift and textSize are only of any real value locally [i.e. inwith Livecode]
as export does all sorts of things which renders the results effectively useless:
RTF export
HTML export

richmond62 wrote:why is this SO under-documented / publicised that . . . ?

What would constitute adequate documentation on this in your view?

What would constitute adequate documentation on this in your view?

I do feel that a different type of documentation could be developed; possibly with chapter headings.

Let us imagine a chapter entitled; "Everything to do with Text".

This would then have subheadings such as:

1. Aligning text.

2. Kerning text.

and so on.

Currently the only "way" into the documentation is via terms, and if one doesn't know
Livecode's terms that can be slow and painful at best.

For the sake of argument, I wonder what would make someone who wanted to check out manual kerning
in Livecode think "textShift" out of nowhere. That would just not happen.

I rather doubt we'll get adequate kerning support any time in the near future. I'm rather too ignorant of the internals for font mechanics to contribute anything useful to the conversation. I know there is a way of using font hints when they're supported and available, but I'm afraid it would take a lot of work to get that to a useful state.

Textshift has been around for a long time and hasn't changed. And yes, it's one of those gems that's hidden down in the deeps of the documentation. Granted it's of limited usefulness (no sub-pixel placement, etc) but it's quite a handy tool to have available.

I *do* like that thematic documentation idea, and it seems that the new docs are getting to a stage where something like that can happen.

...and I rather like the unexpected html export, even though it may not be what's desired.

unexpected html export

"unexpected" ? How come?

richmond62 wrote:Currently the only "way" into the documentation is via terms, and if one doesn't know
Livecode's terms that can be slow and painful at best.

The Dictionary is not the only documentation available for LiveCode. Though I agree it may be helpful to see more cross-referencing within it - you're welcome to add some:
https://livecode.com/putting-the-you-in-documentation/

The User Guide, Lessons, and other Guides are joining the Dictionary content in being translated to Markdown on Github. Most of them are already there. There are many benefits to this, not the least of which is allowing you to add more See Also links in Dictionary entries.

Another thing that can be done with the new modular documentation content is that it's becoming possible for anyone to link any portions of it to curate specialized task-specific guides.

For example, if you wanted a guide to "Everything you can do with text" you can write a Markdown document with a little introductory text, and then link to the relevant portions of the User Guide to get folks oriented, followed by any Lessons that may be relevant, then any Dictionary entries you feel should be there.

The range of documentation options for LiveCode have never been broader. All that's needed now is anyone sufficiently motivated to assemble them into anything they want.

"unexpected" in the sense of different size characters.

But also unexpected in that the different sized letters don't directly correspond to those in the originating
text field in Livecode.

This is NO GOOD as far as exporting results goes.