4258922
Question 1
Question
Your query is showing zero results at the beginning of cadence - even though HO email indicated there should be some strings for you. What are the possible reasons?
Answer
-
Another member of my Team might have worked on those strings already. I should check with my colleagues.
-
I might be running an outdated query. I should re-download it from ftp and try again.
-
There's a zombie apocalypse ongoing, and all strings had been eaten.
Question 2
Question
Your query is showing a lot more results than expected. Which of the following are the possible reasons for that?
Answer
-
LSP_Default filter might be turned off. I should make sure it's set and run the query again.
-
Maybe someone from my Team has accidentally modified the query by removing some of its conditions. I should download the query again from ftp.
-
PJM kept the real word count a secret from me, hoping I'd do it anyway.
-
The Client has been working on the strings and accidentally made them all visible to us. We should contact PJM Team.
Question 3
Question
When should you do the following: 1. Export your work to an offline file. 2. Close LEAF. 3. Clear your browser's history 4. Reload the strings from exported file and try again.
Answer
-
When I get a SOAP error in LEAF.
-
Whenever I am submitting my translation to Fabric.
-
When I get 'No downloadable resources' error.
Question 4
Question
What does the following LocVer error message mean?
Placeholder Rule Placeholder 08: Placeholder '<' does not exist in target.
Answer
-
Placeholder '<' should appear in my translation, but it doesn't. I need to add it.
-
I have added the placeholder '<' to my translation by mistake, I should remove it.
-
I have a hot key in my translation, I need to escape it.
Question 5
Question
What is LocVer validation?
Answer
-
It's a verification of localized text against a set of technical rules that make the text work in software as designed.
-
LocVer is a version test. It checks if our localized strings are consistent with older versions of the product.
-
It's verification of localization - checks spelling and some very simple grammar mistakes.
Question 6
Question
You have just finished your translation, and tried to upload strings to server. However, you got an unusual dialog window listing the strings. This dialog only displays Res IDs, but you have recognized at least a few of the strings you have just worked on. Apparently you made some changes, and this window gives you two options to choose from: 'Accept all theirs' and 'Accept all yours'. What happened, and what should you do?
Answer
-
Someone else had uploaded the very same strings to Fabric just before me. I should double check with my colleagues if they were working on the same query. If yes, we can decide whose changes to keep. If not, I should contact PJM Team.
-
This is a common LEAF error, usually caused by my session ending before I got the chance to upload strings. I should save my translation offline, close LEAF, clear my cookies, and then log in to LEAF again.
-
This is a technical issue caused by the Client's Engineers making some general changes in LEAF. I should always click 'Accept all theirs'.
Question 7
Question
You had a very urgent job to deliver, and you had to hire an external resource with no LEAF access. You have exported the strings to Excel for them, and they sent you back the translation. You have now pasted it back in Fabric, and validated it. Why are there so many LocVer errors for missing placeholders? You have double checked, and placeholders are correct!
Answer
-
They are all noise LocVer errors. I should add a TermNote comment for each of them and submit the strings normally.
-
LEAF sometimes fails to recognize placeholders from pasted text. I need to check if placeholders appear in gray font. If not, I should rewrite them or copy-paste them from source, and those LocVers will disappear.
-
LocVer validation can't see the placeholders because of connectivity issues. I confirmed the placeholders are there, so I can safely submit the strings.
Question 8
Question
You found a bug for your language in Daily Bug Report entitled: 'Inconsistent translation for Broadcast', but there is nothing in Description field. How will you fix this bug?
Answer
-
There is nothing I can do on my own, I should go back to Engineers and request a query.
-
I should check Area Path (column G) as it will likely tell me in which tenant and project to look for the term 'Broadcast'. If I still don't know how to find it, I should contact Engineers.
-
I should follow the instruction from Repro Steps (column J) to find the bug, and fix it.
Question 9
Question
You made a query to fix a bug, and you based it on your Translation query. You run it, and you got no results. What should you do?
Answer
-
I need to check if I removed Custom Condition: SDL_Language_Translator.
-
The resource ID I was looking for may contain a semicolon ( ; ). I should remove a part of res ID so that semicolon disappears, and try again.
-
I might have set the condition for Res ID to 'Equals' instead of 'Contains'. I need to make sure it says 'Contains'.
-
This string is probably outside of Custom Condition: Language_Standard_Conditions. I should remove it and try again.
Question 10
Question
You got a bug for incorrect translation. The string looks very bad, you are positive neither yourself nor any of your colleagues ever submitted such low quality translation. Where will you check who created it?
Answer
-
I will run an old translation query.
-
I will check History of the string in LEAF.
-
I can't check that myself, I need to ask PJM to do it for me.
Want to create your own Quizzes for free with GoConqr? Learn more.