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

Ambiguous for-less link for 'grapheme cluster' #1860

Closed
emlun opened this issue Mar 6, 2023 · 2 comments · Fixed by #1863
Closed

Ambiguous for-less link for 'grapheme cluster' #1860

emlun opened this issue Mar 6, 2023 · 2 comments · Fixed by #1863

Comments

@emlun
Copy link
Member

emlun commented Mar 6, 2023

New builds of the spec generate this error:

LINE ~4823: Ambiguous for-less link for 'grapheme cluster', please see <https://tabatkins.github.io/bikeshed/#ambi-for> for instructions:
Local references:
spec:utr29; type:dfn; for:/; text:grapheme cluster
for-less references:
spec:i18n-glossary; type:dfn; for:/; text:grapheme cluster
spec:i18n-glossary; type:dfn; for:/; text:grapheme cluster
[=grapheme cluster=]
LINE ~4825: Ambiguous for-less link for 'grapheme cluster', please see <https://tabatkins.github.io/bikeshed/#ambi-for> for instructions:
Local references:
spec:utr29; type:dfn; for:/; text:grapheme cluster
for-less references:
spec:i18n-glossary; type:dfn; for:/; text:grapheme cluster
spec:i18n-glossary; type:dfn; for:/; text:grapheme cluster
[=grapheme cluster=]
LINE ~4832: Ambiguous for-less link for 'grapheme cluster', please see <https://tabatkins.github.io/bikeshed/#ambi-for> for instructions:
Local references:
spec:utr29; type:dfn; for:/; text:grapheme cluster
for-less references:
spec:i18n-glossary; type:dfn; for:/; text:grapheme cluster
spec:i18n-glossary; type:dfn; for:/; text:grapheme cluster
[=grapheme cluster=]
LINE ~4834: Ambiguous for-less link for 'grapheme cluster', please see <https://tabatkins.github.io/bikeshed/#ambi-for> for instructions:
Local references:
spec:utr29; type:dfn; for:/; text:grapheme cluster
for-less references:
spec:i18n-glossary; type:dfn; for:/; text:grapheme cluster
spec:i18n-glossary; type:dfn; for:/; text:grapheme cluster
[=grapheme cluster=]

Our index.bs contains an anchor definition for [=grapheme cluster=] linking to https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries :

spec: UTR29
    urlPrefix: https://unicode.org/reports/tr29/
        type: dfn; for:/; url: Grapheme_Cluster_Boundaries; text: grapheme cluster

Apparently the i18n-glossary spec has added an exported <dfn> for [=grapheme cluster=], which now makes our reference ambiguous. The definition in i18n-glossary in turn links to a different Unicode document: http://www.unicode.org/versions/latest/ch02.pdf .

Should we move to using the definition from i18n-glossary, or disambiguate and keep using our existing reference?

@emlun
Copy link
Member Author

emlun commented Mar 8, 2023

2023-03-08 call: Probably use the i18n-glossary definition if it seems applicable enough. @emlun to compare and open a PR.

@emlun
Copy link
Member Author

emlun commented Mar 16, 2023

I'm not sure how I identified http://www.unicode.org/versions/latest/ch02.pdf as the primary further reference from i18n-glossary. At the moment, the definition reads:

Grapheme cluster. A grapheme cluster is defined by the Unicode Standard as the default mechanism for computing an approximation to graphemes (see Unicode Standard Annex #29: Text Segmentation [UAX29]). Two types of default grapheme cluster are defined. Unless otherwise noted, grapheme cluster in this document refers to an extended default grapheme cluster. (A discussion of grapheme clusters is also given in Section 2 of the Unicode Standard, [Unicode]. Cf. near the end of Section 2.11 in version 14.0 of The Unicode Standard.) Because different natural languages have different needs, grapheme clusters can also sometimes require tailoring. For example, a Slovak user might wish to treat the default pair of grapheme clusters "ch" as a single grapheme cluster. Note that the interaction between the language of string content and the end-user's preferences might be complex.

The first parenthetical links to https://www.unicode.org/reports/tr29/tr29-39.html which is an earlier revision (39) of our current link, https://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries (currently revision 41). The contents of the "Grapheme Cluster Boundaries" section looks identical between these two revisions.

Given this I judge that we can safely drop our anchor for [=grapheme cluster=] and use the definition from i18n-glossary instead.

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

Successfully merging a pull request may close this issue.

1 participant