Ć

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Norman Diamond - 02 Aug 2007 03:03 GMT

Running Visual Studio 2005 SP1 Japanese on Windows XP SP2 Pro Japanese,
editing a Polish language resource file, I need to input the letter Ć.

In Windows XP's language bar, I set the keyboard language and layout to
Polish. Typing into Visual Studio 2005, I can input c and C and ć, but not
Ć. I can press right-Alt + right-Shift + c, and it inputs nothing.

I can open Notepad, and in Windows XP's language bar again set the keyboard
language and layout to Polish. Typing into Notepad, I can input c and C and
ć and Ć. Using the mouse I can select Ć, copy it, and paste it into Visual
Studio.

This is the opposite of previously discovered problems using Visual Studio
2005 SP1 and Unicode resource files. Previously I could type input when the
keyboard was set to a foreign language (English or whatever) but at random
times couldn't copy and paste foreign characters (such as English £ or
whatever). So Visual Studio is even more random than I thought.

I'm lucky though. This Visual Studio session has been open for more than 30
minutes and hasn't crashed yet. And I could even find a workaround to type
the input I needed, so far. Wow, so lucky today.

Reply to this Message

Michael S. Kaplan [MSFT] - 02 Aug 2007 15:36 GMT

Known issue related to the "helpful" shortcuts provided by products like VS
and Word that conflict with keyboard shortcuts. The only workaround is to
disable the CTRL+ALT+SHIFT shortcut in question.

Signature

MichKa [Microsoft]
NLS Collation/Locale/Keyboard Technical Lead
Globalization Infrastructure, Fonts, and Tools
Blog: http://blogs.msdn.com/michkap

This posting is provided "AS IS" with
no warranties, and confers no rights.

> Running Visual Studio 2005 SP1 Japanese on Windows XP SP2 Pro Japanese,
> editing a Polish language resource file, I need to input the letter C.
[quoted text clipped - 17 lines]
> 30 minutes and hasn't crashed yet. And I could even find a workaround to
> type the input I needed, so far. Wow, so lucky today.

Reply to this Message

Norman Diamond - 03 Aug 2007 02:10 GMT

Um, nice internationalization in your posting.

Thank you for the information about Visual Studio, I do appreciate it, and I
should either search for the option to turn off misfeatures or continue
using Notepad as a workaround. Thank you, I do appreciate the information
in your posting.

But the supposed internationalization of your posting makes your quotation
of my posting look like nonsense. In your quotation of my previous message,
it looks like I was saying that I could type c and C and c but not C. Both
lower-case c characters look identical and both upper-case C characters look
identical, and it makes me look like an idiot. I am an idiot sometimes but
I wasn't this time.

I've looked back at my original message and the contents were correct. I
set the encoding of that message to UTF-8 because I know that Japanese
character sets can't handle the Polish characters that I had to write about.
Outlook Express is still displaying the contents of my original message
correctly, only the Subject line gets garbaged because OE can't handle I18N
in Subject lines.

So why is your posting encoded in Japanese and why did you wipe out the
Polish characters that I had typed? Surely you should have at least as many
I18N capabilities as I have.

> Known issue related to the "helpful" shortcuts provided by products like
> VS and Word that conflict with keyboard shortcuts. The only workaround is
[quoted text clipped - 22 lines]
>> 30 minutes and hasn't crashed yet. And I could even find a workaround to
>> type the input I needed, so far. Wow, so lucky today.

Reply to this Message

Michael S. Kaplan [MSFT] - 03 Aug 2007 02:40 GMT

Well, I am using Outlook Express, which seems be getting hints of Japanese
from you. It has nothing to do with internationalization skill.

You should learn to relax a bit more....

Signature

> Um, nice internationalization in your posting.
>
[quoted text clipped - 47 lines]
>>> than 30 minutes and hasn't crashed yet. And I could even find a
>>> workaround to type the input I needed, so far. Wow, so lucky today.

Reply to this Message

Norman Diamond - 03 Aug 2007 02:54 GMT

If you're using Outlook Express, when you posted a followup to a message
that you were reading, why didn't it copy the encoding setting of UTF-8 from
the quoted message to your message? Really, this seems like an obvious
thing to do, in order to avoid breaking the contents of the quoted message.

In fact it's not only obvious to me, it's obvious to someone in your
company, because Outlook Express does this automatically and I didn't even
have to set it to do so. (Or if OEMs can customize OE settings then maybe
this was obvious to someone in every OEM whose products I ever used, instead
of to someone in your company.)

Meanwhile, although I'm a user of Outlook Express, I didn't write any of its
code (at least not that I know of). So when it gets hints of Japanese, it
gets its hints from your company (or your company's suppliers).

> Well, I am using Outlook Express, which seems be getting hints of Japanese
> from you. It has nothing to do with internationalization skill.
[quoted text clipped - 52 lines]
>>>> than 30 minutes and hasn't crashed yet. And I could even find a
>>>> workaround to type the input I needed, so far. Wow, so lucky today.

Reply to this Message

Cezary Noweta - 03 Aug 2007 14:37 GMT

Hello,

> Known issue related to the "helpful" shortcuts provided by products like VS
> and Word that conflict with keyboard shortcuts. The only workaround is to
> disable the CTRL+ALT+SHIFT shortcut in question.

AFAIK, Office apps (or at least Word) distinguish between "raw" Ctrl+Alt and "meta"
Ctrl+Alt (which is retrieved by pressing Right Alt). Maybe it is time to implement
this behaviour into VS?

-- best regards

Cezary Noweta

Reply to this Message

Michael S. Kaplan [MSFT] - 03 Aug 2007 14:47 GMT

Well, they sort of do -- the methods they use are imperfect and it is still
quite easy to have problems.

It is the #1 support question in MSKLC (now that 64-bit works) -- keyboards
that work great in Notepad, poorly in Word....

Signature

> Hello,
>
[quoted text clipped - 12 lines]
>
> Cezary Noweta

Reply to this Message

Ć

Free Magazines