<commit_before># Liquid Support in Scriban

Scriban supports all the [core liquid syntax](https://shopify.github.io/liquid/) tags and filters, except the following known issue.

## Known issues

> NOTE: The liquid syntax has never been strictly formalized, and custom tags implementation can choose whatever syntax for their arguments.
>
> This is a known issue in liquid itself, for example:
>  - [issue 507: Custom tags: what’s the preferred method of providing arguments containing quotes](https://github.com/Shopify/liquid/issues/507)
>  - [issue 671: Using liquid class libraries inside Liquid::Tag](https://github.com/Shopify/liquid/issues/671)
>  - [issue 560: Unified syntax for tag arguments [RFC]](https://github.com/Shopify/liquid/issues/560)
>
> There is in fact multiple versions of the liquid language, supporting different syntaxes for tags.
>
> As a consequence, **the liquid parser implemented in Scriban cannot parse any custom liquid tags that are using custom arguments parsing**

## Examples

In the following sections, you will find a few examples about how scriban translates a liquid template into a scriban template. 

> NOTE: All the following examples are using the feature [**Ast to text**](runtime.md#ast-to-text) that<commit_msg>Update liquid-support to explain liquid syntax discrepancies<commit_after># Liquid Support in Scriban

Scriban supports all the [core liquid syntax](https://shopify.github.io/liquid/) tags and filters, except the following known issue.

## Known issues

> NOTE: The liquid syntax has never been strictly formalized, and custom tags implementation can choose whatever syntax for their arguments.
>
> This is a known issue in liquid itself, for example:
>  - [issue 507: Custom tags: what’s the preferred method of providing arguments containing quotes](https://github.com/Shopify/liquid/issues/507)
>  - [issue 671: Using liquid class libraries inside Liquid::Tag](https://github.com/Shopify/liquid/issues/671)
>  - [issue 560: Unified syntax for tag arguments [RFC]](https://github.com/Shopify/liquid/issues/560)
>
> For example in liquid, you usually pass arguments to tags and filters like this (supported by scriban):
>
> ```liquid
> {{ "this is a string" | function "arg1" 15 16 }}
> ```
>
> ```liquid
> {% custom_tag "arg1" 15 16 %}
> ```
>
> But some liquid tag/filter implementations may in fact choose to accept different ways of passing arguments:
>
> ```liquid
> {% avatar user=author size=24 %}
> ```
>
> There is in fact multiple versions of the liquid language, supporting different syntaxes for tags, which are completely arbitrary and not unified.
>
> As a consequence, **the liquid parser implemented in Scriban cannot parse any custom liquid tags/filters that are using custom arguments parsing**
> but only regular arguments separated by spaces.

## Examples

In the following sections, you will find a few examples about how scriban translates a liquid template into a scriban template. 

> NOTE: All the following examples are using the feature [**Ast to text**](runtime.md#ast-to-text) that
{'fraction_non_alphanumeric': 0.09120521172638436, 'fraction_numerical': 0.015635179153094463, 'mean_word_length': 4.783427495291902, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 42, 'https://': 8, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4472749', 'n_tokens_mistral': 869, 'n_tokens_neox': 781, 'n_words': 376}