Any thoughts on localization? #24

Closed
opened 3 years ago by obonac · 1 comments
obonac commented 3 years ago (Migrated from github.com)

Hi,

I am new to racket (some scheme and lisp background).

Whats the best way to localize the demos?

See https://github.com/djinn/khhota as a initial effort

Regards,
Abhishek

Hi, I am new to racket (some scheme and lisp background). Whats the best way to localize the demos? See https://github.com/djinn/khhota as a initial effort Regards, Abhishek
mbutterick commented 3 years ago (Migrated from github.com)

I don’t know anything about localization.

I suppose I would go into the lexer.rkt and translate the English-language tokens to the new language. In the case of reserved-terms, the lexer could convert the reserved term in the new language to its English equivalent before emitting a token (which would contain the original English). Thus the lexer would act as a translation layer, in effect.

By keeping the localization in one file, it would be easier to create a system where you could support multiple localizations.

But I’m just guessing. Beyond that, it would be experimentation and refinement.

I don’t know anything about localization. I suppose I would go into the `lexer.rkt` and translate the English-language tokens to the new language. In the case of `reserved-terms`, the lexer could convert the reserved term in the new language to its English equivalent before emitting a token (which would contain the original English). Thus the lexer would act as a translation layer, in effect. By keeping the localization in one file, it would be easier to create a system where you could support multiple localizations. But I’m just guessing. Beyond that, it would be experimentation and refinement.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: mbutterick/beautiful-racket#24
Loading…
There is no content yet.