ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Hamid,Idris" <Idris.Hamid@ColoState.EDU>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>,
	Hans Hagen <j.hagen@xs4all.nl>
Subject: [NTG-context] Re: Scaling characters without font switching in CLD
Date: Sat, 12 Aug 2023 22:56:12 +0000	[thread overview]
Message-ID: <3ff5855a-bd10-4d18-847d-8c5b214c1a0a@Spark> (raw)
In-Reply-To: <edf07a75-f79e-4f74-b9ac-01006dc3a0e5@Spark>


[-- Attachment #1.1: Type: text/plain, Size: 1580 bytes --]

On Aug 12, 2023, 4:20 PM -0600, Hans Hagen <j.hagen@xs4all.nl>, wrote:

> btw, no need for squeezine as there are virtual commands for scaling; not for rotating

From your original CLD template:

local function topthing(characters,target,base,accent)
--    if not characters[target] then
        local data1 = characters[base]
        local data2 = characters[accent]
        if data1 and data2 then
            characters[target] = { -- "Ḥ"
                height   = (data1.height or 0) + 0.5*(data2.height or 0),
                depth    = data1.depth,
                width    = data1.width,
                unicode  = target,
                commands = {
                    { "slot", 0, 0x048 },
                    { "left", 0.5*(data2.width  or 0) + 0.5*(data1.width  or 0) },
                    { "up",   0.5*(data2.height or 0) },
                    { "slot", 0, 0x2D9, },
                },
            }
        end
--    end
end

What are the virtual commands for scaling? Can they be added under "commands =" in the above? Or will that have to go under another local function?

Of course, we may still have to insert the \symbol's for rotation, so perhaps better to stick with \symbol's for scaling as well (you know best).

Now that the \symbol's for the glottals have been defined with your second template, I need to figure out where/how to plug them into the CLD based on your first template.

Best wishes
Idris
--
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523

[-- Attachment #1.2: Type: text/html, Size: 2819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 495 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2023-08-12 22:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-12 14:03 [NTG-context] " Hamid,Idris
2023-08-12 15:34 ` [NTG-context] " Hans Hagen
2023-08-12 18:05   ` Hamid,Idris
2023-08-12 20:10     ` Hans Hagen via ntg-context
2023-08-12 21:33       ` Hamid,Idris
2023-08-12 21:48         ` Hans Hagen
2023-08-12 22:11           ` Hamid,Idris
2023-08-12 22:16             ` Hamid,Idris
2023-08-12 22:56               ` Hamid,Idris [this message]
2023-08-13 12:32                 ` Hans Hagen via ntg-context

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ff5855a-bd10-4d18-847d-8c5b214c1a0a@Spark \
    --to=idris.hamid@colostate.edu \
    --cc=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).