Skip to content

docs: markup feature history #401

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 3 commits into from
Jul 3, 2023
Merged

docs: markup feature history #401

merged 3 commits into from
Jul 3, 2023

Conversation

cdaringe
Copy link
Contributor

Problem

On visiting the WG, I was (am) deeply interested in ultimately ensuring the formatToParts like implementation became part of the spec. I did not understand...

  • the prior context for which all discussions on the matter had occurred in
  • what different team members meant when using the term "markup" in context of this repo
  • the state of markup support in MFv2 (i'd argue, few actually have a great grip on this, outside of a select few, having read all of the issues 😄 )

Solution

Read through the rich history of markup in the codebase. Capture,

  • each key discussion
  • interesting takeaways from the discussion
  • a "Status", representing the sentiment that I perceive that the WG wants from "markup" support

@CLAassistant
Copy link

CLAassistant commented Jun 21, 2023 •
edited
Loading

CLA assistant check
All committers have signed the CLA.

@cdaringe cdaringe mentioned this pull request Jun 21, 2023
Closed
eemeli
eemeli approved these changes Jun 21, 2023
View reviewed changes
Copy link
Collaborator

@eemeli eemeli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks pretty accurate. One small nit: In general we tend to abbreviate as "MF2" rather than "MFv2".

@cdaringe
Copy link
Contributor Author

"MF2" rather than "MFv2".

handled in 1fd3730

@cdaringe cdaringe marked this pull request as ready for review June 21, 2023 17:00
aphillips
aphillips reviewed Jun 25, 2023
View reviewed changes
docs/archive/markup-support.md Outdated
- Revisiting "can our syntax just be XML"-ish? Counter-assertion that XML-compat may be contributor bias.
- Revisiting (implicitly) formatToParts

## Apr 10
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Include the year

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3690b9b

docs/archive/markup-support.md Outdated
represent how collective sentiment or code have tangibly shifted over the
project lifetime, not to represent the perfect synopsis of an event.

## 27 Nov, 2019
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's usually a good idea to put the most recent date at the top and "push" dates down. This makes it easier to find the current state later!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3690b9b

@cdaringe cdaringe requested a review from aphillips June 26, 2023 01:09
@aphillips aphillips merged commit 63554e2 into unicode-org:main Jul 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@eemeli eemeli eemeli approved these changes

@aphillips aphillips Awaiting requested review from aphillips

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@cdaringe @CLAassistant @aphillips @eemeli