Xliff: use a real namespace

Open
#455 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
internationalization

Research direction

Start with MF2xliff.ts line 29 and inspect how the current placeholder XLIFF namespace is used. Determine the expected real namespace under schemas.unicode.org and whether an XSD is required; the work is complete when the placeholder is replaced and the requested MF XLIFF schema is provided if in scope.

Written by the indexing model from the issue text.

Description

MF2xliff.ts line 29 has "message format/2.0/not-real-yet" - we have the host schemas.unicode.org reserved for this purpose so i would recommend using that . But really, we should write an xsd for the 'mf' xliff namespace.

Dominant language
TypeScript
Stars
1.8k
Forks
161
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from messageformat/messageformat

All issues in messageformat/messageformat

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.