Technical forums » OmegaT support »
SAXParseException : where to look?
Track this topic	Jump to forum [Translation - art & business]====================== Art of Translation and Interpreting--------------------Translator resourcesTranslation Theory and PracticeLiterature / PoetryInterpretingSubtitlingProofreading / Editing / ReviewingTranslation Project / Vendor Manage...MedicalLegalTranslation feedback area Business of Translation and Interpreting--------------------Money mattersGetting establishedBeing independentBusiness issuesTranslation agenciesScamsTranslators AssociationsMarketing for translators Language studies--------------------LinguisticsProfessional developmentTeaching and Learning LanguagesMultilingual familiesAncient languagesArtificial languagesStudentZ ForumStudentZ PubLinguistic diversityPronunciation Events and Awards--------------------Language Industry Events & Announce...Honors / CitationsProZ.com Germany eventsProZ.com Canada eventsProZ.com Netherlands eventsProZ.com UK eventsProZ.com Brazil eventsProZ.com Poland eventsProZ.com Austria eventsProZ.com Argentina eventsProZ.com France eventsProZ.com Spain eventsProZ.com's Virtual ConferencesProZ.com international conferences ProZ.com Chile eventsProZ.com Arab world eventsProZ.com regional eventsProZ.com USA events Translator playground--------------------Lighter side of trans/interpFun with ProZ.comFun with imagesFun with languageOther games Off-topic / Other--------------------Off topictranslators4kidsHealth and lifestyle for language p... [Technical forums]====================== Technical--------------------General technical issuesLocalizationSmart shoppersRight-to-left language technical fo...DTP - Desktop Publishing CAT Tools Support--------------------CAT Tools Technical HelpSDL Trados supportDéjà Vu supportWordfast supportTransit supportAlchemy supportAcross supportOmegaT supportMetatexis supportMemoQ supportSwordfish supportFluency supportCafeTran supportXTM Cloud support Computing--------------------Windows operating systemsApple/Mac operating systemsLinux OS / Free softwareHardware Software and Internet--------------------Office applicationsSoftware applicationsInternet for translatorsSafe computingSpeech recognition Machine Translation (MT)Social networking [Non-English forums]====================== Non-English forums--------------------AlbanianArabicArmenianAzerbaijaniBengaliBosnianBulgarianCatalanChineseCreoleCroatianCzechDanishDutchEstonianFinnishFrenchGaelic GeorgianGermanGreekGujarati HebrewHiligaynonHindiHungarianIcelandicIndonesianItalianJapanese / 日本語KazakhKoreanKurdishLatvianLithuanianMacedonianMalayMarathiMongolianNorwegianPersian/FarsiPolishPortugueseRomanianRussianSerbianSlovakSlovenian SpanishSwedishTagalogTamilThaiTurkishUkrainianUrduVietnamese [Country-specific forums]====================== Country-specific forums--------------------Translation in Argentina / La tradu...Translation in AustraliaTranslation in CanadaTranslation in Mexico / La traducci...Translation in Russia / Перев�...Translation in Spain / La traducci�...Translation in the UKTranslation in the USTranslation in Ukraine / Перек...Translation in Uruguay / La traducc... [Forums about proz.com]====================== Site Features--------------------ProZ.com in-person eventsTranslation newsPowwowsMiscellaneousKudoZProZ.com trainingProZ.com virtual conferencesFreelance translator workspacesProZ.com job systemsSite forumsProZ.com directoryProZ.com hostingPowwow organizersProZ.com: Translator CoopProZ.com technical supportPoll DiscussionTranslation Article KnowledgebaseProZ.com MembershipProZ.com Translation ContestsProZ.com translation industry wikiReports to ProZ.com membersProZ.com profile help Help Us To Improve--------------------ProZ.com suggestionsProZ.com bugs Corporate forums--------------------Business MattersOperations/ToolsSales/MarketingWorking with ProZ.com [Private forums]====================== ProZ.com Group Forums--------------------Proposals arising out of job postin...

