[daniel klein]

But my understanding could be wrong, and so perhaps Mohammad could list some data from a toy dataset and show the output from tabulate (or whatever command) that illustrates the problem for everyone to be clear in understanding.

Perhaps, Mohammad can start his own thread for this, as it is really getting off topic here. Someone with the same or similar problems is unlikely to search the archive for "Stata 15 is here" in the future.

Best
Daniel

[Joseph Coveney]

The way I understood it, Persian is written right-to-left and, although the text is stored in the dataset correctly, when Mohammad executes a tabulate command on the variable, in the display of the text in the Results window is reversed, left-to-right. I played around with some Persian text (using simple translations copied and pasted into a string variable from Google Translate), and I did not find such a phenomenon to happen with tabulate. The direction of the text did not appear to be altered.

But my understanding could be wrong, and so perhaps Mohammad could list some data from a toy dataset and show the output from tabulate (or whatever command) that illustrates the problem for everyone to be clear in understanding.

[Marcos Almeida]

If I understood right, I fear that 'reverting the order' in #31 just means keeping the alphabetical order. What is more, it seems to be unrelated to how unicode in Stata 'treats' Pearsian language. Among the strategies to keep the previous reference level, the factor notation 'ib#." may do the trick.

[Mohammad Shoaib]

Thank you Sergiy and Joseph,

Sergiy Radyakin, It is possible to import a Persian language text in to Stata 14, for example I import the data set from Ms. Excel into Stata 14 it works perfect. But what is not working well, let me give you an example, assume that I have a data set in Persian language and it has variable (gender) and it is a string variable (Male and Female) when I check the data in data editor it looks fine and in good shape (Male and Female) but when I do a tabulation in result window it shows the the out put different in revers order it shows the Male "elaM" and Female "elameF".

Thank you again,




,

[Sergiy Radyakin]

Mohammad Shoaib could you please elaborate on the import/export of the Persian language:

It is not working very well in Stata 14

Thank you, Sergiy

[Joseph Coveney]

Assuming that you're talking about a delimited text file, import delimited in Stata 14 should be able to import a file containing Persian language if it is encoded in one of the encodings that Java uses. See help import delimited for more information about which encodings are available.

[Mohammad Shoaib]

Is it possible to in Stata 15 to import data in Persian language? It is not working very well in Stata 14.

[Richard Williams]

I'm very interested in the markdown module to create html and docx. Do I need a full upgrade just for this feature? Thanks.

If you do -findit markdown- various user written routines show up. I don't know they compare with what is in Stata 15.

[Emmanuel Segui]

I'm very interested in the markdown module to create html and docx. Do I need a full upgrade just for this feature? Thanks.

[Alan Riley (StataCorp)]

I noticed that the download page only allows five downloads of the software while it seems to be the default option. I am not certain this is introduced now or has been introduced at some earlier version already.

This struck me as inconvenient as I am not sure how often I will use this download option. Of course, I can download and archive the installation file(s), but is it necessary? It would be quite easy to fix, but I might overlook the underlying reason or overestimate the nuisance to the user.

This isn't a new limit. The idea is that if you accidentally leave your download information where someone else sees it, an entire class won't accidentally download your copy. If you run into an issue with the limit though, just email us and our sales group is happy to reset it.

[Ben Kriechel]

Another thing.

I noticed that the download page only allows five downloads of the software while it seems to be the default option. I am not certain this is introduced now or has been introduced at some earlier version already.

This struck me as inconvenient as I am not sure how often I will use this download option. Of course, I can download and archive the installation file(s), but is it necessary? It would be quite easy to fix, but I might overlook the underlying reason or overestimate the nuisance to the user.

--- Ben

[Dave Airey]

Respectfully, I had different feelings about this release. Nonlinear mixed models. Thank you. Groups in generalized SEM. Thank you. Bayes prefix. Thank you. Better reporting built in. Thanks again. Anyway, it's good to get different thoughts on this release as clearly you were disappointed across some issues of workflow / ease of use.

Dave

I'm sorry to say that on the face of it, this looks like a very disappointing release.
Most of these additions would better be charcaterized as simmilar to user addons than what I would expect from stata itself. It also seems to ignore most if not all of the suggestions and requests made by avid stata users in this very forum. I understand of course that statacorp can't do everything and please everyone, but It seems to me like there's ignorance of what users want and wish.
I would name a few, broad issues that I and others have mentioned and that should've been dealt with on the software level:

1. Interface and results window: The coercive abbreviation of output (of long variable names etc.) - At least give users the ability to decide whether or not they wish to abbreviate (the infamous ~) output.

2. No multi-core support in non-MP versions: Other stat software support multi-core (which is standard in computers now days, and has been for sometime) natively. The price differentiation between MP and non-MP flavors prevents users from utilizing the speed benefits of multi cores. A single "flavour" that utilizes multi cores, I think, is a long time coming.

3. Limited number of variables - while this has increased, there have been several discussions on this very forum how today's "big data" (or even "medium data") sets can have hundreds of thousands of variables. The current limit is not big enough for 2017 and many users (not in my field, btw) would not use stata due to this reason.

4. Better debugging - Being unable to even set a breakpoint in a do file can be extremly frustrating. debugging programs in stata is more art than sciense, with the user writing nonsense code where I want to program to stop (as it will exit due to error) just to "break" at a given time.

