On Tue, 2022-11-08 at 09:17 -0800, TheDiveO wrote:
> I've always wondered how to deal with exported versus unexported
> identifiers in scripts like Chinese?
There is an issue for this https://go.dev/issue/22188 which discusses
the approaches that are currently used with a view to making it
I've always wondered how to deal with exported versus unexported
identifiers in scripts like Chinese?
On Sunday, November 6, 2022 at 3:08:59 PM UTC+1 ba...@iitbombay.org wrote:
> In Indic scripts in certain contexts you have to use a vowel sign for the
> typography to make sense; you can’t use
In Indic scripts in certain contexts you have to use a vowel sign for the typography to make sense; you can’t use a vowel letter in its place. So for example the middle “ku” in my name has to be written as ક+ુ — which will be rendered as કુ — even though it is equivalent to ક+્+ઉ. Also, “halant”
% unicode -d పే
U+0C2A 'ప' telugu letter pa
U+0C47 'ే' telugu vowel sign ee
% unicode -U C2A C47
U+0C2A 'ప' TELUGU LETTER PA
category: Lo
canonical combining classes: 0
bidirectional category: L
mirrored: N
U+0C47 'ే' TELUGU VOWEL SIGN EE
category: Mn
canonical combining classes: 0
On Sun, Nov 06, 2022 at 01:45:53PM +0530, Nikhilesh Susarla wrote:
>> Per the Go spec[1], an identifier consists of a Unicode letter followed by
>> zero or more Unicode letters or digits. The character పే is in the Unicode
>> category nonspacing mark rather than the category letter.
[...]
> So,
Per the Go spec[1], an identifier consists of a Unicode letter followed by
zero or more Unicode letters or digits. The character పే is in the Unicode
category nonspacing mark rather than the category letter.
If you choose a Telugu letter then your code compiles as expected[2].
[1] -
