Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"..." string caused compilation error under VS2017 #35736

Closed
longhuan2018 opened this issue Apr 13, 2020 · 1 comment
Closed

"..." string caused compilation error under VS2017 #35736

longhuan2018 opened this issue Apr 13, 2020 · 1 comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!

Comments

@longhuan2018
Copy link
Contributor

OS : Microsoft Windows 10 Pro (Chinese Version)
Compiler: MSVC 2017

The following error is prompted during compilation

4>D:\Qilence2020\QGIS-final-3_12_0\src\core\qgstessellator.cpp(611): error C2143: 语法错误: 缺少“)”(在“user-defined literal”的前面)
4>D:\Qilence2020\QGIS-final-3_12_0\src\core\qgstessellator.cpp(611): error C2143: 语法错误: 缺少“;”(在“user-defined literal”的前面)
4>D:\Qilence2020\QGIS-final-3_12_0\src\core\qgstessellator.cpp(611): error C3688: 文本后缀“D”无效;未找到文文本运算符或文本运算符模板“operator """"D”
4>D:\Qilence2020\QGIS-final-3_12_0\src\core\qgstessellator.cpp(611): error C2001: 常量中有换行符
4>D:\Qilence2020\QGIS-final-3_12_0\src\core\qgstessellator.cpp(611): error C2143: 语法错误: 缺少“;”(在“字符串”的前面)
4>D:\Qilence2020\QGIS-final-3_12_0\src\core\qgstessellator.cpp(612): error C2143: 语法错误: 缺少“;”(在“}”的前面)

Error line code:

QgsMessageLog::logMessage( QObject::tr( "Triangulation failed. Skipping polygon…" ), QObject::tr( "3D" ) );

I checked the information and found that the cause of the error is the UTF-8 encoding problem, and there are related solutions in Microsoft
https://docs.microsoft.com/en-us/cpp/build/reference/utf-8-set-source-and-executable-character-sets-to-utf-8?redirectedfrom=MSDN&view=vs-2019

@longhuan2018 longhuan2018 added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Apr 13, 2020
@longhuan2018
Copy link
Contributor Author

I submitted a PR #35737 to solve the problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Projects
None yet
Development

No branches or pull requests

1 participant