Unicode Standards - Revision history

Sethjackson at 16:27, 30 September 2006

2006-09-30T16:27:58Z

Sethjackson at 16:26, 30 September 2006

2006-09-30T16:26:56Z

Sethjackson at 16:21, 30 September 2006

2006-09-30T16:21:02Z

Artojon: wikify

2006-09-01T10:47:17Z

wikify

Show changes

Artojon: edited categories

2006-07-08T14:11:35Z

edited categories

Sethjackson at 23:44, 12 April 2006

2006-04-12T23:44:54Z

Sethjackson at 23:43, 12 April 2006

2006-04-12T23:43:58Z

Sethjackson at 23:42, 12 April 2006

2006-04-12T23:42:41Z

Sethjackson at 20:44, 11 April 2006

2006-04-11T20:44:24Z

Thomas at 15:22, 6 February 2006

2006-02-06T15:22:20Z

@@ Line 77: / Line 77: @@
 _T()/wxT() are macros which can be used with character and string literals (in other words, 'x' or "foo") to automatically convert them to Unicode in Unicode build configuration. Please see the Unicode overview for more information.
-These macros simply returns the value passed to it without changes in ASCII build. In fact, its definition is:
+These macros simply returns the value passed to it without changes in ASCII build. In fact, the wxT() definition is:
   #ifdef UNICODE

