Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider adding a generalized transformation directive #147

Open
tzlaine opened this issue Mar 1, 2024 · 1 comment
Open

Consider adding a generalized transformation directive #147

tzlaine opened this issue Mar 1, 2024 · 1 comment

Comments

@tzlaine
Copy link
Collaborator

tzlaine commented Mar 1, 2024

From #119:

Maybe something for the future: there's a lot of effort in the code to get no_case working, and in
the end it's all about applying case folding. What about having a transformation-directive letting
users plug-in their own transformations for input and target:

transform( _input_transformation_ )[ parser ]
transform( _input_transformation_, _target_transformation_ )[ parser ]

@tzlaine
Copy link
Collaborator Author

tzlaine commented Mar 5, 2024

This is very low priority. I like the idea, but it's currently searching for a use case. I'm leaving it open so that 1) it is not forgotten, and 2) others who do have a use case for this might stumble upon it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant