<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">A translation-oriented categorisation of wordplays</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Michel</forename><surname>Delarchea</surname></persName>
							<email>delarche@noos.fr</email>
							<affiliation key="aff0">
								<orgName type="institution">Université Paris-Diderot UFR EILA 8</orgName>
								<address>
									<addrLine>place Paul Ricoeur</addrLine>
									<postCode>75013</postCode>
									<settlement>Paris</settlement>
									<country key="FR">France</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">A translation-oriented categorisation of wordplays</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">974CD431B84EDD92E304E75E41E732ED</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T03:24+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>wordplay categorisation</term>
					<term>automated wordplay detection</term>
					<term>wordplay translation</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>We show here that it is possible to pragmatically base a wordplay categorisation scheme on the different tools and algorithms needed to support the (more or less) automated detection and translation of wordplays, especially those whose translation by existing generic tools is impossible or inadequate. This approach also provides a way to develop metrics for quantifying the quality of wordplay translations.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>There exist various categorisation schemes for wordplays based either on a non-academic cataloguing of wordplay types (as enumerated in <ref type="bibr" target="#b0">[1]</ref> for example) or on linguistic structures (eg. <ref type="bibr" target="#b1">[2]</ref>, <ref type="bibr" target="#b2">[3]</ref>). In the context of the JOKER project <ref type="bibr" target="#b3">[4]</ref> this working note proposes a different approach, whose scope is however limited to alphabetic languages. Some authors restrict the notion of wordplay to phonetic, semantic and/or syntactic wordplays based on polysemy or homophony (informally known as puns). In this note, we address a wider variety of wordplays. We also suggest additional tools or algorithmic filters for specific subtypes of wordplays.</p><p>The deterministic algorithms described in this note should be viewed as both a description of the heuristic processes at work in human translation activities and an outline specification of heuristic tools aimed at facilitating the detection and translation of wordplays too complex to be confidently delegated to automated translation systems functioning as blackboxes. In this respect, we agree with Miller <ref type="bibr" target="#b4">[5]</ref> in respect of the many pitfalls plaguing a fully automated approach to wordplay translation. However, by contrast with his PunCAT tool (an ongoing development presented in <ref type="bibr" target="#b5">[6]</ref>), our approach, if implemented, would rely on simple searching and matching algorithms operating on (supposedly digitised) traditional dictionaries rather than on database models and engines.</p><p>This note is divided into sections and sub-sections reflecting different structural types of wordplays. Each (sub-)section contains:</p><p>1. a definition of the type of wordplay it addresses, 2. a list of tools needed for automating the detection and translation of the wordplays, 3. an informal description of the algorithms to be used, 4. a short discussion of quality assessment metrics.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>2.1.</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acronyms</head><p>Acronyms are utterable pseudo-words (or real words) consisting of the first letters of a sequence of words. In this note focused at wordplays, we exclude those acronyms that have been turned into common words, like 'radar' (radio detection and ranging) or 'scuba' (self-contained underwater breathing apparatus) or that are never translated like "the SALT agreements" ("les accords SALT") or "the BBC" ("la BBC"). Acronyms for international organisations admit internationally standardised translations like NATO=OTAN or WHO=OMS and are not concerned either.</p><p>When acronyms are meant as wordplays, like the TWIT ("True Worshippers of the Ineffable Tetractys", a pseudo-Pythagorician sect invented by Thomas Pynchon in <ref type="bibr" target="#b6">[7]</ref>) or the MOU ("Mouvement Ondulatoire Unifié" a mock political party created by the French humourist Pierre Dac <ref type="bibr" target="#b7">[8]</ref> in 1965) they are always written in capital letters (sometimes separated by full stops), which makes their detection extremely simple, providing the established acronyms described in the previous paragraph be filtered out. There may be some semantic relation between the stand-alone meaning of the acronym and its developed form, but is it not necessarily the case (as shown by the ALICE acronym below, certain acronyms may sound playful per se. independently from the meaning of their developed form.)</p><p>The translation of acronyms requires the following tools: a a source-to-target language dictionary (STLD) to determine the meaning of the acronym and also of its component words in the target language. A dictionary of names (DoN) would also be necessary because some acronyms are based on names, like the mnemonic ALICE (Alert, Lockdown, Inform, Counter, Evacuate).</p><p>To initiate the translation process, a list of acceptable translations in the target language for each component word can be determined e.g. in the case of TWIT, with French as the target language, Vrai(e), Véritable, Authentique, Certain(e), Incontestable, Juste, Loyal(e), Réel(le) etc for 'True', Servants, Adorateurs, Disciples, Sectateurs, Dévots, Croyants, Zélateurs etc for 'Worshippers' etc.). 'Ineffable' does not need to be translated, neither does 'Tetractys'. Then, starting from a meaning of the acronym (IDIOT or ABRUTI for TWIT and SOFT or LIMP for MOU) a candidate selection algorithm would try to match one or more acceptable translations with the successive letters of the target algorithm: Incontestables Dévots/Disciples de l'Ineffable Tetractys provide 4 matches out of the 5 needed for IDIOT, which is a good starting point for the human translator (selecting some adjectives starting with O, like Optimal or Original, would provide some additional assistance). For ABRUTI, our lists of synonyms would allow for a partial correspondence only: Authentiques B R U du Tetractys Ineffable.</p><p>Translating MOU into SOFT with the same synonym-matching algorithm would pick matches from three lists, the first one containing Association, League, Move, Organisation, Party etc. for 'Mouvement', the second one Fluctuating, Ondulating, Oscillating, Tremulous, Wavy etc. for 'Ondulatoire' and the third one Coalesced, Federated, Integrated, Merged, Unified, United etc. for 'Unifié'. Matching OFT with Organisation of Federated Tremulations and LIM with League of Integrated Moving would each provide a useful starting point: the end points could be Social/Special Organisation of Federated Tremulations and League of Integrated Moving Parties, respectively. (The resulting acronyms are baroque assemblies of words, very much like the original ones: achieving fully rational meaningfulness is not really essential in this kind of exercise.)</p><p>As implicitly shown by the above proposed algorithm, the quality criteria of the translation of an acronym are:</p><p> respecting the semantics of the source acronym,  minimising the difference in length between the source and target acronyms,  respecting the semantics of the developed acronym (allowing for some permutations and/or derivations of the target words). It is now possible to build up quantitative metrics reflecting these three criteria. For example, allocating N points for fully respecting the semantics of a source acronym of length N, adding 1 point for each target word matching a source word and subtracting 1 point for each non-matching target word would linearly aggregate the three criteria, with a higher weight granted to the meaning of the whole acronyms. Applying this metric to IDIOT vs TWIT, we get: 4 source letters + 4 words matching the source words -1 non matching word = 7.</p><p>For ABRUTI we get only: 4 source letters + 3 matching words -3 non-matching words = 3. According to this metric, IDIOT is a better translation of TWIT than ABRUTI.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2.">Acrostics</head><p>An acrostic is a poem (resp. a piece of prose) where the selection of the first letters of successive verses (resp. sentences or paragraphs) produce either a single word (frequently the name of the addressee, like ELIZABETH in an acrostic by Edgar Allan Poe <ref type="bibr" target="#b8">[9]</ref>, but it may be a common noun or infinitive verb form) or a multi-word expression. We denote these two subtypes of acrostics as name acrostics and multi-word acrostics, respectively.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2.1.">Name acrostics</head><p>The only tool required for the detection of name acrostics is a dictionary of names (DoN). Building up the relevant letters into a string of characters and then checking the result is so simple it can hardly be termed an algorithm.</p><p>Translating name acrostics would require an additional tool: a STLD. The translation algorithm would start from the word in the source text associated with the first letter of the name, then find its translation(s) into the STLD. If a translation starts with the same letter, we have a good candidate. We can look for the translations of subsequent words in the first verse to find other candidates. For example, in a translation from English into French, if the name is IRIS, 'Intense' as the first word of the first verse would be an obvious candidate since it also exists in French. If we find the word 'here' in the rest of the verse, 'Ici' would be another candidate for the French version.</p><p>Repeating the process for each verse, we get a set of possible starting points that would be heuristically helpful to the human translator. As regards the quality metrics for a name acrostics, respecting the name is the key quality factor (replacing IRIS by IRMA would get only a 50% mark).</p><p>This simple metric could be refined by comparing the selected target candidates with the source text: for example, 'Ici' would be a better candidate than 'Incongru' for translating an acrostic starting with 'Iffy'.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2.2.">Multi-word acrostics</head><p>Multi-word acrostics would require a more combinatorial algorithm to determine the sequence of words by splitting the acrostic string at all the right places (starting with a list of potential first words, then a list of potential second words for each potential first word and so on). At the end of the process a shortlist of solutions can be proposed to the user. Including some syntactic rules, e.g. that in Western European languages "definite determiners (the, le, la, les, der, die, das, el, los, gli, etc.) should be followed by a noun or an adjective" in the algorithm would further narrow the list of plausible results.</p><p>Translating a multi-word acrostic would involve the same kind of candidate selection algorithm as previously described for name acrostics. The quality metrics that may be developed for multi-word acrostics are also the same.</p><p>We can see that, by comparison with name acrostics, the detection of multi-word acrostics requires an additional tool (an SLMD). It also requires a specific string segmentation algorithm.</p><p>In our approach, these two differences justify the use of distinct categories for these two types of acrostic. However, the candidate selection algorithm and the STLD to be used for supporting the translation process are the same for both.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Some polysemic constructs</head><p>Polysemic wordplays rely on some polysemic keyword(s), that is a word or a set expression that can have two (or more) different senses. In such wordplays, the keyword or set expression is used in a context where its different possible senses constitute the wordplay. The script-based General Theory of Verbal Humour developed by Attardo and Raskin <ref type="bibr" target="#b9">[10]</ref> proposes a formal model for characterising such semantic disjunctions and Low <ref type="bibr" target="#b10">[11]</ref> has listed the generic strategies used by translators (including the ultimate option of leaving a pun untranslated); he also described step-by-step transformation mechanisms operating in the source language and/or the target language so as to support a systematic approach to the translation process by finding semantic approximates.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1.">Single pivotal keyword</head><p>The structure of these wordplays involves a single pivotal keyword, for which the upstream context points at one of the possible meanings while the downstream context leads to another interpretation:&gt; "I took several sick leaves last year, because the trees were suffering from the drought."</p><p>The pivotal word is 'leaves'. The beginning of the sentence seems to be about taking a sick leave several times, while the end of the sentence makes sense only if more than one sick leaf has been gathered from the trees. The same structure can be instantiated through a short dialogue featuring a non sequitur:</p><p>"-Je suis allé à la boulangerie, et j'ai pris de la brioche.</p><p>-Pour t'en débarrasser, fais un peu de sport !" In a lazy English translation, the answer seems irrelevant: "-I went to the bakery, and I took some brioche.</p><p>-To get rid of it, do a little sport!" Here 'brioche' is the pivotal word with a dual interpretation. This is because the sentence: "j'ai pris de la brioche" can be interpreted colloquially as: "I've developed /a paunch/a corporation/" "I've got a bit of a tummy" (these three translations are provided in <ref type="bibr" target="#b11">[12]</ref>) Since the colloquial expression "prendre de la brioche" can be found in an STLD, the double entendre can be detected by scanning the upstream context, as 'bakery' points at the proper meaning of the word 'brioche'.</p><p>After detecting 'brioche' as the pivotal keyword, it is possible to check which translations of this pivot may accept several interpretations; neither 'tummy' nor 'paunch' meet this requirement. but 'corporation' would allow the human translator to devise some approximate equivalence, since the word 'corporation' can designate either a commercial company or a potbelly:</p><p>"-I started a small business then I developed a corporation.</p><p>-To get rid of it, do a little sport!" This kind of creative translation cannot be obtained from the deterministic algorithms we are discussing here, but identifying automatically the word 'corporation' as a candidate pivotal word in English would be quite helpful to the human translator. The quality criteria (and hence the quality metric) for the automated part of the process would be:</p><p> the correct identification of the pivotal keyword and  the identification of good candidates for the role of pivotal keyword in the translation (at least one of the two meanings involved in the wordplay should be kept by each candidate).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2.">Repeated keyword with different meanings</head><p>Another construct consists in repeating a word in a sentence with a different meaning. Assigning a correct meaning to each occurrence is also a matter of context analysis.</p><p>The identification of repeated words is easy. To decide whether a repeated word can be listed as a potential polysemic keyword, the first tool to be used is an SLMD. If the dictionary contains different possible meanings for the word, the next step consists in determining whether the two occurrences are associated with a single meaning or not.</p><p>In some cases, the context allows for the immediate determination of adequate translations: "L'eau potable c'est bien, mais un vin potable, c'est mieux." Here, we have two occurrences of 'potable' which can be considered as the repeated keyword for this semantic wordplay. In this sentence, the first occurrence of 'potable' is part of the set expression "eau potable" (drinking water), while the second one has the figurate meaning of 'acceptable', 'passable', 'palatable'. The translation of "eau potable" as "drinking water" may be directly available in the STLD (as is the case in <ref type="bibr" target="#b11">[12]</ref>), and the wording "drinkable water" may be concurrently available too.</p><p>Selecting the best translation for "vin potable" consists in reflecting as best as possible the dual meaning of 'potable', and 'drinkable' would be the obvious choice. Using 'drinkable water' would not be erroneous, but associating "drinking water" to "drinkable wine" would capture more accurately the humour in the French wordplay. In that case, the selection algorithm could provide both options for the human translator to make his choice.</p><p>"When the lockdown parties scandal erupted, the conservative party was nicknamed the party of parties".</p><p>This sentence features 4 occurrences of the word 'party', which can therefore be identified as the keyword in the semantic wordplay due to its polysemy.</p><p>Here we have two pairs of occurrences of the noun 'party' the singular ones referring to political party, and the plural ones denoting festive gatherings. Here, a basic automatic translation process may yield erroneous results inter alia because, in many other contexts, "the party of parties" means a superlative feast (as it is a construct similar to such expressions as: "the King of Kings" or "the problem of problems").</p><p>However, associating 'party' to the preceding occurrence 'conservative party' and 'parties' to 'lockdown parties' would select the correct interpretations. And if the context proposed instead some synonyms of these contextual occurrences such as 'the bring-your-own-booze gatherings' or 'the Tories', using a SLMD for exploring the definition part of the corresponding entries, would allow to associate 'party' and 'parties' to their respective meanings.</p><p>In French, 'partie' means 'part', but is also used either in the domain of games, sports and leisure ("une partie de ping-pong", "une partie de chasse") or to denote the genitals ("private parts") in popular language ("il a reçu le ballon dans les parties"). There are also some set expressions like "surprisepartie", "partie fine" whose meanings correspond to the festive gatherings evoked in our example.</p><p>"Le parti conservateur a été surnommé le parti des parties fines" would be a good enough translation. An expression like "partie fine" is unlikely to be given in a bilingual translation dictionary but may be found in a dictionary of idioms (DoI).</p><p>The detection and translation of such wordplays requires both a SLD and an STLD. An extensive Target Language Dictionary (TLD) for finding synonyms and a DoI for detecting colloquial set expressions in either language may also be necessary.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">A few preliminary conclusions</head><p>We have shown that name acrostics and acronyms would fall in the same algorithm-based category, while multiword acrostics would have to be categorised separately (because their require a specific string-to-word segmentation algorithm and an SLMD).</p><p>We have also reached the conclusion that the structural difference between a polysemic wordplay based on a single pivotal keyword and a polysemic wordplay based on the repetition of a keyword need not be ascribed to distinct algorithm-based categories.</p><p>These examples demonstrate that non-trivial wordplay categories can be based on different sets of dictionaries and deterministic detection and translation algorithms.</p><p>It must also be noted that traditional mono-or bilingual dictionaries include most of the linguistic functionalities we have here identified separately in relation with the type of algorithmic processing envisaged: a traditional paper dictionary is simultaneously a semantic domain dictionary (plus some register indications by means of asterisks or other notations), a pronouncing dictionary and also in part a dictionary of synonyms and a dictionary of idioms; it frequently contains annexes describing conjugations or declensions. An approach of computer-aided translation based on the use of matching algorithms operating on digitized versions of those traditional dictionaries might be of interest, especially for the little used languages that are unlikely to ever benefit from the construction of advanced linguistic databases.</p><p>For the sake of brevity, we have not addressed phonemic puns in this paper. In our approach, they would constitute another group of wordplay categories because they would require additional tools such as pronouncing dictionaries. For puns based on phonemic approximates rather that pronunciations that are strictly the same, more flexible matching algorithms would be needed too.</p></div>		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Acknowledgements</head><p>Many thanks to Liana Ermakova for inviting me to submit this note.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">The Game of Words</title>
		<author>
			<persName><forename type="first">Willard</forename><forename type="middle">R</forename><surname>Espy</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Random House</title>
		<imprint>
			<biblScope unit="page" from="448" to="01196" />
			<date type="published" when="1972">1972</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Javakhishvili Tbilisi State University, Tbilisi, Georgia Linguistic features of pun, its typology and classification</title>
		<author>
			<persName><forename type="first">M</forename><surname>Giorgadze</surname></persName>
		</author>
		<author>
			<persName><surname>Ivane</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">European Scientific Journal</title>
		<idno type="ISSN">1857 -7881 e- 1857-7431271</idno>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<date type="published" when="2014-11">November 2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Overview of JOKER@CLEF 2022: Automatic Wordplay and Humour Translation Workshop</title>
		<author>
			<persName><forename type="first">Liana</forename><surname>Ermakova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Tristan</forename><surname>Miller</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Fabio</forename><surname>Regattin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Anne-Gwenn</forename><surname>Bosser</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Élise</forename><surname>Mathurin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Gaelle</forename><surname>Le Corre</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Sílvia</forename><surname>Araújo</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Experimental IR Meets Multilinguality, Multimodality, and Interaction. Proceedings of the Thirteenth International Conference of the CLEF Association (CLEF 2022)</title>
				<editor>
			<persName><forename type="first">Alberto</forename><surname>Barrón-Cedeño</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Giovanni</forename><surname>Da San</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Mirko</forename><surname>Martino</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Fabrizio</forename><surname>Degli Esposti</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Craig</forename><surname>Sebastiani</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Gabriella</forename><surname>Macdonald</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Allan</forename><surname>Pasi</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Martin</forename><surname>Hanbury</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Guglielmo</forename><surname>Potthast</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Nicola</forename><surname>Faggioli</surname></persName>
		</editor>
		<editor>
			<persName><surname>Ferro</surname></persName>
		</editor>
		<imprint>
			<date type="published" when="2022">2022</date>
			<biblScope unit="volume">25</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">CLEF Workshop JOKER: Automatic Wordplay and Humour Translation</title>
		<author>
			<persName><forename type="first">L</forename><surname>Ermakova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Miller</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Puchalski</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Regattin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">É</forename><surname>Mathurin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Araújo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A.-G</forename><surname>Bosser</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Borg</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Bokiniec</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><forename type="middle">L</forename><surname>Corre</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Jeanjean</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Hannachi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Ġ</forename><surname>Mallia</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Matas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Saki</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-3-030-99739-7_45</idno>
		<ptr target="https://doi.org/10.1007/978-3-030-99739-7_45" />
	</analytic>
	<monogr>
		<title level="m">Advances in Information Retrieval</title>
				<editor>
			<persName><forename type="first">M</forename><surname>Hagen</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">S</forename><surname>Verberne</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">C</forename><surname>Macdonald</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">C</forename><surname>Seifert</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">K</forename><surname>Balog</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">K</forename><surname>Nørvåg</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">V</forename><surname>Setty</surname></persName>
		</editor>
		<imprint>
			<publisher>Springer International Publishing</publisher>
			<date type="published" when="2022">2022</date>
			<biblScope unit="volume">13186</biblScope>
			<biblScope unit="page" from="355" to="363" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">The punster&apos;s amanuensis: The proper place of humans and machines in the translation of wordplay</title>
		<author>
			<persName><forename type="first">Tristan</forename><surname>Miller</surname></persName>
		</author>
		<idno type="DOI">10.26615/issn.2683-0078.2019_007</idno>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Second Workshop on Human-Informed Translation and Interpreting Тechnology (HiT-IT 2019)</title>
				<meeting>the Second Workshop on Human-Informed Translation and Interpreting Тechnology (HiT-IT 2019)</meeting>
		<imprint>
			<date type="published" when="2019-09">September 2019</date>
			<biblScope unit="page" from="57" to="64" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Human-computer interaction in pun translation</title>
		<author>
			<persName><forename type="first">Waltraud</forename><surname>Kolb</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Tristan</forename><surname>Miller</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Using Technologies for Creative-Text Translation</title>
				<editor>
			<persName><forename type="first">James</forename><surname>Hadley</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Kristiina</forename><surname>Taivalkoski-Shilov</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Carlos</forename><forename type="middle">S C</forename><surname>Teixeira</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Antonio</forename><surname>Toral</surname></persName>
		</editor>
		<imprint>
			<publisher>Routledge</publisher>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
	<note>To appear</note>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<author>
			<persName><surname>Th</surname></persName>
		</author>
		<author>
			<persName><surname>Pynchon</surname></persName>
		</author>
		<title level="m">Against the Day</title>
				<imprint>
			<publisher>Penguin Press HC ISBN</publisher>
			<date type="published" when="2006">2006</date>
			<biblScope unit="page">9781594201202</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<monogr>
		<author>
			<persName><forename type="first">P</forename><surname>Dac</surname></persName>
		</author>
		<title level="m">Le parti d&apos;en rire : Pierre Dac président !</title>
				<imprint>
			<publisher>Cherche Midi</publisher>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<monogr>
		<title level="m" type="main">ca) in The Complete Poetry of Edgar Allan Poe</title>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">A</forename><surname>Poe</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Elizabeth</forename></persName>
		</author>
		<imprint>
			<date type="published" when="1829">1829. 1996</date>
			<publisher>Signet Classic ISBN</publisher>
			<biblScope unit="page">9780451526403</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<title level="m" type="main">Script theory revis(it)ed: joke similarity and joke representation model</title>
		<author>
			<persName><forename type="first">Salvatore</forename><surname>Attardo</surname></persName>
		</author>
		<author>
			<persName><surname>Raskin</surname></persName>
		</author>
		<author>
			<persName><surname>Victor</surname></persName>
		</author>
		<idno type="DOI">10.1515/humr.1991.4.3-4.293</idno>
		<ptr target="https://doi.org/10.1515/humr.1991.4.3-4.293" />
		<imprint>
			<date type="published" when="1991">1991</date>
			<biblScope unit="volume">4</biblScope>
			<biblScope unit="page" from="293" to="348" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Translating Jokes and Puns</title>
		<author>
			<persName><forename type="first">Alan</forename><surname>Peter</surname></persName>
		</author>
		<author>
			<persName><surname>Low</surname></persName>
		</author>
		<idno type="DOI">10.1080/0907676X.2010.493219</idno>
	</analytic>
	<monogr>
		<title level="j">Perspectives: Studies in Translation Theory and Practice</title>
		<idno type="ISSN">0907-676X</idno>
		<imprint>
			<biblScope unit="volume">19</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="59" to="70" />
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<author>
			<persName><forename type="first">B</forename><forename type="middle">T</forename><surname>Atkins</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Duval</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">C</forename><surname>Milne</surname></persName>
		</author>
		<title level="m">Dictionnaire Français-Anglais et Anglais-Français</title>
				<meeting><address><addrLine>Paris ISBN</addrLine></address></meeting>
		<imprint>
			<publisher>SNL Le Robert</publisher>
			<date type="published" when="1978">1978</date>
			<biblScope unit="page">2850360082</biblScope>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
