AST and non-Latin scripts

AST and non-Latin scripts

[Lyndon Drake]

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

Quick question: does the Pandoc AST have a way of identifying the script 
for a sequence of characters? E.g. using the named Unicode ranges, perhaps 
tagged with their ISO 15924 name (similar to various HTML 
implementations: https://en.wikipedia.org/wiki/ISO_15924).

That way a writer or filter could do different things with non-Latin 
scripts.

The particular case I'm interested in is documents with mixed Latin, 
Hebrew, Greek, Syriac, cuneiform, etc., where the ability for a writer (or 
filter) to set a different document inline or paragraph style (DOCX, or 
ICML writers) or span/environment (LATEX or HTML) would make life much 
easier. Typically one wants a specific font for the script in question, or 
in LATEX using polyglossia you mark a particular environment.

For LATEX I could embed the environment commands but it's not portable to 
other output formats. And now that text editing for these scripts is so 
good, I like keeping everything in plain text without the clutter of markup.

Does that make any sense?

Cheers,
Lyndon

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a88f9304-09b6-4f8f-acea-5626ccc9e546%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: AST and non-Latin scripts

[John MacFarlane]

Except for verbatim code, all of the actual text will be
in Str elements in the AST.  So your filter can just
match on Str elements, check the string to see if it
satisfies some condition, and then do something
depending on the result -- e.g. add a raw latex
font-changing command, if the output format is
latex, or put it in a special span.

Pandoc itself doesn't provide any special functions
for unicode ranges, but you can just use whatever
functions are provided by the language in which
you're writing the filter.

Re: AST and non-Latin scripts

[John Muccigrosso]

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

On Monday, June 5, 2017 at 9:47:56 AM UTC-4, John MacFarlane wrote:
>
> Except for verbatim code, all of the actual text will be 
> in Str elements in the AST.  So your filter can just 
> match on Str elements, check the string to see if it 
> satisfies some condition, and then do something 
> depending on the result -- e.g. add a raw latex 
> font-changing command, if the output format is 
> latex, or put it in a special span. 
>
> Pandoc itself doesn't provide any special functions 
> for unicode ranges, but you can just use whatever 
> functions are provided by the language in which 
> you're writing the filter. 
>

I'm not great on the scripting, but the ability to switch fonts by language 
would be handy for me. 

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/3d6dab29-856a-49a0-9484-3b9b9b43a9de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: AST and non-Latin scripts

[Lyndon Drake]

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

I'll have a go at that. I know the unicode ranges I need so it shouldn't be 
impossible.

BTW, is there a reason the default latex template uses Babel with Xelatex? 
For this I want to use Polyglossia, and up till now I've just been able to 
put options in a YAML block, but I figure someone might have run into 
difficulty and so I'm reluctant to switch if it will cause problems.

On Monday, June 5, 2017 at 2:47:56 PM UTC+1, John MacFarlane wrote:
>
> Except for verbatim code, all of the actual text will be 
> in Str elements in the AST.  So your filter can just 
> match on Str elements, check the string to see if it 
> satisfies some condition, and then do something 
> depending on the result -- e.g. add a raw latex 
> font-changing command, if the output format is 
> latex, or put it in a special span. 
>
> Pandoc itself doesn't provide any special functions 
> for unicode ranges, but you can just use whatever 
> functions are provided by the language in which 
> you're writing the filter. 
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/08b4ef89-105b-4e88-bd37-2f81b59b552f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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