Using STATA to create coding file and export it as txt - what are the requirements for the txt format of a coding file? Text-delimited or something else? #1138
Unanswered
talk100
asked this question in
2.2 Q&A (in English)
Replies: 2 comments
-
Please see the manual section A.2.5 or example coding file: codes_from_tag2.txt. We call this a "coding rule file" and it's a text file. And I don't use STATA and I am not sure about it. |
Beta Was this translation helpful? Give feedback.
0 replies
-
If someone needs to use STATA to generate txt file for khcoder, I figured it out. the STATA command for extracting variable "var" is In this case, the txt file is extracted in plain text file and it is perfectly readable in khcoder on Mac. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Version number of KH Coder
the latest version
Your Qeuestion
Your Operating System
Mac OS
Your Question
I use STATA to create a coding file and STATA has options for exporting txt files. what are the requirements for the txt format of coding files? Is it text-delimited as described here https://www.stata.com/features/overview/importing-and-exporting-text-delimited-data/ or something else? I just want to ensure that I choose the appropriate format for the txt file when exporting it from STATA.
What language of text are you trying to analyze?
English
Beta Was this translation helpful? Give feedback.
All reactions