[postgis-devel] postgis_letters in project tree?

Bruce Rindahl bruce.rindahl at gmail.com
Thu Jan 27 15:47:27 PST 2022


Nice!  Very clever way to implement kerning

On Thu, Jan 27, 2022 at 3:40 PM Paul Ramsey <pramsey at cleverelephant.ca>
wrote:

> Added some extra magic to tighten up the kerning to pack short letters
> tighter under tall narrow letters like T and Y. OK, I'll stop now!
>
>
>
> On Jan 27, 2022, at 2:45 PM, Paul Ramsey <pramsey at cleverelephant.ca>
> wrote:
>
> Challenge accepted, all just one function.
>
> https://gist.github.com/pramsey/2020ef463a8880edc7e23c56420d7df8
>
> On Jan 27, 2022, at 2:08 PM, Darafei Komяpa Praliaskouski <me at komzpa.net>
> wrote:
>
> I like this way. Believe we only need one function really.
>
> (I called this ST_GeomFromText in my head for a bit...)
>
> пт, 28 сту 2022, 00:38 карыстальнік Paul Ramsey <pramsey at cleverelephant.ca>
> напісаў:
> Here's the two functions. I think putting these into the default postgis
> extension makes sense, they are small and then we have letter
> magic available for doco etc wherever we want.
>
> https://gist.github.com/pramsey/2020ef463a8880edc7e23c56420d7df8
>
> P
>
> On Jan 27, 2022, at 10:32 AM, Paul Ramsey <pramsey at cleverelephant.ca>
> wrote:
>
> Using base64 encoded twkb, i can get the letters set down to a 22K
> function. So, I think maybe this just goes into the main postgis extension.
> (Assuming you're OK with my minimalist anglo no-special-font handling
> approach.)
>
> On Jan 27, 2022, at 9:29 AM, Martin Davis <mtnclimb at gmail.com> wrote:
>
>
> On Thu, Jan 27, 2022 at 9:03 AM Paul Ramsey <pramsey at cleverelephant.ca>
> wrote:
> I'm thinking of converting the letter/font table into a function with a
> fixed collection of letters, so that an install involves just two
> functions ST_GeomFromLetter(letter) and ST_GeomFromWord(text).
> ST_GeomFromLetter can be expanded over time to include additional letters
> for other language charsets. That matches the capabilities of the system to
> the needs.
>
> That sounds like the simplest approach.  Nice to avoid needing a table.
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
>
>
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
>
>
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20220127/3883caa8/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: screenshot_810.png
Type: image/png
Size: 44417 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20220127/3883caa8/attachment-0001.png>


More information about the postgis-devel mailing list