In my Visual Studio 2012 application, I just wrote the following:
_snprintf_s(page[row++], NUM_COLS, _TRUNCATE, " Lat: %-11s (\x0b1 %3.1fm)",
lat_string, lat_precision_meters);
The \xb1 is the escape code for the "+/-" symbol, 177 in extended ASCII, ISO 8859.
I read that this was originally a Windows feature with some other name.
This works for me - it shows the correct symbol next to the precision, in my default font.
My question is: have I just introduced an issue for users who override the default font? Are all Microsoft-provisioned fonts ISO 8859-1 compliant?
Related
I'm trying to use VS Code but I'm having a problem opening code written with other editors, VS Code can't read korean language unicode? utf-8? what we call other languages in code?
I wrote the code with vim editor with some comment written in korean, and any other editors can read korean languagee but VS Code like following.
ret.insert(ret.end(), bottom.begin(), bottom.end()); // written in vim
// 는 다음과 같음
ret.insert(ret.end(), bottom.begin(), bottom.end()); // opened in VS Code
// �� ������ ����
How can I fix this problem?
Make sure your VSCode is opening the file with UTF8 encoding.
Change the encoding of a file in Visual Studio Code
I have a VB 6.0 application in which one of the windows needs to display Arabic characters. When it used VSFlexgrid 7 it worked fine, but since upgrading to VSFlexgrid 8 it displays question marks and other "junk" characters. I have references to vsflex8.ocx, vsflex8l.ocx, vsflex8n.ocx and vsflex8u.ocx in the project. Is there something else I need to download, or a setting I need to set somewhere?
(Note: not off topic per Is it appropriate to post vim questions on Stack Overflow now that there is a vi/vim site?)
On my mac using vim version:
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 10 2016 10:50:34) MacOS X (unix) version Included patches: 1-1219
when I am in visual mode, select a block of text, then click x, the text is removed but the whitespace remains. Here is a video: https://vimeo.com/176318393
similarly, when I paste using "+p (pastes from the system clipboard), the text overwrites whatever is on those lines and does not "bump" down the text being pasted. Video: https://vimeo.com/176319290
I want to solve these two problems but I have a hunch they are related so I am posting them in one question here.
A subset of my vimrc (vimrc is massive but nearly positive the plugin stuff has nothing that could affect this) that handles generic settings is here: http://pastebin.com/2APD1ycp
What is wrong?
The behavior shown in both videos is perfectly normal and expected in visual block mode.
You have visual mode and visual line mode at your disposal so, if you don't want the behavior of visual block mode… don't use it.
Normally the context menu display string for a command verb is contained in the default value of HKCR\[class]\Shell\[verb]. For example, the default value of HKCR\Word.Document.12\Shell\Open is usually '&Open', which is the menu string.
But in some Win10 installations of Office 2016, the menu string is different. Instead of '&Open', it looks like this:
#C:\Program Files (x86)\Microsoft Office\Root\VFS\ProgramFilesCommonX86\Microsoft Shared\Office16\oregres.dll,-3
Fine, this is a reference to the string with resource ID 3 in oregres.dll.
But there's a problem: On a 64-bit machine, oregres.dll doesn't exist in that folder; instead it's under ProgramFilesCommonX64 (X64 instead of X86).
Sure, I can change 'X86' to 'X64' and try again if the library load fails, but I'd like to know why this is happening before I do something as kludgy as that.
Any ideas? TIA
I do not have the inside story as to why this clearly out-of-place string has littered Office 2016, but, in addition to Word 2016's, you will find the same nonsense among Outlook 2016's entries within 64-bit Spyware 10's proprietary trash heap — I mean, Registry:
Outlook 2016 Excel Previewer Not Working
'This file cannot be previewed, because there is no previewer installed for it' Error When You Preview Excel Workbooks in Outlook 2016
If your reasonable kludge does not yield the proper string (and even if it does and the string could just as easily be hard-coded with no consequence), I should stick with typing it in.
In xcode it's possible to have characters like "💊" in code. If I paste it to Android Studio it shows me another 2 unicode characters, which don't have anything in common with "💊".
Both editors use UTF-8 encoding AFAIK.
So where is the difference?
Android Studio uses windows-1252 as default and you can use the unicode equivalent:
\uD83D\uDC8A
for example using a TextView:
myTextView.setText("\uD83D\uDC8A");
will create something like (in my device two pills are showed):
Here you can find the equivalent "Java Escape" code :
http://www.charbase.com/1f48a-unicode-pill