when defining constants.xlf it's really important to use UUID to avoid conflicts, since you have no idea of what other plugin, components (private and public) have defined and will define after yours is loaded.
something like: > <?xml version="1.0" encoding="UTF-8" standalone="no" ?> > <xliff version="1.0" xmlns:d4="http://www.4d.com/d4-ns";> > > <header> > <note>Common Crypto plugin</note> > </header> > > <group resname="themes"> > <trans-unit id="30075EDF927B4ADCA4FB6968D37ABE4C" > resname="30075EDF927B4ADCA4FB6968D37ABE4C" translate="no"> > <source>Crypto output format</source> > </trans-unit> > </group> > > <group d4:groupName="30075EDF927B4ADCA4FB6968D37ABE4C" restype="x-4DK#"> > <trans-unit d4:value="0:L" id="30075EDF927B4ADCA4FB6968D37ABE4C.1"> > <source>Crypto HEX</source> > </trans-unit> > </group> > > </xliff> notice how group@d4:groupName is a UUID and trans-unit@id and id is its derivative. notice also the use of a type specifier (:L for longint) in trans-unit@d4:value ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
