Stanisław Małolepszy
                                            Stanisław Małolepszy
                                        
                                    The sooner we relax, the less trouble we'll encounter due to cross-channel. We haven't seen much use of custom term attributes yet, which is why I think we're not seeing...
I'm trying to make a point that this is about matching strings, not identifiers. However, in context of identifiers, UAX31 could help us, yes. In my proposal, `["text"]` would follow...
No, because `StringExpressions` may not contain newlines.
> Lastly, although this might be best discussed in a separate issue, we could consider allowing attributes names to contain arbitrary characters using a new `."attr name" = Value` syntax....
I'd like to nominate this for Syntax 0.6 rather than 0.7. Or, perhaps we could separate this into two changes: - Syntax 0.6: Restrict variant keys to numbers and identifiers...
You're right about 0.6, let's keep this in 0.7 for now, thanks. Do you mean introducing a new production, say, `bracketed_text` which is like `quoted_text` but delimited with `[` and...
CLDR defines groups of supplemental data for each territory, like `timeData` or `weekData`. An incomplete table can be consulted here: http://www.unicode.org/cldr/charts/28/supplemental/territory_information.html And the full data set here: http://unicode.org/repos/cldr/trunk/common/supplemental/supplementalData.xml Perhaps a...
Hi @glen-84, thanks for your interest and questions about Fluent. I'm the leader of the project and I'll be happy to provide answers. You may be also interested in following...
(I was away last week and I'm catching up with the discussions here.) Thanks for the good comment, @spookylukey. I have a few thoughts on how to handle errors/warnings for...
I think that would be good, but in this PR I'd like to just unblock myself from being able to use the Python interpreter in VS Code. Two copies is...