Beginning with v 0.9.12, LDSql supports MLS languages other than English.  The first such language to be supported is Spanish.

To use files exported from MLS when MLS is set to Spanish, first you must detect and use the four core export files corresponding to the English filenames Membership.csv (Miembros.csv), Organization.csv (Organizacion.csv), HomeTeaching.csv (OrientFam.csv) and VisitingTeaching.csv (MaestraVisit.csv). 

Those filenames, and the column names at the top of each file, are documented here:

https://tech.lds.org/wikildstech/images/5/5c/MLS-Export-Languages.xls

Internally, LDSql will still use the English column names.  So the simplest thing to do is use the positions of the columns rather than thecolumn names.  Alternately, one could take the Spanish CSV files and copy the first header line from an English MLS export file.

Once that is handled by whatever method, the MLS_Export_Ward.db database can be populated.

Assuming that the LDSql_Ward.db has been created by the script Create_LDSql_Ward.sql (which defaults to English as the current language), one thing remains to be done before running Populate_LDSql_Ward.sql.  In the LDSql_Ward.db database, execute the following single SQLite statement:


Then the Populate_LDSql_Ward.sql script will execute correctly and load the Spanish data.

It is even possible to load the database with English MLS files and then set the Language to Spanish with such an UPDATE command.  Or in reverse, Spanish MLS export files can be loaded as above, and the statement


will then toggle the query output back to English.