<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
	<channel>
		<title>ProZ.com Translation Forums</title>
		<link>http://www.proz.com/forums/</link>
		<atom:link href="http://www.proz.com/forums/" rel="self" type="application/rss+xml"/>		<description>Topic: Glossary terms - wrong case</description>
		<language>en-us</language>
		<pubDate>Sun, 08 Nov 2026 04:06:03 +0000</pubDate>
		<lastBuildDate>Sun, 08 Nov 2026 04:06:03 +0000</lastBuildDate>
		<docs>http://www.proz.com/faq</docs>
		<managingEditor>support@proz.com (ProZ.com Support)</managingEditor>
		<webMaster>support@proz.com (ProZ.com Support)</webMaster>
		<item>
			<title>Glossary terms - wrong case | There is also an individual setting</title>
			<author>Jean Lachaud</author>
			<category>Wordfast support</category>
			<link>http://www.proz.com/post/2910476#2910476</link>
			<pubDate>Thu, 03 Jun 2021 18:02:00 +0000</pubDate>
			<description>&lt;b&gt;Forum:&lt;/b&gt; Wordfast support&lt;br/&gt;&lt;b&gt;Topic:&lt;/b&gt; Glossary terms - wrong case&lt;br/&gt;&lt;b&gt;Poster:&lt;/b&gt; Jean Lachaud&lt;br/&gt;&lt;b&gt;Post title:&lt;/b&gt; There is also an individual setting&lt;br/&gt;&lt;br/&gt;Capitalization can also be set individually for both each source and target term. &lt;br /&gt;&lt;br /&gt;In my experience, that is usually not necessary when using the Entire glossary setting, but may be useful in specific cases, such as when an all-UC target term matches an all-LC source.&lt;br/&gt;&lt;br/&gt; [url removed] &lt;br /&gt;&lt;br /&gt;J L</description>
		</item>
		<item>
			<title>Glossary terms - wrong case | Thank you!</title>
			<author>Armorel Young</author>
			<category>Wordfast support</category>
			<link>http://www.proz.com/post/2910475#2910475</link>
			<pubDate>Thu, 03 Jun 2021 17:58:00 +0000</pubDate>
			<description>&lt;b&gt;Forum:&lt;/b&gt; Wordfast support&lt;br/&gt;&lt;b&gt;Topic:&lt;/b&gt; Glossary terms - wrong case&lt;br/&gt;&lt;b&gt;Poster:&lt;/b&gt; Armorel Young&lt;br/&gt;&lt;b&gt;Post title:&lt;/b&gt; Thank you!&lt;br/&gt;&lt;br/&gt;Indeed - that&#039;s a very simple solution! I was looking all over the place in Setup and Pandora&#039;s Box - thank you for pointing me in the right direction.</description>
		</item>
		<item>
			<title>Glossary terms - wrong case | Easy!</title>
			<author>Jean Lachaud</author>
			<category>Wordfast support</category>
			<link>http://www.proz.com/post/2910473#2910473</link>
			<pubDate>Thu, 03 Jun 2021 17:55:00 +0000</pubDate>
			<description>&lt;b&gt;Forum:&lt;/b&gt; Wordfast support&lt;br/&gt;&lt;b&gt;Topic:&lt;/b&gt; Glossary terms - wrong case&lt;br/&gt;&lt;b&gt;Poster:&lt;/b&gt; Jean Lachaud&lt;br/&gt;&lt;b&gt;Post title:&lt;/b&gt; Easy!&lt;br/&gt;&lt;br/&gt;Is &quot;Lock target case on entire glossary&quot; checked for the glossaries concerned? &lt;br /&gt;&lt;br /&gt;That setting will force insertion of terms exactly as they are stored in the glossaries, i.e. no automatic capitalization. The setting needs to be enabled separately for each glossary.&lt;br /&gt;&lt;br /&gt;In the PB, &quot;PropagateCase=0&quot; also enables strict propagation.&lt;br /&gt;&lt;br /&gt; [url removed] &lt;br/&gt;&lt;br/&gt;JL</description>
		</item>
		<item>
			<title>Glossary terms - wrong case</title>
			<author>Armorel Young</author>
			<category>Wordfast support</category>
			<link>http://www.proz.com/post/2910460#2910460</link>
			<pubDate>Thu, 03 Jun 2021 17:15:00 +0000</pubDate>
			<description>&lt;b&gt;Forum:&lt;/b&gt; Wordfast support&lt;br/&gt;&lt;b&gt;Topic:&lt;/b&gt; Glossary terms - wrong case&lt;br/&gt;&lt;b&gt;Poster:&lt;/b&gt; Armorel Young&lt;br/&gt;&lt;br/&gt;Having had to reinstall WF Classic, WF now has the annoying habit of inserting words from the glossary using the capitalisation of the source text rather than the case of the target term in the glossary - which, since I am working from German with its capitalised nouns, means that all nouns are appearing capitalised.&lt;br /&gt;&lt;br /&gt;How to I make WF insert a term in lower case if the target term is in lower case in the glossary, even though the source term is upper case? No doubt the answer is in the manual somewhere, but I have spent far too long searching it fruitlessly so help from a knowledgeable person would be appreciated (I also know that I knew the answer myself in times gone by, but I can&#039;t locate it now!).</description>
		</item>
	</channel>
</rss>