[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] RE: Binary files (e.g., jpg) with dependent source files (e.g., PhotoShop)
I’ve settled on using
xlf:reference with an xlf:note indicating that the referenced file is used to
generate the binary file. Doug From: Doug Domeny Christian, It’s
case 2. An HTML
page shows a picture (a .jpg photo) that needs to be localized. The image may
need graphic changes and/or text translation. The .jpg is created from a
Photoshop file that uses layers and/or graphic objects. I would
expect the translator to add layers / graphics to the Photoshop file for the
target language and regenerate the .jpg file. Shown
here (in Paint Shop Pro since I don’t have Photoshop) is an image with
different layers. The “Hello World” text is a graphic object in the
English layer. The “Hola mundo” is a graphic object in the Spanish
layer. Other languages would be added in more layers. Without
the layers, it would be very difficult to separate the “Hello
World” text from the background. The
Photoshop file is the “source” from which the JPEG is created.
(Much like a binary objects are compiled from C or Java source code). Regards, Doug From: Lieske, Christian
[mailto:christian.lieske@sap.com] Hi
there, I
would need some additional information in order to comment: What is the
“nature/purpose” of the “dependant files”? I see at
least the following possibilities: 1.
The
files are needed to produce an overall “product” (example: the JPG
is needed to produce a Web page), but do not need to undergo any kind of
localization or translation. 2.
The
files are needed to produce an overall “product” (example: the JPG
is needed to produce a Web page), and need to undergo some kind of localization
or translation (example: the JPG needs to be adapted wrt. certain graphical
elements). 3.
The
files serve reference or preview purposes (example: the PDF is included to show
translators how the rendered version of the source language marketing material
looks like). 4.
The
files are related to processing chains (example: you reference the Framemaker
file for traceability reason – eg. to ensure that you don’t miss
updates). From my
understanding, you can only choose the correct XLIFF representation if this
kind of questions is answered. Only then, you can for example tell whether
something goes into the “reference” element or a
“translate=’no’” has to be used. Best
regards, Christian From: Rodolfo M. Raya
[mailto:rmraya@maxprograms.com] Hi
Doug, If you
put both, PSD and JPG, files in the XLIFF document, then you are duplicating
the translatable units in different formats. You should include only one of
them. Regarding
units linking, there is no way that I know. Best
regards, Rodolfo -- Rodolfo M.
Raya <rmraya@maxprograms.com> Maxprograms
http://www.maxprograms.com From: Doug Domeny
[mailto:ddomeny@ektron.com] Rodolfo, Yes, I
agree, however the problem is a bit more complex than I had originally
explained. Here’s a better explanation. The
image is referenced in HTML: <img
src="”assets/filename.jpg”" /> The
XLIFF for the JPEG would be: <bin-unit id=”id”
mime-type=”image/jpeg”> <bin-source> <external-file
href="”filename.jpg”/> </bin-source> </bin-unit> The
XLIFF for the Photoshop would be: <bin-unit id=”id”
mime-type=”image/vnd.adobe.photoshop”> <bin-source> <external-file
href="”photoshopfilename.psd”/> </bin-source> </bin-unit> How,
in XLIFF, should the .psd be linked to the .jpg so the translator knows how to
name the jpg file? Or to create a JPEG, PNG or other web-friendly image file at
all? Currently,
the implementation would have the JPEG and PSD bin-units in two different XLIFF
files, but I might be able to combine them if necessary. Thanks
for the quick reply (and apologies or the slow response back). Doug From: Rodolfo M. Raya
[mailto:rmraya@maxprograms.com] Hi
Doug, In
case 1, the source document is the PhotoShop file, not the JPG picture. Let the
user translate the text from the PhotoShop file and then generate a new JPG. In
case 2, the source document would be the Framemaker book. Once it is
translated, you can generate a new PDF from it. I
would not use <bin-unit> for translating a Framemaker file. You can save
it as MIF and use <trans-unit> elements instead to hold translatable
text. Hope
this helps, Rodolfo
From: Doug Domeny
[mailto:ddomeny@ektron.com] Sent
this to the official list, but believe it was not forwarded to the team, so
I’m sending it directly to a few of you. If you did get the automated
email, please excuse this duplicate. From: Doug Domeny XLIFF Team, What is best practice for handling
dependent files in XLIFF? Case 1: Web content includes an image in
JPEG format. The JPEG file (.jpg) was originally created from a PhotoShop file
(.psd). In XLIFF, the JPEG file is marked
as: <bin-unit id=”id”
mime-type=”image/jpeg”> <bin-source> <external-file
href="”filename.jpg”/> </bin-source> </bin-unit> How should the PhotoShop file be
associated with the JPEG? Case 2: An Adobe Acrobat file (.pdf)
originally created from a FrameMaker book. In XLIFF, the PDF file is marked
as: <bin-unit id=”id”
mime-type=”application/pdf”> <bin-source> <external-file
href="”filename.pdf”/> </bin-source> </bin-unit> How should set of FrameMaker files
be associated with the PDF? I’ve thought of making the
bin-source the original file(s), but would like the translator to create the
derived file. Regards, Doug Domeny |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]