Time Until about nsdate-timeago

[tjhenry]

It looks like this would require either duplicating the timeAgo method or re-factoring timeAgo and timeUntil to use the same numbers and general logic. Interesting idea though.

[Antoine4011]

I would be very interested with this kind of feature too.

[kevinlawler]

Let's call this feature timeUntil. We can implement it as follows:

1. Someone (anyone) propose an English template for the new strings which we can review before accepting. This step will not modify the codebase.
2. (Items 2 and 3 should be submitted at the same time.) Update the logic in the codebase to compute the strings for future dates using the approved template. Refactor and add function aliases as necessary. As @tjhenry suggests, I suspect we'll want the aliases (timeAgo, timeUntil, etc.) to all compute the fully generalized method, but perhaps not.
3. Update all existing localizations with filler English-to-English versions of the new template and highly visible notices that the localizations are incomplete, with a request for help and a reminder to remove the notice upon completion.
4. Notify the previous translators that the project has been updated. Politely request that they update the new strings. If the previous translators cannot contribute, find suitable substitute translators.
5. Note that, as with timeAgo, timeUntil may require localization-dependent logic.

Obviously, more complex than writing an if/else block in English, but also useful to more people.

[kevinlawler]

It would be nice to solve #11 at the same time, perhaps by adding repeated versions of the base strings with different capitalization formats.