Unit Intervals

Cameron Dutro cameron at lumoslabs.com
Wed Dec 10 15:44:24 CST 2014


Hey Yury and Jukka,

This is great info, thank you both for explaining the inherent issues in
collecting such data. I imagine we could come up with several different
contexts that would serve as the main use cases for such data, then add
additional contexts as they become necessary. This would be similar to how
CLDR currently stores data for full, narrow, and abbreviated date and unit
formats. I'm envisioning something in the XML like:

<timeIntervals>
    <timeInterval context="inclusive">
        <year>
            <one>every year</one>
            <other>every {0} years</other>
        </year>
    </timeInterval>
    <timeInterval context="sequential">
        <year>
            <one>each year</one>
            <other>every {0} years</other>
        </year>
    </timeInterval>
</timeIntervals>

(I just made all this up, it's not scientifically derived in any way.)

Would having multiple contexts be appropriate for Russian and other
languages?

-Cameron

On Wed, Dec 10, 2014 at 4:16 AM, Jukka K. Korpela <jkorpela at cs.tut.fi>
wrote:

> 2014-12-10, 13:15, Yury Tarasievich wrote:
>
>  Then it's a natural language problem, and as such, (almost) completely
>> un-algorithmisable, at least in such a context.
>>
>> yury
>>
>> On 12/10/2014 01:43 PM, Philippe Verdy wrote:
>>
>>> The term "interval" is badly chosen in what he
>>> describes; Cameron actually wants to express
>>> periodicity (without any implied start or end;
>>> i.e. only the frequency).
>>>
>>
> It is “algorithmisable” in an essential way, though it is debatable
> whether this justifies inclusion into CLDR and how important this is
> relative to all kinds of things that might be included there.
>
> For example, in questionnaires and reports, phrases like “every 2 months”
> are common. And the amount of time might be something that is determined
> “dynamically”, i.e. during program execution, and should be presented
> without any contribution from a human being, i.e. automatically.
>
> An obvious problem here is that different languages use different
> expressions, so that this is not just a matter of using a pattern
> consisting of a word like “every” and a designation of amount of time. Some
> languages use expressions that would be something like “each 2nd month” if
> applied in English. There are probably other approaches too, so some
> pre-study would be needed to find out the basic overall patterns.
>
> Yucca
>
>
>
>
> _______________________________________________
> CLDR-Users mailing list
> CLDR-Users at unicode.org
> http://unicode.org/mailman/listinfo/cldr-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20141210/c350a64a/attachment.html>


More information about the CLDR-Users mailing list