User	Thread poster: JoyeuxDrille SAXParseException : where to look?
JoyeuxDrille Canada Local time: 16:56	Feb 10 Hi, I have used OmegaT for about a week now. I aligned five texts withtout any issue. Then, I translated a text using OmegaT, produced the target text and voilà! Got myself a nice translation, and got my TM going. BUT. But, but, but, now I've got an issue. Here's the error shown by OmegaT when I try launching my TM. Fatal error at line 8, column 153 org.xml.sax.SAXParseException: The element type "e0" must be terminated by the matching end-tag "" I also see this message for column 60 and column 204. This should be self-explanatory, but unfortunately I don't know which file I should be looking into... Does anyone know how I may find out which is the faulty file?   Subject: Comment: The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Didier Briel   France Local time: 22:56 Member (2007) English to French + ...	What do you call "launching your TM"? Feb 10 JoyeuxDrille wrote: BUT. But, but, but, now I've got an issue. Here's the error shown by OmegaT when I try launching my TM. What do you call "launching your TM"? Fatal error at line 8, column 153 org.xml.sax.SAXParseException: The element type "e0" must be terminated by the matching end-tag "" I also see this message for column 60 and column 204. This should be self-explanatory, but unfortunately I don't know which file I should be looking into... Does anyone know how I may find out which is the faulty file? Hard to say without the circumstances. If it happens when opening OmegaT, it is possible it's one of the TMXs (either project_save.tmx in the /omegat folder, or one of the external TMXs). Didier [Edited at 2012-02-10 16:49 GMT]   Subject: Comment: The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
JoyeuxDrille Canada Local time: 16:56 TOPIC STARTER	Pinpointing the right TMX file Feb 10 I call "launching my TM", loading the project I already created with OmegaT. I know it's very probably a TMX file, I just don't know how to find out which one it is. That is the essence of my question.   Subject: Comment: The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Didier Briel   France Local time: 22:56 Member (2007) English to French + ...	Check the log file Feb 10 JoyeuxDrille wrote: I call "launching my TM", loading the project I already created with OmegaT. I know it's very probably a TMX file, I just don't know how to find out which one it is. That is the essence of my question. Check the log file. Location (depending on your operating system) is given in the (at least English) manual. Didier   Subject: Comment: The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
JoyeuxDrille Canada Local time: 16:56 TOPIC STARTER	Log info Feb 11 I finally found that elusive logbook in the "/user/application data/omegaT" folder. Here's a short excerpt of what I found in there (about my error messages, of course). Could it be that the real issue is with a wrong language pair? I.e., that if I capitalize "en" into "EN" with all my aligned files, it might just work out? But then, why did I not get this error the first time around, when I loaded those TMX-aligned files? What to do? Any stem of an answer will be appreciated! 36271: Info: Créé par : Bitext2tmx (TMXR_INFO_CREATION_TOOL) 36271: Info: Version : 0.91 (TMXR_INFO_CREATION_TOOL_VERSION) 36271: Info: Méthode de segmentation : sentence (TMXR_INFO_SEG_TYPE) 36271: Info: Langue source : en (TMXR_INFO_SOURCE_LANG) 36271: Avertissement: La langue source (en) du fichier TMX est différente de la langue source du projet (EN-CA). Le fichier TMX continuera à être chargé. (TMXR_WARNING_INCORRECT_SOURCE_LANG) 36271: Info: Lecture du fichier TMX terminée (TMXR_INFO_READING_COMPLETE) 36271: Info: Lecture du fichier TMX D:\Traductions\OmegaT, projets de traduction\Articles sportifs, Cité Nouvelles\tm\Lakeshore Blue Jays Aug. 31fr.tmx (TMXR_INFO_READING_FILE) 36271: Info: Créé par : Bitext2tmx (TMXR_INFO_CREATION_TOOL) 36271: Info: Version : 0.91 (TMXR_INFO_CREATION_TOOL_VERSION) 36271: Info: Méthode de segmentation : sentence (TMXR_INFO_SEG_TYPE) 36271: Info: Langue source : en (TMXR_INFO_SOURCE_LANG) 36271: Avertissement: La langue source (en) du fichier TMX est différente de la langue source du projet (EN-CA). Le fichier TMX continuera à être chargé. (TMXR_WARNING_INCORRECT_SOURCE_LANG) 36271: Erreur: Erreur fatale à la ligne 8, colonne 204 pendant l'analyse : (TMXR_FATAL_ERROR_WHILE_PARSING) 36271: Erreur: org.xml.sax.SAXParseException: The element type "e0" must be terminated by the matching end-tag "". 36271: Erreur: at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) 36271: Erreur: at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(Unknown Source) 36271: Erreur: at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source) 36271: Erreur: at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(Unknown Source) 36271: Erreur: at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) 36271: Erreur: at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source) 36271: Erreur: at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source) 36271: Erreur: at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) 36271: Erreur: at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) 36271: Erreur: at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) 36271: Erreur: at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source) 36271: Erreur: at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source) 36271: Erreur: at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) 36271: Erreur: at javax.xml.parsers.SAXParser.parse(Unknown Source) 36271: Erreur: at org.omegat.util.TMXReader.loadFile(TMXReader.java:475) 36271: Erreur: at org.omegat.core.data.RealProject.loadTMXFile(RealProject.java:672) 36271: Erreur: at org.omegat.core.data.RealProject.loadTM(RealProject.java:642) 36271: Erreur: at org.omegat.core.data.RealProject.loadProject(RealProject.java:217) 36271: Erreur: at org.omegat.core.data.ProjectFactory.loadProject(ProjectFactory.java:66) 36271: Erreur: at org.omegat.gui.main.ProjectUICommands$2.doInBackground(ProjectUICommands.java:155) 36271: Erreur: at org.jdesktop.swingworker.SwingWorker$1.call(Unknown Source) 36271: Erreur: at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) 36271: Erreur: at java.util.concurrent.FutureTask.run(Unknown Source) 36271: Erreur: at org.jdesktop.swingworker.SwingWorker.run(Unknown Source) 36271: Erreur: at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) 36271: Erreur: at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 36271: Erreur: at java.lang.Thread.run(Unknown Source) 36271: Erreur: Erreur fatale à la ligne 8, colonne 204 pendant l'analyse : (TMXR_FATAL_ERROR_WHILE_PARSING) 36271: Erreur: org.xml.sax.SAXParseException: The element type "e0" must be terminated by the matching end-tag "".   Subject: Comment: The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Didier Briel   France Local time: 22:56 Member (2007) English to French + ...	There is probably a damaged or missing tag Feb 11 JoyeuxDrille wrote: I finally found that elusive logbook in the "/user/application data/omegaT" folder. That's what the documentation says. Here's a short excerpt of what I found in there (about my error messages, of course). Could it be that the real issue is with a wrong language pair? Not at all. OmegaT is very tolerant as far as language codes are concerned. I.e., that if I capitalize "en" into "EN" with all my aligned files, it might just work out? No. What to do? Any stem of an answer will be appreciated! 36271: Info: Lecture du fichier TMX D:\Traductions\OmegaT, projets de traduction\Articles sportifs, Cité Nouvelles\tm\Lakeshore Blue Jays Aug. 31fr.tmx (TMXR_INFO_READING_FILE) It seems to be the faulty one. 36271: Erreur: Erreur fatale à la ligne 8, colonne 204 pendant l'analyse : (TMXR_FATAL_ERROR_WHILE_PARSING) 36271: Erreur: org.xml.sax.SAXParseException: The element type "e0" must be terminated by the matching end-tag "". Clearly, one tag (not necessarily the one mentioned, given the way a parser works) has been damaged. Normally, tags such as "eo" should not appear as tags in a TMX, so I suspect some "text" (i.e., pseudo tags) that should be escaped is not. A "simple" way to solve it is to look at that file with a text editor, and see what might be wrong. If you do not manage to see what's wrong, I suggest to subscribe to the OmegaT Yahoo mailing list, where you will be able to ask for help. Didier   Subject: Comment: The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)

Reply / comment

To report site rules violations or get help, contact a site moderator:

Moderator(s) of this forum
Emanuela Galdelli	[Call to this topic]

You can also contact site staff by submitting a support request »

SAXParseException : where to look?