15

3

Possible Duplicate:
Feature Request: Ability to force Kiln to treat specific file types as text regardless of encoding

Currently, if files in repository are not unicode-encoded, localized strings won't show up correctly in kiln web ui. For example, here is a Windows-1251 encoded file:

alt text

We need an option to choose an encoding to correctly view such files. With unicode, of course, still being default selection.

I think, this is needed somewhere in the view file page, because global option would not be enough if files in repositories are in different encodings. The same file, if I could pick the encoding would display correctly:

alt text

flag
opened case FC2313213 – adambox♦ Jul 5 at 19:35

closed as exact duplicate by Kevin Gessner♦♦ Mar 14 at 17:12

1 Answer

2

Thanks for suggestion! We have a feature request filed and will consider this for a future release.

link|flag
We are top 50 already :) – Alexander Gornik Jan 30 2012 at 19:50
WOW! Interesting, only if you got 100 votes you'll start considering international customers as important? This has already caused a serious problem for us in production because KILN was also corrupting the characters in the the downloaded files, and many of our home-pages texts were corrupted and a LOT of messages shown to end-users ended up corrupted. The entire dev-team was up for a scolding session because of KILN messing things up. This is not a feature, this is a BUG. I won't vote for this as a matter of principle, you should be sensible enough to determine what is important. – Felipe Machado Jul 4 at 19:53
1) I accidentally posted our fogbugz.stackexchange.com response. We have scripts which monitor that site and update our cases in fogbugz with the vote counts. The high traffic of that site makes votes a good proxy for what is important to the community. This site gets less traffic, so the process is different. If you send us an email at customer-service@fogcreek.com, we will make sure that engineering knows about your needs. 2) It's the top 100 requests by votes, not requests with 100 or more votes. That would be far too high a bar indeed! – adambox♦ Jul 5 at 19:28
update: we do have a case open with engineering, but it is not a priority as we have standardized on UTF8 in Kiln. UTF8 handles all languages and is the preferred encoding. – adambox♦ Jul 6 at 15:11

Not the answer you're looking for? Browse other questions tagged or ask your own question.