jira and github open
r12a via CLDR-Users
cldr-users at unicode.org
Mon May 13 10:49:13 CDT 2019
hi Steven,
Thanks for the reply.
The https://unicode-org.atlassian.net/projects/CLDR/issues was
unresponsive for me, until just now when i clicked on several items in
the left column, and *then* clicked on "Issues and filters". Now it
seems to work straight away. I previously tried it on Firefox and Chrome
with the same result. Not sure what's going on there.
Ok, so i'll try reporting the issue now via the link.
cheers,
ri
On 13/05/2019 16:34, Steven R. Loomis wrote:
> Richard,
> The first link below is the issue tracker
> <https://unicode-org.atlassian.net/projects/CLDR>. “We need to fix up
> docs” is a bit of an understatement here: There needs to be a link to
> that tracker, etc.
>
> The README has been in HTML since it was added that way in 2012… what
> you are looking at is a faithful copy of the previous svn repository,
> not a rewrite. Would you like to use the above link and suggest that
> the README be moved to markdown?
>
> Thank you for the feedback!
>
> --
> Steven R. Loomis | @srl295 | git.io/srl295 <http://git.io/srl295>
>
>
>
>> El may. 13, 2019, a las 3:49 a. m., r12a <ishida at w3.org
>> <mailto:ishida at w3.org>> escribió:
>>
>> Did you intend the README file to be html source code ?
>>
>> Also, i was disappointed not to see an Issues tag, or any indication
>> of how to raise issues.
>>
>> hth
>> ri
>>
>>
>> On 11/05/2019 02:44, Steven R. Loomis via CLDR-Users wrote:
>>> I’m declaring these open. We still need to fix up docs, etc. but have
>>> a look and report any issues here.
>>> https://unicode-org.atlassian.net/projects/CLDR
>>> https://github.com/unicode-org/cldr.git
>
>
More information about the CLDR-Users
mailing list