<sic>

<sic> (Latin for thus or so) contains text reproduced although apparently incorrect or inaccurate. [3.4.1 Apparent Errors]
Modulecore — Elements Available in All TEI Documents
Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
model.choicePart model.pPart.transcriptional
Contained by
analysis: cl pc phr s w
core: abbr add addrLine author bibl biblScope choice citedRange corr date del distinct editor email emph expan foreign gloss head headItem headLabel hi item l label measure mentioned name note num orig p pubPlace publisher q quote ref reg rs said sic soCalled speaker stage street term textLang time title unclear
dictionaries: case colloc def dictScrap entryFree etym form gen gram gramGrp hyph iType lang lbl mood number orth per pos pron re sense stress subc syll tns usg xr
drama: actor camera caption castItem role roleDesc sound tech view
figures: cell
header: change distributor edition extent geoDecl handNote licence scriptNote
linking: ab seg
msdescription: accMat acquisition additions catchwords collation colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit layout material musicNotation objectType origDate origPlace origin provenance rubric secFol signatures source stamp summary support surrogates typeNote watermark
namesdates: addName affiliation birth bloc country death district education faith floruit forename genName geogFeat geogName nameLink nationality occupation offset orgName persName placeName region residence roleName settlement sex socecStatus surname
spoken: u writing
tagdocs: eg
textcrit: lem rdg wit witDetail
textstructure: byline closer dateline docAuthor docDate docEdition docImprint imprimatur opener salute signed titlePart trailer
transcr: am damage fw metamark mod restore retrace secl supplied surplus
verse: rhyme
May contain
analysis: c cl interp interpGrp m pc phr s span spanGrp w
certainty: certainty precision respons
core: abbr add address bibl biblStruct binaryObject cb choice cit corr date del desc distinct email emph expan foreign gap gb gloss graphic hi index l label lb lg list listBibl measure measureGrp media mentioned milestone name note num orig pb ptr q quote ref reg rs said sic soCalled stage term time title unclear
dictionaries: lang oRef oVar pRef pVar
drama: camera caption castList move sound tech view
figures: figure formula notatedMusic table
gaiji: g
header: biblFull idno
iso-fs: fLib fs fvLib
linking: alt altGrp anchor join joinGrp link linkGrp seg timeline
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName affiliation bloc climate country district forename genName geo geogFeat geogName listEvent listNym listOrg listPerson listPlace location nameLink offset orgName persName placeName population region roleName settlement state surname terrain trait
spoken: incident kinesic pause shift vocal writing
tagdocs: att classSpec code constraintSpec dataSpec eg egXML elementSpec gi ident listRef macroSpec moduleSpec outputRendition specDesc specGrp specGrpRef specList tag val
textcrit: app listApp listWit witDetail
textstructure: floatingText
transcr: addSpan am damage damageSpan delSpan ex fw handShift listTranspose metamark mod redo restore retrace secl space subst substJoin supplied surplus undo
verse: caesura rhyme
character data
Example
for his nose was as sharp as
a pen, and <sic>a Table</sic> of green fields.
Example

If all that is desired is to call attention to the apparent problem in the copy text, sic may be used alone:

I don't know, Juan. It's so far in the past now
— how <sic>we can</sic> prove or disprove anyone's theories?
Example

It is also possible, using the choice and corr elements, to provide a corrected reading:

I don't know, Juan. It's so far in the past now
— how <choice>
 <sic>we can</sic>
 <corr>can we</corr>
</choice> prove or disprove anyone's theories?
Example
for his nose was as sharp as
a pen, and <choice>
 <sic>a Table</sic>
 <corr>a' babbld</corr>
</choice> of green fields.
Content model
<content>
 <macroRef key="macro.paraContent"/>
</content>
Schema Declaration
<rng:element name="sic">
 <rng:ref name="att.global.attributes"/>
 <rng:ref name="att.global.rendition.attributes"/>
 <rng:ref name="att.global.linking.attributes"/>
 <rng:ref name="att.global.analytic.attributes"/>
 <rng:ref name="att.global.facs.attributes"/>
 <rng:ref name="att.global.change.attributes"/>
 <rng:ref name="att.global.responsibility.attributes"/>
 <rng:ref name="att.global.source.attributes"/>
 <rng:ref name="macro.paraContent"/>
</rng:element>
element sic
{
   att.global.attributes,
   att.global.rendition.attributes,
   att.global.linking.attributes,
   att.global.analytic.attributes,
   att.global.facs.attributes,
   att.global.change.attributes,
   att.global.responsibility.attributes,
   att.global.source.attributes,
   macro.paraContent
}