HighTechTalks DotNet Forums  

Re: D20N?

Dotnet Internationalization microsoft.public.dotnet.internationalization


Discuss Re: D20N? in the Dotnet Internationalization forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
Michael S. Kaplan [MSFT]
 
Posts: n/a

Default Re: D20N? - 11-22-2007 , 12:43 PM






Hmmmm.

It is apparently awful that MSDN has committed such terrible crimes as:

1) providing multilingual samples, and
2) providing translations if their content into languages like Japanese

Although in the process of committing these terrible crimes they allow
Norman Diamond (who we could call N12D if we include the space there!) to
accuse Microsoft of doing terrible things like describing in Japanese
samples that were not written in Japanese, therefore proving terrible things
of some sort.

Most impressive here? The power of sarcasm that N12D wields is not to be
trifled with.

OTOH I guess I can do it too. :-)


--

MichKa [Microsoft]
Fundamentals Technical Lead
Windows International
Blog: http://blogs.msdn.com/michkap

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


"Norman Diamond" <ndiamond (AT) community (DOT) nospam> wrote

Quote:
What do you call it when your version of Visual Studio promises not to
support its own language, promises not to support most other countries'
languages, and promises only 7-bit clean ASCII? Although such an
environment is very useful when coding device drivers and maybe some other
specialized projects, I have to wonder about the general case. Should we
call this deinternationalization? D20N for short?

First, an example which isn't 7-bit clean, which supports 3 foreign
languages but not Japanese:
http://msdn2.microsoft.com/ja-jp/lib...d3(VS.80).aspx
* 10. F5 ?????????? [????] ????? [??] ?
* ????????
* ???????? ????? UI ????????????????
* ?????????????????? ????????????
(Press the F5 key or click the "Debug" menu "Start" entry. Depending on
the
operating system's UI language, an English, French, or German greeting
will
be displayed in the dialog box.)

Next, how to really restrict developers to a single foreign language:
http://msdn2.microsoft.com/ja-jp/lib...fy(VS.80).aspx
* ???? ???????????.resx ??????????? ????
* ??16 ?????? ASCII ??????? ???????????
(If you use the binary editor, you can edit resource files including .resx
files in hexadecimal or ASCII.)
Fortunately Visual Studio 2005 didn't obey this one. It displayed
resources
in either Shift-JIS or Unicode, I'm not sure which.

Now, I'm really glad that Visual Studio 2005 supports its own language.
This beats some Win32 APIs. But MSDN's promises of D20N started out
looking
pretty discouraging.




Reply With Quote
  #2  
Old   
Norman Diamond
 
Posts: n/a

Default Re: D20N? - 11-25-2007 , 06:47 PM






I looked back at my original posting before it was quoted by Microsoft's
software. My original posting did not have long strings of question marks.

Even in a Japanese encoded posting that quoted a Japanese encoded posting,
Japanese text turned into long strings of question marks. More D20N at
work.

P.S. I agree, since Microsoft doesn't really want to sell working versions
of Japanese software or documentation, Microsoft should not do so. Let most
of the world's market be addressed by software makers who want to address
most of the world's market.


"Michael S. Kaplan [MSFT]" <michka (AT) online (DOT) microsoft.com> wrote

Quote:
Hmmmm.

It is apparently awful that MSDN has committed such terrible crimes as:

1) providing multilingual samples, and
2) providing translations if their content into languages like Japanese

Although in the process of committing these terrible crimes they allow
Norman Diamond (who we could call N12D if we include the space there!) to
accuse Microsoft of doing terrible things like describing in Japanese
samples that were not written in Japanese, therefore proving terrible
things of some sort.

Most impressive here? The power of sarcasm that N12D wields is not to be
trifled with.

OTOH I guess I can do it too. :-)


--

MichKa [Microsoft]
Fundamentals Technical Lead
Windows International
Blog: http://blogs.msdn.com/michkap

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


"Norman Diamond" <ndiamond (AT) community (DOT) nospam> wrote in message
news:eQfEkJdJIHA.1620 (AT) TK2MSFTNGP03 (DOT) phx.gbl...
What do you call it when your version of Visual Studio promises not to
support its own language, promises not to support most other countries'
languages, and promises only 7-bit clean ASCII? Although such an
environment is very useful when coding device drivers and maybe some
other
specialized projects, I have to wonder about the general case. Should we
call this deinternationalization? D20N for short?

First, an example which isn't 7-bit clean, which supports 3 foreign
languages but not Japanese:
http://msdn2.microsoft.com/ja-jp/lib...d3(VS.80).aspx
* 10. F5 ?????????? [????] ????? [??] ?
* ????????
* ???????? ????? UI ????????????????
* ?????????????????? ????????????
(Press the F5 key or click the "Debug" menu "Start" entry. Depending on
the
operating system's UI language, an English, French, or German greeting
will
be displayed in the dialog box.)

Next, how to really restrict developers to a single foreign language:
http://msdn2.microsoft.com/ja-jp/lib...fy(VS.80).aspx
* ???? ???????????.resx ??????????? ????
* ??16 ?????? ASCII ??????? ???????????
(If you use the binary editor, you can edit resource files including
.resx
files in hexadecimal or ASCII.)
Fortunately Visual Studio 2005 didn't obey this one. It displayed
resources
in either Shift-JIS or Unicode, I'm not sure which.

Now, I'm really glad that Visual Studio 2005 supports its own language.
This beats some Win32 APIs. But MSDN's promises of D20N started out
looking
pretty discouraging.





Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.