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

Do ldpl identifiers (or sentence words) support uf8? #190

Closed
arielf212 opened this issue Jul 10, 2020 · 5 comments
Closed

Do ldpl identifiers (or sentence words) support uf8? #190

arielf212 opened this issue Jul 10, 2020 · 5 comments

Comments

@arielf212
Copy link
Contributor

This is more of a question than an issue, but does ldpl support utf8 or is it an ascii-only language?

@Lartu
Copy link
Owner

Lartu commented Jul 17, 2020

Hi there! Yes, they should without a problem. I will check to make sure though...

@Lartu
Copy link
Owner

Lartu commented Jul 17, 2020

data:
המבורגר is number
バーガー is number

procedure:
store 20 in המבורגר
store 30 in バーガー
display המבורגר " + " バーガー " = " 
add バーガー and המבורגר in המבורגר
display המבורגר "!" lf

Works perfectly!

@arielf212
Copy link
Contributor Author

arielf212 commented Jul 17, 2020

I should have probably asked this question a bit differently: is an alternative implementation of ldpl expected to accept case insensitive utf8 identifiers?

The problem is not specifically the utf8 identifiers, but the fact that lower/upper casing utf8 is kinda hard (or, at least, much harder than ascii).

@Lartu
Copy link
Owner

Lartu commented Jul 19, 2020

Ahh, I get it. You know, this is something that never crossed my mind 🤔 We are using the http:https://www.cplusplus.com/reference/cctype/toupper/ function to transform the source code to uppercase, so I don't believe ááá is the same variable as ÁÁÁ. So I guess no, that's not expected. I should add that to the documentation, thank you!

@Lartu
Copy link
Owner

Lartu commented Jul 24, 2020

I will be closing this issue now. Feel free to reopen it if you need.

@Lartu Lartu closed this as completed Jul 24, 2020
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

2 participants