Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Packaging maven epub3-maven branch

Received: by 10.180.105.41 with SMTP id gj9mr1222798wib.3.1351892059210;
        Fri, 02 Nov 2012 14:34:19 -0700 (PDT)
X-BeenThere: epubcheck@googlegroups.com
Received: by 10.216.144.17 with SMTP id m17ls1674974wej.0.gmail; Fri, 02 Nov
 2012 14:34:16 -0700 (PDT)
Received: by 10.181.12.101 with SMTP id ep5mr1168572wid.1.1351892056501;
        Fri, 02 Nov 2012 14:34:16 -0700 (PDT)
Received: by 10.181.12.101 with SMTP id ep5mr1168571wid.1.1351892056486;
        Fri, 02 Nov 2012 14:34:16 -0700 (PDT)
Return-Path: <rdelt...@gmail.com>
Received: from mail-we0-f177.google.com (mail-we0-f177.google.com [74.125.82.177])
        by gmr-mx.google.com with ESMTPS id v1si2676wiw.2.2012.11.02.14.34.16
        (version=TLSv1/SSLv3 cipher=OTHER);
        Fri, 02 Nov 2012 14:34:16 -0700 (PDT)
Received-SPF: pass (google.com: domain of rdelt...@gmail.com designates 74.125.82.177 as permitted sender) client-ip=74.125.82.177;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of rdelt...@gmail.com designates 74.125.82.177 as permitted sender) smtp.mail=rdelt...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-we0-f177.google.com with SMTP id u50so1734927wey.36
        for <epubcheck@googlegroups.com>; Fri, 02 Nov 2012 14:34:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        bh=kXueLRIZTVHHqygkefElSPZFxYvsoJpODKrG3ZEHUgI=;
        b=ZCqc75nRjYG55kxp2sZP7PCpMPR7TdjvvmNeSZX+9VtCvjkGOuC8UA7oWPlmEKIQSL
         E2TPESoi5NPh+Dsg4QNi/eSR+q0Nan6R2n3F22c51tyFjKm3uFNdqVDDtENeYIlZq46K
         qMTE5r4qAB43o4A2fl3NAGhkXHa5+gMnYQzt03adEghcnrFQYnf/0U5B+oM6xJ6MogBs
         Y8OeAOVSZcM/sSOQ5Y6e2IU+we3Q/CEuhVb06oymizlbDyquGP4AANYdropplzbCWAFT
         1wIsaWEMbfbyIkx17v4EGOLSRQQX5bK2ASa0ns7tTV5uqD56tX5isA0TQdLyryoQ9O7S
         0SvQ==
Received: by 10.180.84.202 with SMTP id b10mr4292822wiz.13.1351892056193;
        Fri, 02 Nov 2012 14:34:16 -0700 (PDT)
Return-Path: <rdelt...@gmail.com>
Received: from ?IPv6:2a01:e35:2ecd:d830:4c2b:c199:ad0b:91bc? ([2a01:e35:2ecd:d830:4c2b:c199:ad0b:91bc])
        by mx.google.com with ESMTPS id dq6sm60149wib.5.2012.11.02.14.34.14
        (version=TLSv1/SSLv3 cipher=OTHER);
        Fri, 02 Nov 2012 14:34:15 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Packaging maven epub3-maven branch
From: Romain Deltour <rdelt...@gmail.com>
In-Reply-To: <CAAEmz6PEfdPwpmP4Kk4pBiwe0_C_6=0jCySW0xQXeEXXDT7...@mail.gmail.com>
Date: Fri, 2 Nov 2012 22:34:12 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1B02409-DA5D-44BC-9EFB-77FF5C64F...@gmail.com>
References: <CAGdiRnfYAp0U0V5YFbH69iyaDfDqZEqr8xVqUhuW2XHT=gC...@mail.gmail.com> <DF63B696-C4B7-4C2B-BC12-8A873D6BC...@gmail.com> <CAGdiRnc2iaHEPO3NxCFcoxmiGD04gLys_x7K9OgBj1W12Fv...@mail.gmail.com> <66C6734A-5626-4A09-825E-228FE82C7...@gmail.com> <CAGdiRnfbjSG1s73TPPkPamP0yqW7Lk5qABhRD=un7WaEW41...@mail.gmail.com> <d6d1df33-a1dc-4e8e-83a5-0a1b2bbed263@googlegroups.com> <7280BE85-1C35-4795-BD67-64BF20632...@gmail.com> <CAAEmz6PEfdPwpmP4Kk4pBiwe0_C_6=0jCySW0xQXeEXXDT7...@mail.gmail.com>
To: epubcheck@googlegroups.com
X-Mailer: Apple Mail (2.1499)

> this is quite peculiar. Indeed, the [creation date] comes from the
> time of the container.xml file in the zip container. From
> =
http://docs.oracle.com/javase/1.4.2/docs/api/java/util/zip/ZipEntry.html#s=
etTime%28long%29,
> the time is supposed to be "the entry modification time in number of
> milliseconds since the epoch". So for me this information should not
> depend on the local timezone !!! I will look into that to understand
> why this value varies.

Well, the ZIP contains no info on the time zone where the ZIP entry was =
created, so the API returns the entry modification time by assuming that =
the entry was created in the same time zone as the current one.
In other words, if you call ZipEntry#getTime on two different time =
zones, you will get two different values.

> By the way, the text files in the test environment are not test
> reports; they are just reference information (some interesting part of
> the report) to be matched with the actual generated reports as part of
> the unit tests.

I know, but I believe that it does not make a lot of sense to test that =
the report matches for each single test method. The "unit" tests are =
quite focused ; testing the entire report info makes it a tad more =
dependent on non-related parts of epubcheck. Additionally, it's a bit =
more difficult to maintain since every time we will like to update the =
text report format we will need to re-generate the reports for all the =
test samples.

Romain.

>=20
> Best
>  Thomas
>=20
> 2012/11/2, Romain Deltour <rdelt...@gmail.com>:
>> Thomas,
>>=20
>> I believe Ali's issue below was not an encoding issue. The problem is =
that
>> the creation date field in the text file reports is time-zone =
sensitive. The
>> fix would be to output a creation date relative to UTC when writing =
to the
>> test reports or to simply get rid of the text file reports =
altogether, which
>> do not really belong to the unit tests IMHO.
>>=20
>> Anyway, wrt encoding issues, I did face an issue some time ago due to =
a text
>> report file that was encoded in latin1 but opened as utf8, but I =
transcoded
>> the file since then.
>>=20
>> The tests run fine on revision 371 (if you're in the CET zone).
>>=20
>> Romain.
>>=20
>> On 2 nov. 2012, at 21:25, Thomas <tledou...@gmail.com> wrote:
>>=20
>>> Hi Ali,
>>>=20
>>> I just commited some corrections in r370.
>>> While doing my tests, I run into the same issue than you and I =
appears
>>> that some file texts used during tested where encoded in UTF-8 with =
BOM
>>> which make the test to fail.
>>>=20
>>> Could you please retry your build and let me know?
>>>=20
>>> Thanks in advance
>>>  Thomas
>>>=20
>>>=20
>=20
> --=20
> You received this message because you are subscribed to the Google =
Groups "epubcheck" group.
> To post to this group, send email to epubcheck@googlegroups.com.
> To unsubscribe from this group, send email to =
epubcheck+unsubscribe@googlegroups.com.
> For more options, visit this group at =
http://groups.google.com/group/epubcheck?hl=3Den.
>=20