What LaTeX is
A LaTeX table is a tabular environment: a column specification, ampersands between cells and double backslashes at the end of each row.
Academic papers, theses and anything typeset with LaTeX or written in Overleaf.
What Qlik is
A Qlik load script block using LOAD INLINE, which embeds the data in the script itself.
QlikView and Qlik Sense developers.
What changes when you convert LaTeX to Qlik
The tabular body is read, rules are dropped, and escaped characters are unescaped. Text wrapped in textbf or emph is reduced to the text itself.
Suitable for small reference tables. For anything large, load from a file instead.
What carries over from LaTeX to Qlik
LaTeX records 3 things about a table that Qlik has no way to hold.
Qlik wants a type for each column, and LaTeX does not record one, so each column is typed from what its values look like. A column of digits that should stay text - a zip code, a phone number, a leading-zero id - is the usual thing to check afterwards.
LaTeX can hold a value that is itself a list or an object. Qlik has only flat cells, so nested values are flattened into one cell rather than being spread across columns.
A line break inside a cell ends the row in Qlik, so line breaks are replaced rather than carried through.
Anything visual in the LaTeX - weight, alignment, colour, column widths - has no counterpart in Qlik and is dropped. The values are what survives.
This is the direction that recovers structure: LaTeX has no table in it to read, only an arrangement that looks like one, so the rows and columns are inferred rather than read.
The identifier 007 comes out of the Qlik as 007. Reading it as a number would have made it 7, and an id that changes value is worse than one that stays text.
The role "Analyst, data" survives with its comma, in one cell rather than split across two. That is the first thing to check in any converted table, and the usual place a Qlik file goes wrong.
The quotes around Jonah "Jo" Pryce are left as a plain quote character in the Qlik.