Oops, I meant ‘double-check Justin’s findings'

On 1/24/15, 12:50 PM, "Alex Harui" <aha...@adobe.com> wrote:

>Ha, that's what I get for not double checking justin. I'll revert in a
>bit.
>Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
>
>Harbs <harbs.li...@gmail.com> wrote:
>
>
>Here’s the texts which are all clearly public domain:
>1) Alice in Wonderland (and parts of it)
>2) Parts of Nathaniel Hawthorne by Ethan Brand
>3) John F. Kennedy’s “ask not” speech.
>4) The Barnsley Manifesto
>5) UN Universal Declaration of Human Rights
>6) The Bible in Hebrew
>
>The following are Adobe licensed and donated, so they are okay:
>1) Text from the Japanese OpenType guide.
>
>
>On Jan 24, 2015, at 10:03 PM, Harbs <harbs.li...@gmail.com> wrote:
>
>> It looks to me that we are fine with this:
>> 
>>http://www.apache.org/legal/resolved.html#can-works-placed-in-the-public-
>>domain-be-included-in-apache-products
>>
>> I’ll be happy to check the rest of the test texts to make sure they are
>>all public domain.
>>
>> On Jan 24, 2015, at 9:50 PM, Harbs <harbs.li...@gmail.com> wrote:
>>
>>> Why is that a problem? As Erik points out, it’s currently public
>>>domain text. I did not go through all the text, but I’m sure Adobe
>>>picked open domain text for all the tests.(i.e. I noticed the Hebrew
>>>text is text from the bible. You can’t get more open domain then
>>>that…);-)
>>>
>>> Swapping out the texts for other texts will probably be a lot of work
>>>because there’s certain assumptions of where / how long texts will be.
>>>
>>> On Jan 24, 2015, at 8:38 PM, Alex Harui <aha...@adobe.com> wrote:
>>>
>>>> Piotr, Harbs,
>>>>
>>>> Turns out the TLF tests are infested with text from Alice In
>>>>Wonderland
>>>> and probably other famous text.  Do either of you (or anybody else)
>>>>have
>>>> time to overhaul the tests?  I think you probably would be faster at
>>>>it
>>>> than me.  I’m not that familiar with FlexUnit and how it manages
>>>>results.
>>>> I’d suggest grabbing replacement text from the Apache Flex blog
>>>>because we
>>>> own that content.
>>>>
>>>> -Alex
>>>>
>>>
>>
>

Reply via email to