-
Notifications
You must be signed in to change notification settings - Fork 5
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
Phrase about edition superseding #1103
Comments
Is the phrase more generally "This n-th edition supersedes the n-1-th edition"? I'd have to assume so... |
@opoudjis yes, sure. |
For Russian, this will become the very first time we will have had to allow for case inflection in i18n (we will need both nominative and accusative). I will need to work out whether I hard code casing in i18n processing, or build a metalanguage like Fluent (if not Fluent itself) into the template. But unless we do a lot more Russian than we have been doing, that would be overengineering. If it's Настоящее второе издание заменяет первое издание, then I see "edition" is neuter, with the same inflection for nominative and accusative, so in this one instance, I would not need to build case inflection. But that's a happy accident, and I want to be safe... |
Again, while this solution is overkill for this instance ("edition" in Russian is neuter, so it's the same in the nominative and accusative), I'm using this as an opportunity to refactor i18n. The current uninflected (so nominative) i18n templates for "first edition" and "1st EDITION" in Russian are:
%Spellout and %Ordinal are special variables, to be populated from metadata, and formatted according to the word after %, and twitter-cldr-rb. We have variables in general in our YAML, indicated by %, %1, %2, etc. We now need to introduce case inflection on variables, and on words that already occur in our i18n. Fluent https://projectfluent.org/fluent/guide/terms.html would express the case for "This n-th edition supersedes the n-1-th edition" as:
Fluent... as I said, does not actually do that much, other than passing attributes into the i18n word lookup. We're not going to get that much out of adopting it. But it's clear that we should add the following functionality to our i18n manipulation of YAML:
With a conservative approach (allowing words to remain hard-coded if they do not vary), and allowing default values (which isodoc-i18n already knows about, given
If we unify variables and Liquid, and allow dynamic entry of word inflection, as a maximimalist solution, we end up with:
This is overkill. But if we do serious work with Russian or Arabic, we need this level of overkill; and even if we don't, we should not perpetuate ad hoc solutions to inflection. The solution I'll implement will be more conservative, and it will still make the foregoing possible:
And I will gradually or suddenly replace %, %1, %2 with {{variable1}}, {{variable2}} in i18n. |
Done:
Element will only appear if edition is > 1 and document scheme is 1951 |
Source issue: #1089
The 2nd, etc. ISO publications from 1951 to 1971 contains the sentence about superseding the previous edition.
Need to add the localized resource.
Examples:
'en' -

This second edition supersedes the first edition
'fr' -

Cette deuxième édition annule et remplace la première édition
The text was updated successfully, but these errors were encountered: