Historiographia Linguistica

• Back to: HL submission information page
• Go to: Files
• Go to: Elements of the article
• Go to: Layout/style

Historiographia Linguistica welcomes submissions in line with the aim and scope of the journal. These submissions should be unique, not have been published before, and not be under simultaneous consideration elsewhere. Article submissions will be assessed for possible publication through a process of blind peer review; for this purpose, in your initial submission, please make sure to leave out any information that identifies the author(s).

Before sending a manuscript, contributors should familiarize themselves with the style adopted in HL and outlined below, as manuscripts deviating significantly from its conventions may be returned without being evaluated for their contents. Particular attention should be paid to the conventions employed in the presentation of data and the citation of sources.

If your article is accepted after peer review and revision, the journal editor(s) will ask you to provide a final version of the manuscript. This final version should be prepared in line with the instructions below, and should also include the information on the author(s) and their affiliation(s), etc. When submitting this final version, make sure that those files are the correct, complete and copy-edited, final versions only. Please delete any personal comments/notes; any instructions for the typesetters should be supplied separately.

Files

Please make sure that you supply all text and graphic files of your contribution.

Text files in .docx are preferred.

In addition, you must also provide a PDF file of the text, with embedded fonts. This serves as 'hard copy' and should display any special characters, tables etc. as they are intended to look.

Any graphics created in Word (or Excel or such) can remain in their location in the text file and do not require special action. Graphics that have been created in another program, such as special purpose graphics software, and any other illustrations, should be supplied separately. For photos or plates we recommend a resolution of 600 dpi (at the very minimum 300 dpi) at the required size.

When naming the files please use a clear and consistent file naming convention, that allows us and the typesetters to identify the article/review easily. We suggest using the (first) author’s surname. E.g., for an article or review written by Joe Johnson, the files should be named johnson.docx, johnson.pdf. Figures can be named as follows johnson-fig1.png, johnson-fig2.jpg, etc.

Additional materials: If your article has associated (audio-visual) materials or datasets, the text of the article should refer to those and clearly show with which figure/table etc. that material is associated. If you need Benjamins to host those file online, please inform us of this in a separate note, and provide the files and a list containing the name of each associated file, its type, size, and caption/description. If the additional files are hosted elsewhere, a link – preferably a persistent URL, such as a DOI – should be supplied in the text, Appendix section, and references. This hosting location should be permanent, not a personal website.

Elements of your article

Order of elements in your article

Title: Subtitle
Author’s Name*
Author’s Affiliation*
Abstract
Keywords
Article
(Funding information)*
(Acknowledgments)*
References
(Appendix)
Address for correspondence*

* Any information that could identify the author(s) should be left out until after peer review, and instead be provided to the journal editor(s) separately.

Language

Manuscripts should be checked for language, especially if you are not a native/highly proficient speaker of the language used. The language (variant, cf. British or American English) should be consistent throughout the article.

Formatting

Please use a minimum of page settings. The preferred setting is 12pt with at least 14pt line spacing. The only relevant codes are those pertaining to font enhancements (italics, bold, caps, small caps, etc.), punctuation, and the format of the references. For other elements, it is sufficient if they are consistently formatted and recognizable. Any notational conventions for a particular subfield should be used consistently.

Symbols and special characters

Please use Unicode fonts. If you have to use characters that are not available in Unicode, supply the font with your article.

Transliteration of examples, quotations, references from non-Latin scripts:

• Arabic script must adopt the "DMG-transliteration" (Zeitschrift der Deutschen Morgenländischen Gesellschaft).
• For transcribing Indian (including Tibetan) scripts, internationally acknowledged systems should be used.
• Transcription of Chinese characters (traditional) should follow either the system of Thomas F. Wade or the PRC Pinyin.
• For Russian, Old Church Slavonic, and other languages using Cyrillic script, the conventions adopted in the Linguistic Bibliography / Bibliographie Linguistique are to be followed, with the exception that the velar fricative should be transcribed as x, not ch.
• Greek script does not have to be transliterated.

Title and subtitle

If the article has a subtitle, this should be separated from the title by a colon (unless the main title ends with a question or exclamation mark).

The title and subtitle should use sentence case; that is, only the first character (of the main and of the subtitle) is capitalized, except for proper nouns and other words which are generally capitalized by a more specific rule in the relevant language.

Author’s name and affiliation

