Skip to content

Relationship with /TR/ruby #38

@frivoal

Description

@frivoal

@plehegar said in #758

2 considerations:

  1. Shouldn't the SOTD indicate that this specification is meant to deprecate the Ruby Annotations specification?
  2. You should consider what will happen to the /TR/ruby shortname when this specification moves forward, ie you may want to point it to html-ruby-extensions or something.

These are good questions. My take would be:

  1. yes
  2. once this spec is sufficiently mature, /TR/ruby should be formally superseded if favor of this document.

If the WG agrees, I'll updated the SOTD accordingly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs: FeedbackThis issue needs more people to weigh in to make progress.Tests: UnneededThis closed issue does not need tests.Topic: Ruby Markup specRelates to https://www.w3.org/TR/html-ruby-extensions/Type: EditorialTypos, markup errors, rephrasings or reorganizations with no normative effects (class 1 or 2)i18n-trackerGroup bringing to attention of Internationalization, or tracked by i18n but not needing response.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions