LuaLaTeX shouldn’t affect your document too much. The main thing you’ll have to change is the preamble. There’s no need to load packages like fontenc or inputenc. LuaLaTeX supports UTF-8 by default, so you should encode your files with UTF-8 (this should be possible with TeXStudio). Instead of having a preamble like
\documentclass{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
there now is the package fontspec to set the document’s fonts:
\documentclass{article}
\usepackage{fontspec}
\setmainfont[Ligatures=TeX]{Linux Libertine O}
\setsansfont[Ligatures=TeX]{Linux Biolinum O}
and so on. Please read the documentation of the fontspec package for details on this. Also the LuaTeX reference might be useful, as well as Manuel Pégourié-Gonnard’s Guide to LuaLaTeX, which I really recommend reading. It basically gives you the main differences (see p. 3 of the PDF file):
- Don’t load
inputenc; just encode your source in UTF-8.
- Don’t load
fontenc or textcomp; load fontspec.
babel works with LuaLaTeX but you can load polyglossia instead.
- Don’t use any package that changes the fonts; use
fontspec commands instead.
Basically, everything that works with normal pdfTeX should also work with LuaTeX, but be aware that LuaTeX is still in development and it could change from release to release. For distinct questions and problems, please have a look around this website for an answer to your question, or ask a question yourself.
\immediate\pdfobjsyntax clearly only works for pdf/lua tex but there should be an equivalent\specialfor xdvipdfmx I would have thought. It's only just including some literal pdf code at that point. – David Carlisle May 06 '15 at 10:07