In the final article, after review, provide all authors’ names in the order in which they are to appear in the publication. In case of an article with more than one author, please identify one corresponding author.

For each author, give their affiliation(s). The affiliation(s) used should be the affiliation(s) current at the time of doing the research and writing the article. The affiliation should be only the name of the university or institution, in the form that the relevant institution itself has decided upon for international use, followed by the country of that institution. NB. Do not create your own translations of names to match the language of your article, if the institution itself does not provide their name in that language; in that case, use the name in the/a primary language of the institution.

In case of more authors, make sure that it is clear which affiliation belongs with which author.

If you have an ORCID (digital identifier for researchers, https://orcid.org), include this as well.

Abstract

Each article should start off with an abstract of up to 120 words. An abstract should be maximally informative, use the active voice, and include the 4 or 5 most important key words, findings, or implications. It should objectively reflect the purpose and content of the paper. Abstracts should be self-contained: define abbreviations and unique terms, spell out names, and give the context in which the paper should be viewed (e.g., it builds on the author’s previous work, or responds to another publication). Abstracts cannot have references or notes.

If you're article is accepted for publication, you will also be required for provide summaries in English (Summary), French (Résumé), and German (Zusammenfassung) of no more than 120 words each. It is not acceptable to produce these by DeepL, Google Translate, or any other automatic translator; the corresponding author is kindly invited to have the translations checked by native/highly proficient speakers before submitting them with the final manuscript.

Key words

The abstract should be followed by a list of up to 10 key words, separated by commas, that indicate the most important topics, languages or language families, methods and/or frameworks used in the article.

Funding information

If you received funding through a grant for the research that is discussed in the article, provide details on this, including funder name and grant number in a separate section called “Funding information” before (an Acknowledgment section and) the References.

Acknowledgments

We prefer the use of an acknowledgment section at the end of an article, instead of an acknowledgment (foot)note. Acknowledgments of assistance, permissions, etc., other than funding (see above), can be included in this section.

Appendixes

Appendixes should follow the references section. Please refer to the appendix in the main text. If the appendix consists of additional materials that are not included in the (print edition) of the article itself, but hosted online, see also the section on 'Additional materials’ above.

Address for correspondence

In the final version, after peer review, include in the article/book review the full address and email address of the corresponding author. For reasons of privacy, we suggest that this should never be a home address, as this address will be displayed in the publication. If the corresponding author does not have an institutional postal address, only supply an email address.
For our own internal processes (and to provide access to the published article) we also require the email addresses of all co-authors, if applicable; it is easiest for us if you include those in the article, under "Co-author information".

Layout/style

Section headings

Articles should be reasonably divided into sections and, if necessary, into subsections. Please mark the hierarchy of subheadings as follows:

Heading 1 = bold, two lines space above and one line space below.
Heading 1.1 = normal, one line space above and one line space below.
Heading 1.1.1 = italics, one line space above, text on new line.
Heading 1.1.1.1 = italics, one line space above, text on new line. NB. This fourth level is only to be used if absolutely indispensable.

Listings

Should not be indented. If numbered, please number as follows:

1. ..................... or a. .......................
2. ..................... or b. .......................

Listings that run on with the main text should be numbered in parentheses: (1).............., (2)............., etc.

Emphasis and foreign words

Use italics for foreign words, highlighting, and emphasis. Bold should be used only for highlighting within italics and for headings. Please refrain from the use of FULL CAPS (except for focal stress and abbreviations) and underlining (except for highlighting within examples, as an alternative for boldface).

For translations of cited forms in the text use double quotes. E.g., voorbeeld “example”.

Quotations

Text quotations in the main text should be given in double quotation marks. Quotations longer than 3 lines should have a blank line above and below and a left indent, without quotation marks, and with an appropriate reference to the source. For terms or expressions (e.g., “context of situation”) please use double quotes.

Examples

Should be numbered with Arabic numerals (1,2,3, etc.) in parentheses and indented. Each subsequent level in the example (a), (b) gets one indent.

If the glosses should be aligned in the final product, please also align them, with spaces or tabs, in the file submitted for production. For detailed conventions for interlinear morpheme-by-morpheme glosses, please see these Leipzig Glossing Rules for HL.

Full caps for abbreviations in glosses will be changed to small caps during typesetting.

Tables, figures and plates

Tables and figures should be numbered consecutively per article, and be provided with concise captions (max. 240 characters).

All figures and tables should be referenced in the text, e.g. (see Figure 5). References should not be limited to relative indicators such as “as in the table below”, or “in this table: ...”.

If the table or figure is not enclosed in the text file, indicate the preferred position of the table or figure in the text by inserting a line “ Insert (file name) here” at the appropriate position.

The typesetters will place the table/figure at the optimal location given the lay-out of the relevant page, taking into account headings and notes etc. Tables/figures may thus be placed at either the top or bottom of the page on which it is mentioned, or on the following (facing) page.

Tables, figures and plates can be submitted in color, where needed. In tables, keep shading to a functional minimum and for individual cells only.

All tables, plates, and figures eventually have to fit the following maximum area, either portrait or landscape: 12 cm x 20 cm at a minimum resolution of 300 dpi (600 dpi preferred).

Notes in tables and figures should not be regular notes. Please use a table note or a figure note as in the example below. Standard note indicators in tables are ^*, ^**, or ^a, ^b, etc. The note itself is then inserted directly below the table/figure.

To ensure accessibility of the work for readers using text-to-speech tools (for instance, because of a visual impairment), we ask you to add 'alt(ernative) text' to all images. See also this Guidance for al text.

Notes

Notes should be kept to a minimum and not be used for references. Note indicators in the text should appear at the end of sentences, preferably, and follow punctuation marks. If possible, please use the (foot)note option of your word processing program.

References

It is essential that the references are formatted to the specifications given in these guidelines, as these cannot be formatted automatically.

References in the text: These should be as precise as possible, giving page references where necessary; for example (Clahsen 1991:252) or: as in Brown et al. (1991:252).

References section: References should be listed first alphabetically and then chronologically. The section should include all (and only!) references that are actually mentioned in the text. Repeated names should not be replaced by dashes. Journal titles should be written out in full, not abbreviated.
Authors/contributors are encouraged to supply – with a reference, not instead of – the DOI if they happen to have that information readily available.
If other than the original edition is quoted from, this should be made clear in the entry, possibly by a statement added in parentheses at the end (after the publisher's name), or by simply referring to the most recent date of publication of the source (adding the date of the original publication in square brackets right after the new date, e.g., Robins, R. H. 1993[1967]). If a translation is being used, this fact must be stated, with the name(s) of the translator(s) supplied. The date of the original edition should be added in square brackets, right after the date of the translation.

Examples

Book, monograph or collective volume
Baratin, Marc & Françoise Desbordes (avec la participation de Phillipe Hoffmann & Alain Pierrot). 1981. L'Analyse linguistique dans l'Antiquité classique. Vol. I: Les théories. Paris: Éditions Klincksieck.
Budagov, R[uben] A. 1988. Portrety jazykovedov XIX-XX vv. [Portraits of linguists of the 19th and 20th centuries]. Moskva: Izd. "Nauka".
Robins, R[obert] H[enry]. 1967. A Short History of Linguistics. London: Longman; Bloomington, Ind.: Indiana University Press, 1968. (2nd ed., London: Longman, 1979; 3rd ed., 1993; 4th ed., 1997)
Versteegh, Cornelis H. M. [= Kees], E. F. Konrad Koerner & Hans-Josef Niederehe, eds. 1983. The History of Linguistics in the Near East. (= Studies in the History of the Language Sciences, 28.) Amsterdam & Philadelphia: John Benjamins.

Articles in a periodical or collective volume
Auroux, Sylvain. 1986. "Actes de pensée et actes linguistiques dans la Grammaire générale". Histoire Épistémologie Langage 8:2.105-120.
Salmon, Vivian G. 1974. "John Wilkins' Essay (1668): Critics and continuators". Historiographia Linguistica 1.147-163. (Repr. in The Study of Language in 17th-Century England by V. Salmon, 191-206. Amsterdam: John Benjamins, 1979; 2nd ed., 1988.)
Sarmiento, Ramón. 1983. "La gramática académica del siglo de las Luces". Serta Philologica F. Lázaro Carreter natalem diem sexagesimum celebranti dedicata, vol. I: Estudios de lingüística e lengua literaria ed. by Emilio Alarcos [et al.], 571-585. Madrid: Cátedra.

Reviews
Cowan, William. 1983. Review of Arab Linguistics: An introductory classical text with translation and notes by Michael G. Carter (Amsterdam: John Benjamins, 1981). Historiographia Linguistica 10.120-124. https://doi.org/10.1075/hl.10.1-2.11cow