You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VS Code version: 1.11.0-insider
Python Extension version: 0.6.0
Python Version: 3.3.5
OS and version: win7-pro
Actual behavior
Expected behavior
Steps to reproduce:
write "ru" docstring
hovered methods
It's a heisenbug... The text with the wrong encoding appears not on every hover. He occasionally appears when auto-save file, even when editing parcels not related to the method or docstring.
Please could you provide some sample code and exact steps to replicate this issue.
I'm having trouble replicating this at my end. Thanks for your help.
# -*- coding: utf-8 -*-"""Dieses Modul enthält.... <---"""classClient(AuthenticatedClient):
asyncdefschema(self, entity_type: str, single: bool=False) ->object:
"""Fragt das Schema eines Typens von Eintrag ab. Parameters ---------- entity_type : str Der Entitätstyp.... <--- single : bool, optional Ein Wert, der bestimmt, ob das Schema alle referenzierten Entitätstypen.... <--- """
....
Related microsoft/vscode#5388 actually fixed in VSC right around March 2017.
Currently I see that Russian and other languages working when file is saved in UTF-8 (BOM is not required). Things do get broken if file gets forcibly saved in OEM CP (console CP). VSC loads it incorrectly anyway.
If file is saved in UTF-8 (console CP is 866), VSC works properly
// The default character set encoding to use when reading and writing files. This setting can be configured per language too.
"files.encoding": "utf8",
// When enabled, will attempt to guess the character set encoding when opening files. This setting can be configured per language too.
"files.autoGuessEncoding": false,
Igor Novozhilov (@IgorNovozhilov)
Apologies for the late response, but are you still experiencing this issue.
Please feel free to re-open the issue if you are still experiencing this issue.
Closing as it may have been resolved along with #100
Activity
DonJayamanne commentedon Nov 13, 2017
From Igor Novozhilov (@IgorNovozhilov) on March 23, 2017 20:58
I found 🐛. Wrong encoding appears only once executed linting file and highlight warnings.
DonJayamanne commentedon Nov 13, 2017
Please could you provide some sample code and exact steps to replicate this issue.
I'm having trouble replicating this at my end. Thanks for your help.
DonJayamanne commentedon Nov 13, 2017
From Igor Novozhilov (@IgorNovozhilov) on April 6, 2017 18:5
Occurs only on
windowswithRU-rulocalization, and utf-8 py-file encoding.DonJayamanne commentedon Nov 13, 2017
From Marcus Schweda (@mdschweda) on July 18, 2017 19:8
Same for any Umlaut (aöü)
MikhailArkhipov commentedon Dec 12, 2017
Related microsoft/vscode#5388 actually fixed in VSC right around March 2017.
Currently I see that Russian and other languages working when file is saved in UTF-8 (BOM is not required). Things do get broken if file gets forcibly saved in OEM CP (console CP). VSC loads it incorrectly anyway.
If file is saved in UTF-8 (console CP is 866), VSC works properly
MikhailArkhipov commentedon Dec 13, 2017
May need to check settings
DonJayamanne commentedon May 31, 2018
Igor Novozhilov (@IgorNovozhilov)
Apologies for the late response, but are you still experiencing this issue.
Please feel free to re-open the issue if you are still experiencing this issue.
Closing as it may have been resolved along with #100