Unicode compatibility

[hhaensel]

There are (at least) two cases where unicode characters in f"..." expressions currently fail due to index arithmetics:

• directly preceeding format expressions
• at the end of the f"..." expression

Replacing index arithmetics by prevind() and nextind(), e.g. j-1 => prevind(s, j), would solve the problem.

StrLiterals has the same problem, and I have already submitted a PR. I also have version for StringLiterals at hand if you are interested ;-)
But you indicated that you are going to no longer support StringLiterals ...

Two expressions which currently fail:

@test f"π(22)" == "π4"
@test f"π = (290)°" == "π = 180°"

[ScottPJones]

I don't understand this - why should there be any transformation?
f"π(22)" should be simply "π(22)", not "π4"

[ScottPJones]

All interpolations (and formatting) sequences must start with a '' (backslash).

[Socob]

The issue description (and @ScottPJones’ comment) is suffering from some broken Markdown formatting due to the backslashes and asterisks. The intended expressions are

@test f"π\(2*2)" == "π4"
@test f"π = \(2*90)°" == "π = 180°"

Although not sure if it matters at this point since it seems that this package hasn’t been developed for a long time now.

[ScottPJones]

StringLiterals has been replaced by StrLiterals, and this bug was fixed there.