# back to localization

**URL:** <https://discourse.citationstyles.org/t/back-to-localization/164>\
**Category:** CSL Development\
**Created:** [August 1, 2006, 1:45pm UTC](https://discourse.citationstyles.org/t/back-to-localization/164 "2006-08-01T13:45:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bruce\_D\_Arcus1](https://avatars.discourse-cdn.com/v4/letter/b/4bbf92/32.png) [@Bruce\_D\_Arcus1](https://discourse.citationstyles.org/u/Bruce_D_Arcus1)\
**Post date:** [August 1, 2006, 1:45pm UTC](https://discourse.citationstyles.org/t/back-to-localization/164/1 "2006-08-01T13:45:53Z")

</div>

OK, how’s this for the localization markup?

 In Accessed Forthcoming and page pages p pp 

The terms element can either be a standalone file (which it hopefully  
almost always will be), or embedded within a CSL file for  
customization.

I suggest the following schema pattern:

cs-terms = element cs:terms { cs-locale+ }

cs-locale = element cs:locate { attribute xml:lang { xsd:language },  
(cs-simple-term | cs-compound-term)+ }

cs-simple-term = element cs:term { attribute name { cs-terms.simple },  
text }  
cs-compound-term = element cs:term { attribute name { cs-terms.simple },  
cs-term.single, cs-term.multiple }

cs-terms.simple = “in”  
\> “and”  
\> “forthcoming”  
\> “in press”  
\> “no date”  
\> “accessed”  
\> “edited by”  
\> “translated by”  
\> “edited by-short”  
\> “translated-by”

cs-terms.compound = “editor”  
\> “editor-short”  
\> “translator”  
\> “translator-short”  
\> “pages”  
\> “paragraphs”

… and so forth.

Is that what we want? If yes, please suggest additions to the list of  
values.

Bruce