Active
Project:
XLIFF Tools
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
22 Jul 2009 at 00:39 UTC
Updated:
6 Mar 2010 at 02:30 UTC
The xliff I created from a date node opened in the Swordfish xliff editor, however the sources were all copied to targets and moving to another segment gave the following error:
Error saving current target: [Fatal Error] 1:95 The prefix "xmrk" for attribute "xmrk:ancs" associated with an element type "g" is not bound.
| Comment | File | Size | Author |
|---|
Comments
Comment #1
rmraya commentedThe "xmark" prefix indicates the use of a custom extension in the XLIFF file. You can add the XML schema where this extension is defined to Swordfish's XML catalog.
If the XML schema is available under a redistributable license (not GPL), send the schema to tech@maxprograms.com and it will be included in Swordfish's catalog in future releases.
Comment #2
meatron commentedThanks Rodolfo, you really are under every stone! This module is early alpha as announced, I sincerely hope the development continues. For sure it would be a great enhancment to any multi-lingual site.
Comment #3
pasquallethis might be fixed in 6.x-2.x
Comment #4
meatron commentedTesting 6.x-2.x. Nodes with photographs or flash objects don't convert. A simple node converted and Swordfish opened it. But it segmented by paragraphs, and sources copied to targets again.
Comment #5
pasqualle- My guess would be that nodes which can not be exported are not valid HTML, as we worked with images without problem.
- The paragraph segmenting is the way how it works. I do not see what is the problem with that.
- renamed the issue to match the feature request (make target empty)
Comment #6
meatron commentedYes, I think the problem is with image assist and swf code.
Most translators are used to sentence segmenting
Great you are working on this module again, I appreciate it very much!
Comment #7
meatron commentedImage assist works, but the code is of course inside the xliff. Along with tags like for formatted text. It would be a nice feature if tags were in Swordfish format «1» etc. But I just tested it on several nodes, and it worked perfectly! Except I would still prefer sentence segmentation of course :P
Kudos and thanks for the work!
Comment #8
meatron commentedOops the tag got eaten -
Along with tags like
<g id="strong-11">for formatted text