@@ Line 3: / Line 3: @@
 == Macros ==
 {| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
@@ Line 69: / Line 71: @@
   #define _C(x) _CC((x),wxConvUTF8)
-=== wxT() ===
+=== _T()/wxT() ===
-wxT() is used for fixed text's - like XRC resources object names (only adds an L before the string if you're using Unicode build).
+_T()/wxT() are used for fixed text - like XRC resources object names (only adds an L before the string if you're using Unicode build).
-wxT() is a macro which can be used with character and string literals (in other words, 'x' or "foo") to automatically convert them to Unicode in Unicode build configuration. Please see the Unicode overview for more information.
+_T()/wxT() are macros which can be used with character and string literals (in other words, 'x' or "foo") to automatically convert them to Unicode in Unicode build configuration. Please see the Unicode overview for more information.
-This macro is simply returns the value passed to it without changes in ASCII build. In fact, its definition is:
+These macros simply returns the value passed to it without changes in ASCII build. In fact, its definition is:
   #ifdef UNICODE
@@ Line 83: / Line 85: @@
   #endif
-=== _T() ===
+_T() is exactly the same as wxT() and is defined in wxWidgets simply because it may be more intuitive for Windows programmers as the standard Win32 headers also define it (as well as yet another name for the same macro which is _TEXT()).
 Don't confuse this macro with _()!
@@ Line 97: / Line 95: @@
 === _() ===
-_() is used for text's which might be translated to other user-languages.
+_() is used for text which might be translated to other user-languages.
 This macro expands into a call to wxGetTranslation function, so it marks the message for the extraction by xgettext just as wxTRANSLATE does, but also returns the translation of the string for the current locale during execution.

@@ Line 3: / Line 3: @@
 == Macros ==
 {| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
@@ Line 55: / Line 54: @@
 multibyte C string see wxhelp (wxMBConv classes overview)
-Use this one for interacting with APIs needing char const*s, such as saving things to tinyXML.
+Use this one for interacting with APIs needing char const*s, such as saving things to TinyXML.
 Is defined in code as:

← Older revision		Revision as of 14:11, 8 July 2006
Line 1:		Line 1:
−	[[Category:~~Code::Blocks Development~~]]	+	[[Category:Developer Documentation]]
	This page is meant to be a location for developers to find all the current Unicode standards, or good practices, when developing the Code::Blocks [http://en.wikipedia.org/wiki/Integrated_development_environment IDE].		This page is meant to be a location for developers to find all the current Unicode standards, or good practices, when developing the Code::Blocks [http://en.wikipedia.org/wiki/Integrated_development_environment IDE].

← Older revision		Revision as of 23:44, 12 April 2006
Line 2:		Line 2:
	This page is meant to be a location for developers to find all the current Unicode standards, or good practices, when developing the Code::Blocks [http://en.wikipedia.org/wiki/Integrated_development_environment IDE].		This page is meant to be a location for developers to find all the current Unicode standards, or good practices, when developing the Code::Blocks [http://en.wikipedia.org/wiki/Integrated_development_environment IDE].

−	[http://www.wxwidgets.org/manuals/2.6.3/wx_unicode.html#unicode ~~Reference~~]	+	[http://www.wxwidgets.org/manuals/2.6.3/wx_unicode.html#unicode wxWidgets Unicode reference]

@@ Line 1: / Line 1: @@
 [[Category:Code::Blocks Development]]
-This page is meant to be a location for developers to find all the current Unicode standards, or good practices, when editing and developing the Code::Blocks IDE.
+This page is meant to be a location for developers to find all the current Unicode standards, or good practices, when developing the Code::Blocks [http://en.wikipedia.org/wiki/Integrated_development_environment IDE].
 [http://www.wxwidgets.org/manuals/2.6.3/wx_unicode.html#unicode Reference]

@@ Line 1: / Line 1: @@
 [[Category:Code::Blocks Development]]
-This page is meant to be a location for developers to find all the current Unicode standards, or good practices, when editor and developing the Code::Blocks program.  I am going to try and summarize the discussions that I was pointed to here, but I am leaving out the original author.  Sorry  Feel free to edit this to improve it, or keep it up to date.  I am new to using wiki, so please exscuse the bad designs.  This is a a '''VERY''' rough draft with no clear organizational pattern. ~ Joe M.
+This page is meant to be a location for developers to find all the current Unicode standards, or good practices, when editing and developing the Code::Blocks IDE.
-Actually, it's quite good.  I did a quick read-through as it looks fine to me.  All I did was add some things to the bottom. ~ me22
+[http://www.wxwidgets.org/manuals/2.6.3/wx_unicode.html#unicode Reference]
@@ Line 183: / Line 181: @@
 Don't forget the _T()s!
 Alternatively, use "\n" instead, which the compiler doesn't silently convert, so an easy-to-stop&fix compile error will occur.

← Older revision		Revision as of 20:44, 11 April 2006
Line 1:		Line 1:
−	[[Category:Development]]	+	[[Category:Code::Blocks Development]]
	This page is meant to be a location for developers to find all the current Unicode standards, or good practices, when editor and developing the Code::Blocks program. I am going to try and summarize the discussions that I was pointed to here, but I am leaving out the original author. Sorry Feel free to edit this to improve it, or keep it up to date. I am new to using wiki, so please exscuse the bad designs. This is a a '''VERY''' rough draft with no clear organizational pattern. ~ Joe M.		This page is meant to be a location for developers to find all the current Unicode standards, or good practices, when editor and developing the Code::Blocks program. I am going to try and summarize the discussions that I was pointed to here, but I am leaving out the original author. Sorry Feel free to edit this to improve it, or keep it up to date. I am new to using wiki, so please exscuse the bad designs. This is a a '''VERY''' rough draft with no clear organizational pattern. ~ Joe M.

← Older revision		Revision as of 15:22, 6 February 2006
Line 1:		Line 1:
		+	[[Category:Development]]
	This page is meant to be a location for developers to find all the current Unicode standards, or good practices, when editor and developing the Code::Blocks program. I am going to try and summarize the discussions that I was pointed to here, but I am leaving out the original author. Sorry Feel free to edit this to improve it, or keep it up to date. I am new to using wiki, so please exscuse the bad designs. This is a a '''VERY''' rough draft with no clear organizational pattern. ~ Joe M.		This page is meant to be a location for developers to find all the current Unicode standards, or good practices, when editor and developing the Code::Blocks program. I am going to try and summarize the discussions that I was pointed to here, but I am leaving out the original author. Sorry Feel free to edit this to improve it, or keep it up to date. I am new to using wiki, so please exscuse the bad designs. This is a a '''VERY''' rough draft with no clear organizational pattern. ~ Joe M.