<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">Regrets for any duplication: I'm not sure which of the pet vs. erg lists to address this to  since the lexical filtering question is with regard to the ERG, not PET. On 9/18/2013 9:26 AM, Paul Haley wrote: </div> <blockquote cite="mid:5239AA07.8080509@haleyai.com" type="cite"> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> <div class="moz-cite-prefix">Hello, I may be making some conceptual progress on this... I went back to the chart mapping tutorial (<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://moin.delph-in.net/Chart_Mapping">http://moin.delph-in.net/Chart_Mapping</a>) and found myself looking at the following lexical filtering rule from the ERG's lfr.tdl: <blockquote> ;; throw out generic whenever a native entry is available, unless the token is ;; a named entity (which now includes names activated because of mixed case or ;; non-sentence-initial capitalization). ;; generic_non_ne+native_lfr := lexical_filtering_rule & [ +CONTEXT < [ SYNSEM.PHON.ONSET con_or_voc ] >,   +INPUT < [ SYNSEM.PHON.ONSET unk_onset, ORTH.CLASS non_ne ] >,   +OUTPUT < >,   +POSITION "I1@C1" ]. </blockquote> Is it the case that I want the +CONTEXT and +INPUT to be exactly reversed with NO_DEFAULT_LES or DEFAULT_LES_POSGAPS_LEXGAPS? Thank you, Paul On 9/17/2013 4:54 PM, Paul Haley wrote: </div> <blockquote cite="mid:5238C18A.1090302@haleyai.com" type="cite">Hi, It seems that when I send FSC w/ TNT tags for some but not all tokens I get ERG LEs that do not satisfy the provided tags when using any of NO_DEFAULT_LES, DEFAULT_LES_ALL, or DEFAULT_LES_POSGAPS_LEXGAPS.  It does respect these tags when there are no corresponding ERG LEs, however, which is good. Is there a way that I can get PET w/ the ERG to respect the TNT tags when provided but otherwise use the ERG LEs? Thank you, Paul </blockquote> </blockquote> </body> </html>