Just stumbled across this very minor issue. The following contains fa莽ade with a 莽 instead of a c three times:
https://github.com/dotnet/efcore/blob/eb180fe94d8efb1a68f9e12021ebc09aea854427/test/EFCore.Specification.Tests/TestUtilities/DatabaseFacadeExtensions.cs#L15-L16
@lauxjpn Is this a problem? https://dictionary.cambridge.org/us/dictionary/english/facade
@ajcvickers Oops, wasn't aware that this is actually correct English (looked French to me). I guess this can be ignored then :)
@ajcvickers So line 12 is misspelled, then 馃槀 https://github.com/dotnet/efcore/blob/eb180fe94d8efb1a68f9e12021ebc09aea854427/test/EFCore.Specification.Tests/TestUtilities/DatabaseFacadeExtensions.cs#L12 ??
@ErikEJ Well, I guess some are more posh then others on the team :)
(Could make for an interesting NN project trying to extrapolate from peoples source code things like, education, social status, family background etc.)
We should write "focussed" instead of "focus" and in general have more British spelling to give the project a more elitist scent.
(plus, as I agreed I will start using Hebrew in identifiers)
(plus, as I agreed I will start using Hebrew in identifiers)
@roji I absolutely agree. This is 2020 after all!
Though I have successfully avoided pushing any useful commits to EF Core so far, I would really like to write some Japanese source code at some point in time, so I get quicker at typing with the Microsoft IME. (No worries, I wouldn't dare to use the honorific language level, as this might get a bit tricky to get right.)
You guys really want me to start using "ou" rather than "o"?
No honorific - no contribution...
Most helpful comment
@ErikEJ Well, I guess some are more posh then others on the team :)
(Could make for an interesting NN project trying to extrapolate from peoples source code things like, education, social status, family background etc.)