5. Incorporating general-use addons into vanilla stata - User addons are great, but I would have expected statacorp to work with package authors to get their packages into native stata. Packages that a large percentage of users use daily, and that even appear on the stata FAQ. such as outreg/estout, spmap, ivreg2 etc.

6. Working with several databases at the same time - I understand that this will mean a major shift in stata-philosophy, but since other stat software to this at ease, I see no reason for stata not to have this pretty basic feature - Instead the user has to juggle with multiple instances of stata, or keep clearing and using each dataset separately.

7. Speed improvements - I see very little mentioning of "under the hood" improvements, for example - are there not still built-in stata commands which have not yet been mata-ized?

[eric_a_booth]

Stata/IC (14 or 15) can read any dataset created with Stata/IC (14 or 15), Stata/SE (14 or 15), or Stata/MP (14 or 15) so long as the dataset has no more than 2,047 variables.

Stata/IC (14 or 15) can read subsets of variables from datasets created with Stata/IC (14 or 15), Stata/SE (14 or 15), or Stata/MP (14 or 15) so long as those datasets have no more than 32,767 variables.

Stata/SE (14 or 15) can read any dataset or subset of variables from datasets created with Stata/IC (14 or 15), Stata/SE (14 or 15), or Stata/MP (14 or 15) so long as those datasets have no more than 32,767 variables.

If a dataset has 32,768 or more variables, it must have been created by Stata/MP 15, and only Stata/MP 15 can read it.

Edit: and, to be clear, of course versions 14 and 15 of Stata/IC, Stata/SE, and Stata/MP can read all earlier Stata dataset formats created on any platform, all the way back to the first version of Stata 30-odd years ago.

Thanks Alan for this information.
I was also curious about a condition where I have a large >32768 variable dataset managed in MP that I want to send to a collaborator with SE. I wanted to know whether the internal 119 version you describe would persist if I reduced the dataset (thereby making the file unreadable to an SE version even if it had less than 32k vars), and separately whether the SE version could open a subset of the large file created by MP (via use varlist using file.dta).

The example below shows that a large >32768 variable file created by MP cannot be accessed by SE using a subset of the data and also that when the large file is reduced to >32k vars then the internal id changes back to 118 and is readable by SE (I was able to -use- this with Stata 15 SE and Stata 14 SE on mac and windows).

Output from this test:

. cap program drop whatversion

. program define whatversion 
  1. syntax anything
  2.                 file open handle using "`1'", read text
  3.                 file seek handle 28
  4.         file read handle test
  5.         file close handle
  6.                 noi di as smcl `"For file: `1'"'
  7.                 noi di as smcl `"Header: `=substr(`"`test'"', 1, 3)'"'
  8. end

. 
. 
. 
. **test small file first
. global mydir `"/users/ebooth/desktop//"'

. sysuse auto, clear
(1978 Automobile Data)

. sa `"${mydir}/test.dta"', replace
file /users/ebooth/desktop///test.dta saved

.         whatversion `"${mydir}/test.dta"'
For file: /users/ebooth/desktop///test.dta
Header: 118

. 
.         
.         
. **more than 35000 vars
. clear

. set maxvar 36000


. set obs 100
number of observations (_N) was 0, now 100

. forval n = 1/35000 {
  2.         g var`n' = 1
  3.         }

.         desc, sh

Contains data
  obs:           100                          
 vars:        35,000                          
 size:    14,000,000                          
Sorted by: 
     Note: Dataset has changed since last saved.

. sa `"${mydir}mpfile.dta"', replace
file /users/ebooth/desktop//mpfile.dta saved

.         whatversion `"${mydir}mpfile.dta"'
For file: /users/ebooth/desktop//mpfile.dta
Header: 119

. 
.         
. u var1-var10 using `"${mydir}mpfile.dta"'

. sa `"${mydir}mpfile_extract.dta"'       , replace
file /users/ebooth/desktop//mpfile_extract.dta saved

.         whatversion `"${mydir}mpfile_extract.dta"'      
For file: /users/ebooth/desktop//mpfile_extract.dta
Header: 118

[Richard Williams]

If a dataset has 32,768 or more variables, it must have been created by Stata/MP 15, and only Stata/MP 15 can read it.

I was kind of disappointed with 14MP. By far my biggest jobs use sem and MP didn't seem to speed them up. But 15MP is a little cheaper I think and this monstrous number of variables ability could make it more attractive to some people.

[Alan Riley (StataCorp)]

Stata/IC (14 or 15) can read any dataset created with Stata/IC (14 or 15), Stata/SE (14 or 15), or Stata/MP (14 or 15) so long as the dataset has no more than 2,047 variables.

Stata/IC (14 or 15) can read subsets of variables from datasets created with Stata/IC (14 or 15), Stata/SE (14 or 15), or Stata/MP (14 or 15) so long as those datasets have no more than 32,767 variables.

Stata/SE and Stata/MP (14 or 15) can read any dataset or subset of variables from datasets created with Stata/IC (14 or 15), Stata/SE (14 or 15), or Stata/MP (14 or 15) so long as those datasets have no more than 32,767 variables.

If a dataset has 32,768 or more variables, it must have been created by Stata/MP 15, and only Stata/MP 15 can read it.

Edit: and, to be clear, of course versions 14 and 15 of Stata/IC, Stata/SE, and Stata/MP can read all earlier Stata dataset formats created on any platform, all the way back to the first version of Stata 30-odd years ago.