Special notes for LaTeX users
If you are writing with LaTeX (which is a good idea!) please observe the following guidelines:
- Use the standard features of LaTeX2e as documented in Leslie Lamport's original manual LaTeX: A Document Preparation System. If you can't afford that, Tobias Oetiker's ... Introduction to LaTeX2e is free and helpful.
- Use Unicode encoding for your files (i.e., for XeLaTeX or LuaTeX).
E.g., type Kṛṣṇācārya, not K\d{r}\d{s}\d{n}\={a}c\={a}rya or kRSNAcArya or any other workaround. Type Unicode. - Use the standard article class, \documentclass{article}.
- Use logical markup, not presentational markup. That means you mark things as \chapter{xxx}, \section{xxx}, \footnote{xxx}, \emph{xxx}, \title{xxx}, etc., rather than \textbf{xxx}, \vspace{5ex}, or {\it xxx\/}.
- Do not make private commands using \newcommand or \def. If this appears to be unavoidable, please contact the journal editor before proceeding.
- Provide your bibliography entries in BibTeX format. Sites like text2bib can help convert plain text into BibTeX format.
The journal uses BibLaTeX, which is flexible. So please do not use any special formatting commands or non-standard bst files. Just use \cite{xxx} and other standard commands in the simplest manner. Internally, the journal uses OxRef to produce Hart's Rules formatting. If you want to get into BibLaTeX a bit more, there's a cheatsheet and a useful short intro. - If you have tables, keep them simple, and don't spend time putting in many horizontal and vertical lines. They will be reformatted for the journal, in any case.
- If you are a LaTeX wizard, you could try fetching the HSSA LaTeX class and style packages from Github. Follow the guidelines in section 1 of the documentation and use the template to start off your article. But using the standard LaTeX article style is fine and perhaps even a better idea unless you have very special requirements.
- Use the XeLaTeX engine and Polyglossia. Do not use LuaTeX or Babel without contacting the journal's editor first.