rthree-developers

[Tim H. <tim...@me...>]

I noticed an issue with r3 relating to mixed cases in dimension entity  
names.

Scenario

	I setup r3 to work on a site we have and initially created an intl  
entity called "en-gb",  after creating some targets and tagging them,
	I created an XLIFF file for the translations, and discovered that the  
tool i was using did not recognise the intl becuase it was expecting
	"en-GB".

	So I thought since i have no specialisation's in this dimension yet,  
i will just delete this entity with "r3 dimension intl delete en-gb"  
and create
	an new one called "en-GB" instead. Having done that, everything  
seemed to work , however when I went to generate an output target I  
got the error

		Cannot find intl#en-gb

	(interestingly if i did an "r3 gen -a") it seemed to work, I only get  
the error when doing a gen on a specific locations such as "r3 gen  
producta/en-US/mockpage.php",
	The use of en-US is not a typo, this is because i get the same error  
about en-gb regardless of which intl entity i try to generate  
against.  I suspect this is because its the
	first of the mislabled entries in the tum table.

	Looking thought the sqllite database the only reference I can find to  
the deleted intl entity is in the "tum" table, where there are  
container_start entries that still have the
	older (lowercase) enity name.  In fact there are a mixture of entries  
in that table that contain both en-gb and en-GB in the container start  
feilds.

	Its also of note is the the generated output in htdocs has "en-gb" as  
the folder name for the intl, not "en-GB", which is not an issue on  
windows or Mac OSX which are case
	insensative, but is certainly a problem on linux/unix.