<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	
	>
<channel>
	<title>
	Comments on: Don&#8217;t forget outsourcers!	</title>
	<atom:link href="https://www.robg3d.com/2012/02/dont-forget-outsourcers/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.robg3d.com/2012/02/dont-forget-outsourcers/</link>
	<description>Blog of Rob Galanakis (@robgalanakis)</description>
	<lastBuildDate>Fri, 24 Feb 2012 02:12:33 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.4.1</generator>
	<item>
		<title>
		By: Robert		</title>
		<link>https://www.robg3d.com/2012/02/dont-forget-outsourcers/#comment-8647</link>

		<dc:creator><![CDATA[Robert]]></dc:creator>
		<pubDate>Fri, 24 Feb 2012 02:12:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.robg3d.com/?p=938#comment-8647</guid>

					<description><![CDATA[one more thing: Unicode support is also nice to have. If someone accidentally enters Chinese/Russian/etc characters as file name or in a text box in your tool, then it should be able to handle this or pop out an error msg (instead of just dying or adding garbage to your db/xml/etc).

Max scripts: extended ASCII characters break max script on non western PCs! (we then always have to change the windows system locale - annoying). Stay away from the degree sign, the copyright sign, etc. In max script stick to the characters printed on your US/western european keyboard. If you don&#039;t see the character there, then don&#039;t use it in the script.]]></description>
			<content:encoded><![CDATA[<p>one more thing: Unicode support is also nice to have. If someone accidentally enters Chinese/Russian/etc characters as file name or in a text box in your tool, then it should be able to handle this or pop out an error msg (instead of just dying or adding garbage to your db/xml/etc).</p>
<p>Max scripts: extended ASCII characters break max script on non western PCs! (we then always have to change the windows system locale &#8211; annoying). Stay away from the degree sign, the copyright sign, etc. In max script stick to the characters printed on your US/western european keyboard. If you don&#8217;t see the character there, then don&#8217;t use it in the script.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Robert		</title>
		<link>https://www.robg3d.com/2012/02/dont-forget-outsourcers/#comment-8646</link>

		<dc:creator><![CDATA[Robert]]></dc:creator>
		<pubDate>Fri, 24 Feb 2012 02:05:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.robg3d.com/?p=938#comment-8646</guid>

					<description><![CDATA[Biggest problems for us are indeed security (please test your tools on non admin accounts!) and network latency - especially when we have to connect from China to North American servers. Tools which require &quot;always-on&quot; connections are especially bothersome. 

If you talk to some server in your script (P4, database, whatever) please re-check if the connection is still there before doing something. Programs not handling dropped connections is something we encounter often.

Machine setup: Please avoid intrusive setups which totally re-configure Max/Maya/the-entire-PC and make it impossible to run tools from another client afterwards. (my favorite annoyance: MAYA_APP_DIR. Use a batch file to set it and to launch Maya afterwards, don&#039;t just change system environment variables with your tool&#039;s installer). Uninstallers are also welcome, but if your tool isn&#039;t intrusive, then this isn&#039;t so high on our &quot;want to have&quot; list.

Interestingly enough, Localization isn&#039;t a very big topic for us. I think the artists are used to working with English tools. We do however summarize and translate parts of the client supplied docs and also have hands-on training sessions. Translating the tools themselves would probably take more time than we can fit into our busy schedule.

Thanks Rob for putting the spotlight on this topic!]]></description>
			<content:encoded><![CDATA[<p>Biggest problems for us are indeed security (please test your tools on non admin accounts!) and network latency &#8211; especially when we have to connect from China to North American servers. Tools which require &#8220;always-on&#8221; connections are especially bothersome. </p>
<p>If you talk to some server in your script (P4, database, whatever) please re-check if the connection is still there before doing something. Programs not handling dropped connections is something we encounter often.</p>
<p>Machine setup: Please avoid intrusive setups which totally re-configure Max/Maya/the-entire-PC and make it impossible to run tools from another client afterwards. (my favorite annoyance: MAYA_APP_DIR. Use a batch file to set it and to launch Maya afterwards, don&#8217;t just change system environment variables with your tool&#8217;s installer). Uninstallers are also welcome, but if your tool isn&#8217;t intrusive, then this isn&#8217;t so high on our &#8220;want to have&#8221; list.</p>
<p>Interestingly enough, Localization isn&#8217;t a very big topic for us. I think the artists are used to working with English tools. We do however summarize and translate parts of the client supplied docs and also have hands-on training sessions. Translating the tools themselves would probably take more time than we can fit into our busy schedule.</p>
<p>Thanks Rob for putting the spotlight on this topic!</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
