Sarah Ianieri

Thanks for screenshot... although you seem to handling this as an Excel file as opposed to CSV.  At least this is what it looks like since you have everything in one column.  Is this how it's supposed to be handled, so not like this... or something like this?

It seems to me you may be corrupting the intended formatting of this file because of the way you are looking at it and this is making it difficult for you to understand how it should be handled.  Excel could also be responsible for corrupting some of the characters due to encoding issues and this could be the cause of your "special chars" problem.

Can you open the CSV you were sent, before you open it in Excel and mess it up, in a decent text editor and then add a BOM (byte order mark... a good text editor can do this, something like Notepad++ or EditPad).  Then import the CSV into Excel as opposed to opening it in Excel.  Select the comma as the delimiter and then you'll be able to see what it should look like.

Then you'll also be able to see how best to handle it... if you get it Excel ready you can probably handle it easily with the Excel filetype in Studio, just adding a couple of embedded content rules for the ** symbols.  The numbers will be on segments of their own and so easy to handle.

ciao Paul,

thanks for your help! I managed the encoding of the fyle and everything is ok. I'm not able to add the embedded content rules for **. I know where they are but i have no idea which could be a possibility. Can you tell me an example please? the ** corresponds to "bold".

Thanks

Sarah Ianieri

Which filetype did you use in the end?

Sarah Ianieri said:

Can you tell me an example please? the ** corresponds to "bold".

It doesn't work like that.  Can you tell is what has been used for "bold" in the source file and then we can tell you how to pick it up using the embedded content processor.

Paul said:

The Excel filetype.

As you can see in the previous screen I sent you, the sentences are written as this:

**ALU BAND** è il nastro **monoadesivo acrilico** sviluppato specificamente per la **sigillatura ermetica di barriere vapore alluminizzate**

All the words between **  means that are in bold and I would like to transform it in a tag or something like this.

Paul said:

The Excel filetype.

As you can see in the previous screen I sent you, the sentences are written as this:

**ALU BAND** è il nastro **monoadesivo acrilico** sviluppato specificamente per la **sigillatura ermetica di barriere vapore alluminizzate**

All the words between **  means that are in bold and I would like to transform it in a tag or something like this.

Sarah Ianieri

In this case all you do is this:

Activate the Embedded Content and add one rule.  The rule is a new tag pair using this expression:

\*{2}

You can refine the rule using the Advanced Settings in the rule when you create it:

This way the bold tags can be hidden as they are only formatting:

Or show them:

And you could add formatting, also through the tag creation options:

The it would look like this:

Or this:

Thank you! now it works!

hi again Paul,

I'm sorry to write you again but I sent back the translated file to the website owner and he told me that the file is not well formatted. When i imported the .csv file into .xlsx the text was moved in more lines (in the source file there were just 3 lines) and they need back the text in 3 lines. I tried to do the inverse operation but maybe something didn't work. Can you please help me again and say how to re-convert the file as in the source one?

Many thanks

Sarah Ianieri

I can't really answer this question because I have no idea what you have actually done and I can't see where the problem might be originating from.  If you can send me the original source file, your filetype settings, and your translated sdlxliff, then I'll be happy to take a look for you?

If this is ok you can send it to pfilkin@sdl.com

Thank you Paul, I sent you an email, i hope you received it.

Hi Sarah Ianieri

Thanks for sending me your files. The part I'm missing is your source file... the one you actually translated.  Your source was a CSV but you imported this into Excel and translated the Excel.  I think the first thing to check is that you didn't make a mistake when you imported the CSV as this is very easy to do.  If the Excel didn't represent the format correctly then your ability to put it back as a CSV will be limited.

Certainly the CSV source file is a mess and doesn't follow the headings at all.  I would be having a discussion with the client if this is what I received.

ciao Paul

yes, I think the problem is when i convert the CVS file into Excel that all the lines were messed up.

I upload at the link I sent you the the file xls i use for translating (product_trans_semicolumn.cs_OK DECODIFICA.xlsx). You can find it also attached here. 

Which is the best format for translating a web site for example, xml?html?

I hope you can help me with a final solution.

Many thanks

product_trans_semicolumn.cs_OK DECODIFICA.xlsx

Sarah Ianieri

Sarah Ianieri said:

Which is the best format for translating a web site for example, xml?html?

Most likely html.  If your client is extracting text from an html you need to tell him just to provide the html.

Sarah Ianieri said:

yes, I think the problem is when i convert the CVS file into Excel that all the lines were messed up.

I imported the csv and the Excel does have a different format for me.  It's important to use Data -> Import in Excel and don't just open the CSV.  See if this is any better:

pf.zip

Paul

unfortunatelly not! The file should have only 3 lines as in the source file.

In the excel file most of the text moves in colum A and in more lines, I don't know why.

Sarah Ianieri

Sarah Ianieri said:

The file should have only 3 lines as in the source file.

Please explain?  This is your source file... at least this is the one you gave me: