To do it "right", however, as we feel we did with unicode translate for the extended-ASCII-to-Unicode conversion, is a bit tricky. It is certainly possible to write a command similar to unicode translate which would convert all strings/labels/names in a Stata 14 dataset back to some extended ASCII encoding. To my mind this means that it is hardly impossible to expand the capability of unicode translate or saveold to make some "reverse translation". Does anybody have a solution?Īctually, Stat/Transfer 13 does the trick it can translate a Stata 14 dataset to Stata 13, including translation to extended ASCII. The problem will arise when we cooperate with or teach persons who don't have Stata 14. unicode translate lets you translate from extended ASCII to Unicode, but the reverse is not possible.Īt least, this is how I understand the possibilities. With the improved saveold command, Stata 14 can generate a dataset which can be opened by Stata 11 to 13, but legibility is poor. But there is a problem with the switch to Unicode for languages that so far used extended ASCII for some characters (German, French, Spanish, Portuguese, Danish, Norwegian, Swedish, Icelandic, Polish, Turkish, etc.).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |