Editing a Code-Switched and Archaic Short Story Collection

My policy would separate dialogue from narration. In dialogue, preserve code-switching because it characterizes speakers and reflects real Manipuri speech in multilingual Assam; removing English and Assamese words would make urban characters sound unlike themselves. In narration, preserve code-switching only where it carries narrative voice or irony; if the English is merely decorative, the editor may reduce it with the author's consent. For Story B, do not modernize archaic spellings wholesale. First classify them: some spellings may mark historical pronunciation or regional form, while others may be inconsistent typography. Preserve meaningful archaic forms, standardize accidental inconsistency, and annotate only what the reader cannot infer. The trade-off is readability versus historical texture. A student edition should not become a linguistic museum, but neither should it silently rewrite the archive. I would add a short editorial note explaining that spellings have been preserved in Story B where they carry dialect or historical value, and that dialogue retains loanwords because they are part of character speech.

I would not divide 300 entries evenly at 25 per story, because the stories differ in difficulty and cultural density. Criteria should be: frequency of the word across the collection, cultural specificity, and whether meaning is inferable from context. First, build a master list and mark words that recur. Recurring words get one glossary entry and are cross-referenced, saving space. Second, prioritize cultural terms, kinship terms, ritual objects, and regionally specific foods or occupations, because these are least inferable. Third, for words that appear only once and are clear from context, do not gloss. A rough distribution: Story B and the most culturally dense story might receive 45–55 entries each; two code-switched stories might receive 30–35 each because the loanwords need brief glosses; the remaining eight stories share the rest, with simpler stories receiving 10–15 each. Reserve about 20 entries for a back-matter section on recurring terms. This allocation follows need, not equal pages.

I would reply that 'pure Manipuri' is not a describable variety of the language as it is actually used in the stories. Manipuri has long borrowed from Bengali, Assamese, and English, and those borrowings are part of its lexicon and sociolinguistic range. Removing loanwords from dialogue would not purify the text; it would misrepresent the characters and the multilingual setting of Assam. The editorial question is not purity but function: does a loanword carry character, setting, or irony? If yes, keep it and gloss it. If it is merely an unnecessary synonym, the author may choose to revise. I would also point out that archaic Meitei Mayek spellings and modern loanwords are not opposites-both are historical layers. The edition can respect the language by editing consistently, not by purging. If the reviewer wants a 'pure' register, the publisher could add a brief appendix on registers, but the stories themselves should not be rewritten to satisfy a purist criterion that the authors did not use.