CLDR-17829 move PathDescriptions.txt to PathDescriptions.md

[srl295]

• add lychee build task to link check PathDescriptions.md
• added PathDescriptionParser and unit tests
• fixes many descriptions, link targets, and placeholders

CLDR-17829

• This PR completes the ticket.

ALLOW_MANY_COMMITS=true

[srl295]

Note: hard build failure if PathDescriptions.md contains an invalid link: (note cldr.unicode.xrg)

[macchiati]

If it starts with SKIP, but has other characters, it is an error; so best to raise an exception.

[srl295]

the description here is more rich, it's for you to name (or in the future group) these entries.

as below, where First Day of the Week is a comment.

### First Day of the Week

- `^//ldml/localeDisplayNames/types/type\[@key="fw"]\[@type="([^"]*)"]`

The name of “first day of the week is {1}”. For more information, please see [Key Names].

[macchiati]

I don't understand ... that snippet does not have SKIP in it

[macchiati]

Mostly minor except for the "#h."

[srl295]

@macchiati some of the other targets don't seem to exist.

[srl295]

"Cyclic Name Sets" isn't an anchor (defect in date-time-names.md )

[srl295]

I thought this task was to move the format over, for future fixup. I will revisit this tomorow

[srl295]

I'll add a test against the relevant sites page… Probably for a future PR

[macchiati]

I thought this task was to move the format over, for future fixup. I will revisit this tomorow

I just thought that as long as you were getting the anchor text, you could fix the links as well. It can be a separate PR though.

[srl295]

I thought this task was to move the format over, for future fixup. I will revisit this tomorow

I just thought that as long as you were getting the anchor text, you could fix the links as well. It can be a separate PR though.

No, i had just title cased the variable names.

[srl295]

All #h. fragments removed and corrected as best I can.

KEY_NAMES / [Key Names] has been broken for a couple of years according to git. A bunch of the types go to the same section on sensitive territory names.

    public static final String KEY_NAMES =
            "https://cldr.unicode.org/translation/displaynames/countryregion-territory-names#h.x27jspwj91af";

So probably all of these need review.

[macchiati]

I was thinking that for this file and similar ones, it would be useful to have a tool that generated a sample of each message, that would be used to build a web page; we could then review to make sure that all the parameters were right, etc.

Not part of this ticket — I'll file a different one for it.

[macchiati]

https://unicode-org.atlassian.net/browse/CLDR-18555

[srl295]

sorry, i was running the wrong test locally.

This also now fixes a number of cases where the placeholders {} were wrong and were being passed through to users. and adds a test so it doesn't happen again.

[srl295]

I was thinking that for this file and similar ones, it would be useful to have a tool that generated a sample of each message, that would be used to build a web page; we could then review to make sure that all the parameters were right, etc.

Not part of this ticket — I'll file a different one for it.

i recommend deduping cases where the message is the same for multiple xpaths.

[macchiati]

I was thinking that for this file and similar ones, it would be useful to have a tool that generated a sample of each message, that would be used to build a web page; we could then review to make sure that all the parameters were right, etc.
Not part of this ticket — I'll file a different one for it.

i recommend deduping cases where the message is the same for multiple xpaths.

That's what I meant by one message per line, eg per regex path in the <key, values> pair.