Localization file in XLS/XLSX – 7 things to remember1. Do not sort it A-Z, Z-A, by length or in any way other than logical.
2. Make sure the string list is frozen – you will not be adding any new texts OR state that it is not final and new strings will be delivered. Then accumulate as many new strings as possible and send a bigger batch less frequently.
3. Add as many metadata (descriptions, module names, etc.) as possible for every string.
4. Include a maximum limit of characters for every row (if applicable).
5. Do not worry the XLS becomes huge! More data means better translation quality.
6. Make sure that no text or numbers are hardcoded into images.
7. As much as possible try to deliver logical chunks of text. For example: give conversations as
CONVERSATION BETWEEN PERSON A AND B
ROW 1: PERSON A TEXT,
ROW 2: PERSON B REPLY,
ROW 3: PERSON A TEXT,
ROW 4: PERSON B FOLLOW UP
and not
PERSON A TEXTS
ROW 1: PERSON A TEXT,
ROW 2: PERSON A TEXT,
PERSON B TEXTS
ROW 3: PERSON B REPLY,
ROW 4: PERSON B FOLLOW UP
Why do you need a game localization style guide?
Kilgray’s translation industry trend report in 10 thoughts I had when reading it
How to check game localization quality for free?