Posted by meatron on July 22, 2009 at 12:39am
Jump to:
| Project: | XLIFF Tools |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
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.
Comments
#1
The "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.
#2
Thanks 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.
#3
this might be fixed in 6.x-2.x
#4
Testing 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.
#5
- 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)
#6
Yes, 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!
#7
Image 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!
#8
Oops the tag got eaten -
Along with tags like
<g id="strong-11">for formatted text