blog.jdlh.com
Jim DeLaHunt, world-ready » A Technology Globalization meetup for the Vancouver Area: (2) Why, Naming
http://blog.jdlh.com/en/2014/12/31/i18n-meetup-why-naming
Jim DeLaHunt, world-ready. Helping business go global, live from British Columbia. Creating default object from empty value in /home/jdlh/blog.jdlh.com/wp-includes/classes.php. A Technology Globalization meetup for the Vancouver Area: (2) Why, Naming. A Technology Globalization meetup for the Vancouver Area: (1) What, Who. Oct 31, 2014). Happily, this group has already started. We held our first meeting. On Monday, Dec 8, 2014. Our placeholder Twitter feed is @imlig1604. The Vancouver area is a curious p...
blog.jdlh.com
Jim DeLaHunt, world-ready » Jim DeLaHunt
http://blog.jdlh.com/en/author/jim-delahunt
Jim DeLaHunt, world-ready. Helping business go global, live from British Columbia. Creating default object from empty value in /home/jdlh/blog.jdlh.com/wp-includes/classes.php. Posts by Jim DeLaHunt:. Resetting GnuCash’s import transaction matching. Requirements for comparing digital scores. Encoding Music at Music Encoding Conference 2016. Recruiting people, and structuring their work. No longer a foreign troublemaker in Canada. I passed the Canadian Citizenship Test! Next Page ». Most of the time.
blog.jdlh.com
Jim DeLaHunt, world-ready » language
http://blog.jdlh.com/en/category/language
Jim DeLaHunt, world-ready. Helping business go global, live from British Columbia. Creating default object from empty value in /home/jdlh/blog.jdlh.com/wp-includes/classes.php. Archived Posts from this Category. Tain’t right’, says he: storm in apostrophe. A friend pointed me to a interesting blog post,. Which Unicode character should represent the English apostrophe? And why the Unicode committee is very wrong.). Very, very wrong. I’m here to tell you why why.” [Emphasis in the original.]. On Twitter...
blog.jdlh.com
Jim DeLaHunt, world-ready » A Technology Globalization meetup for the Vancouver Area: (1) What, Who
http://blog.jdlh.com/en/2014/10/31/i18n-meetup-what-who
Jim DeLaHunt, world-ready. Helping business go global, live from British Columbia. Creating default object from empty value in /home/jdlh/blog.jdlh.com/wp-includes/classes.php. A Technology Globalization meetup for the Vancouver Area: (1) What, Who. My role model is IMUG. Another role model is VanDev. Our little language and technology community has fuzzy boundaries, and we have no agreed-on word for ourselves. But we include disciplines and activities like:. T9n), the linguistic work to render written w...
tedclancy.wordpress.com
Which Unicode character should represent the English apostrophe? (And why the Unicode committee is very wrong.) | Ted's Blog
https://tedclancy.wordpress.com/2015/06/03/which-unicode-character-should-represent-the-english-apostrophe-and-why-the-unicode-committee-is-very-wrong/comment-page-1
Which Unicode character should represent the English apostrophe? And why the Unicode committee is very wrong.). Which Unicode character should represent the English apostrophe? And why the Unicode committee is very wrong.). June 3, 2015. June 11, 2015. The Unicode committee is very clear that U 2019 (RIGHT SINGLE QUOTATION MARK) should represent the English apostrophe. Section 6.2 of the Unicode Standard 7.0.0 states:. We’ve been here before. Very, very wrong. I’m here to tell you why why. According to t...
tedclancy.wordpress.com
Which Unicode character should represent the English apostrophe? (And why the Unicode committee is very wrong.) | Ted's Blog
https://tedclancy.wordpress.com/2015/06/03/which-unicode-character-should-represent-the-english-apostrophe-and-why-the-unicode-committee-is-very-wrong
Which Unicode character should represent the English apostrophe? And why the Unicode committee is very wrong.). Which Unicode character should represent the English apostrophe? And why the Unicode committee is very wrong.). June 3, 2015. June 11, 2015. The Unicode committee is very clear that U 2019 (RIGHT SINGLE QUOTATION MARK) should represent the English apostrophe. Section 6.2 of the Unicode Standard 7.0.0 states:. We’ve been here before. Very, very wrong. I’m here to tell you why why. According to t...