W3C home > Mailing lists > Public > public-i18n-arabic@w3.org > April to June 2018

Re: Creating tests for gap analysis or other reasons

From: Shervin Afshar <shervinafshar@gmail.com>
Date: Mon, 14 May 2018 09:33:49 -0700
Message-ID: <CA+ONODm-ZNJk=VfhuRw58cyZx+_KCDsQyWa72QRv-tB3tj8nvg@mail.gmail.com>
To: r12a <ishida@w3.org>
Cc: Martin J. Dürst <duerst@it.aoyama.ac.jp>, public-i18n-arabic@w3.org
Thanks. I'm assuming that this is required only for the gap analysis cases
which show a difference between the two. Is that accurate?

On Sun, May 13, 2018, 23:16 r12a <ishida@w3.org> wrote:

> good guess, Martin!  Exactly right.
>
> ri
>
>
> On 14/05/2018 03:53, Martin J. Dürst wrote:
> > Hello Shervin,
> >
> > On 2018/05/14 06:21, Shervin Afshar wrote:
> >> Hi Richard,
> >>
> >> On 22/02/18 09:42, r12a wrote:
> >>
> >>> There are two types of test page pointed to:
> >>>
> >>> [1] Tests: standard syntax • proprietary syntax
> >>
> >> Could you please elaborate a bit on this "standard" vs. "proprietary
> >> syntax"?
> >
> > Just a guess, but I think "proprietary syntax" means CSS properties with
> > browser/rendering-engine specific prefixes (-webkit-, -ms-, -moz-, and
> > so on).
> >
> > Regards,   Martin.
> >
> >> Should we adjust our alreq gap analysis tests accordingly as well?
> >>
> >> Thanks.
> >>
> >> ↪ Shervin
> >>
>
>
Received on Monday, 14 May 2018 16:34:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:55:33 UTC