Under Community Review

Allow translation files and reference files with the same name

Currently you cannot add a reference file and translatable file with the same name in a project.
I believe the reason why is because Studio keeps the original files in the source folder, so a reference file with the same name would conflict with the original file.
However, this could be easily worked around by creating a "Reference" or "Source File" folder to separate the files.

Parents
  • We use reference files in this way: source file might be an InDesign file / IDML, i.e. not accessible to view for our freelancers. We will add a PDF generated from the InDesign file as reference file, so the freelancer can see what the source file looks like in final layout. This provides critical context when translating the SDLXLIFF where segments might not always be in the right order or in context.  That said, I'm not sure I would want them in separate folders. Too easy to miss/ignore. I always make sure they are in each target language folder. The simple fact that they have the .pdf extension prevents the above-described issue of having identical file names.

Comment
  • We use reference files in this way: source file might be an InDesign file / IDML, i.e. not accessible to view for our freelancers. We will add a PDF generated from the InDesign file as reference file, so the freelancer can see what the source file looks like in final layout. This provides critical context when translating the SDLXLIFF where segments might not always be in the right order or in context.  That said, I'm not sure I would want them in separate folders. Too easy to miss/ignore. I always make sure they are in each target language folder. The simple fact that they have the .pdf extension prevents the above-described issue of having identical file names.

Children
No Data