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

Extended unicode identifiers propossal #63

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

miguelh-nvidia
Copy link
Contributor

@miguelh-nvidia miguelh-nvidia commented May 22, 2024

Description of Proposal

UTF-8 identifiers adhere to Unicode XID and as such, some identifiers are still invalid, in particular identifiers with leading digits and medial hyphens (i.e. -).

This type of identifiers are consistently used in different areas like manufacturing and it is important to have a direct one-to-one mapping between the virtual representation and the real world.

In this proposal we address their inclusion in OpenUSD.

Link to Rendered Proposal

Contributing

@asluk
Copy link

asluk commented May 30, 2024

let's a add a link to the rendered proposal to the PR description - https://github.com/NVIDIA-Omniverse/USD-proposals/tree/extended_unicode_identifiers/proposals/extended_unicode_identifiers 👍🏼

@dgovil
Copy link
Contributor

dgovil commented Jul 3, 2024

The idea of a medial hyphen would also be greatly useful to us, especially with regards to the language schema proposal.
I'd also advocate for this + the variant set metadata proposals because they have a material impact on our AOUSD spec. I think they'd be very good to get into the first version of the spec so that we don't need to rev the spec so soon after it would be out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Draft
Development

Successfully merging this pull request may close these issues.

4 participants