[OASIS Issue Tracker] (XLIFF-71) XLIFF 2.1 spec: bad links

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/XLIFF-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Filip updated XLIFF-71:
-----------------------------

    Labels: editorial ready-for-vote  (was: Proposed editorial ready-for-vote)

> XLIFF 2.1 spec: bad links
> -------------------------
>
>                 Key: XLIFF-71
>                 URL: https://issues.oasis-open.org/browse/XLIFF-71
>             Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
>          Issue Type: Bug
>          Components: other
>    Affects Versions: 2.1_cos01
>         Environment: http://markmail.org/thread/vrbgs6oxn5tjcotq
>            Reporter: David Filip
>            Assignee: David Filip
>            Priority: Minor
>              Labels: editorial, ready-for-vote
>             Fix For: 2.1_os
>
>
> There are two different pages that I can find for the XLIFF 2.1 spec:
> A newer document here:
> http://docs.oasis-open.org/xliff/xliff-core/v2.1/xliff-core-v2.1.html
> It is marked "12 October 2017" and the sub-title is "Candidate OASIS
> Standard 01"
> And an older one t
> http://docs.oasis-open.org/xliff/xliff-core/v2.1/cs01/xliff-core-v2.1-cs01.html
> Marked "23 August 2017" and the subtitle is "Committee Specification 01"
> Looking at the newest one (xliff-core-v2.1.html) some of the links are wrong
> (they point to older doc, instead of staying in the same doc)
> For instance go to <source> (
> http://docs.oasis-open.org/xliff/xliff-core/v2.1/xliff-core-v2.1.html#source
> )
> and click on any of the possible content tags.
>  <sm> goes to
> http://docs.oasis-open.org/xliff/xliff-core/v2.1/cos01/xliff-core-v2.1-cos01.html#sm
> and so on.
> v2.1/xliff-core-v2.1.html#sm, click on any attribute (e.g. type), it goes
> to
> /v2.1/cos01/xliff-core-v2.1-cos01.html#type
> I might be some bad redirect though, because saving the file the href(s)
> point to local labels
> (#em, #type and so)
> Probably not a big deal, just confusing...



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)