-
Notifications
You must be signed in to change notification settings - Fork 2
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
International symbols #9
Comments
|
@HassanAkbar is this task addressed? |
@ronaldtse From what I understand currently in glossarist the symbols are in the In the concept model, the symbols are in concept base so they will be shared by all localizations (this is not implemented yet). I'm not sure about 2 and 3. Will have to look into it. |
I think for symbols there are two types: across languages and per language. There is a special type of symbol that applies internationally, ie. “international symbol” and across localizations. These are the ones like the SI system symbols “m”, “s” etc. Let’s take this concept and elaborate into 2 and 3. |
We have some provisions to do that (let me check), but I don’t think they’re necessarily the most elegant way to handle this. I think our data structure doesn’t really allow for international concept data, and this is something that should be addressed on a more fundamental level—adding this symbol to localized concept description for a particular language and indicating a symbol as “international” strikes me as a crutch. |
Please feel free to update the concept model and resulting structures to accommodate the international symbol in a clean/native way. Thanks! |
I have no idea what the integration into Metanorma will look like, and if I have my way, I'm not going to be the one to implement it anyway :-P While you can do what you want in the conceptual modelling of symbols and whatever classes are associated, I'm responsible in Metanorma for a serialisation of the concept model that is parsed grammatically, and I'm responsible for an existing (non-YAML) implementation of markup for concepts. Therefore, I am to be consulted before that changes. Although frankly, I'm not convinced the serialisation, as opposed to the underlying model, needs to change at all. |
@ronaldtse Not sure what’s to be done in this ticket. |
@ronaldtse, @opoudjis, @strogonoff I have three questions:
The text was updated successfully, but these errors were encountered: