Shane F. Carr
Shane F. Carr
> The reason is era is not specified. I get that; specifying era will work around the issue. The bug is that DateTimeFormat is taking a date which has a...
This issue is covered by the eraDisplay proposal.
I dropped the label, but I prefer to keep these issues open until the proposal reaches Stage 4 and is actually merged into the standard.
@littledan What do you see as the next steps on this issue?
What you can do today: 1. Use Intl.Segmenter to get grapheme cluster boundaries 2. Use regular expressions with Unicode properties to remove punctuation characters 3. Use String.prototype.toLocaleLowerCase to do poor-man's...
Sure; this sounds like good material for a proposal. Would you mind sharing some code snippets to help people get a better idea? A list of function names is good,...
There is substantial prior art for Unicode-aware fuzzy text matching. [UAX 15](https://unicode.org/reports/tr15/) does some discussion, as does [W3C](https://www.w3.org/TR/charmod-norm/). In 402 we should try not to reinvent the wheel. CC @aphillips...
My current idea on how to add a getter for the first day of the week is to add support for the [fw keyword](http://unicode.org/reports/tr35/#UnicodeFirstDayIdentifier) to Intl.Locale in conjunction with #409...
The intended behavior would be, ``` { formattedString: '10', roundedNumber: 10, integerDigitsCount: 2 } ``` I think the problem is in how *e* is calculated. In your example, *e* is...
+1 to making this a method on `Calendar` instances.