For style, I tend to prefer em dash and have used it in documentation without thinking about it: it's the only non standard character I know the Win alt code and linux unicode key sequence for.dbenage-cx wrote: En dash is probably the "proper" character to use for the separation (or em dash, depending on interpretation), but did not feel it warranted compiler specific handling when the difference with hyphen-minus is not likely to be noticed.
[Nov. 20 test build (e6848d8)] Missing info on tech hover
Moderator: Oberlus
Forum rules
Always mention the exact version of FreeOrion you are testing.
When reporting an issue regarding the AI, if possible provide the relevant AI log file and a save game file that demonstrates the issue.
Always mention the exact version of FreeOrion you are testing.
When reporting an issue regarding the AI, if possible provide the relevant AI log file and a save game file that demonstrates the issue.
Re: [Nov. 20 test build (e6848d8)] Missing info on tech hove
Mat Bowles
Any code or patches in anything posted here is released under the CC and GPL licences in use for the FO project.
Any code or patches in anything posted here is released under the CC and GPL licences in use for the FO project.
-
- Programmer
- Posts: 389
- Joined: Sun Feb 14, 2016 12:08 am
Re: [Nov. 20 test build (e6848d8)] Missing info on tech hove
I did not realize UTF-8 encoded string literal is not implementation-defined.Geoff the Medio wrote:What's wrong withCode: Select all
u8" \u2013 "
If it is a noticeable difference to others, can open a PR for change to em dash.