Difference between revisions of "Talk:AY Honors/Springboard Diving/Answer Key"
From Pathfinder Wiki
< Talk:AY HonorsTalk:AY Honors/Springboard Diving/Answer Key
m |
|||
| Line 6: | Line 6: | ||
::::When these tags are <i>deleted</i>, the extension then has to reassign all the chunks after the page is saved. This means that the previous translations are then nulled or voided and will often have to be <i>again</i> translated. Leave the tags be and just add the info. The extension will then let translators know that there are new pieces that have to be translated or that the previous chunks have to be updated. Try <b>not</b> to delete the tags or move them around, unless you are going to do the translating. | ::::When these tags are <i>deleted</i>, the extension then has to reassign all the chunks after the page is saved. This means that the previous translations are then nulled or voided and will often have to be <i>again</i> translated. Leave the tags be and just add the info. The extension will then let translators know that there are new pieces that have to be translated or that the previous chunks have to be updated. Try <b>not</b> to delete the tags or move them around, unless you are going to do the translating. | ||
::::While they might be visually distracting, but they are important to keep in place for the translations. --[[User:W126jep|w126jep]] ([[User talk:W126jep|talk]]) 19:05, 8 December 2014 (EST) | ::::While they might be visually distracting, but they are important to keep in place for the translations. --[[User:W126jep|w126jep]] ([[User talk:W126jep|talk]]) 19:05, 8 December 2014 (EST) | ||
| + | |||
| + | :::::I'm pretty sure he was not deleting them because they were visually distracting, but rather, because the extension prevents him from saving under some unknown circumstance. It's better to add some white space or non-printable text (surround with <!-- this won't print -->). But, no, do not delete them. It undoes a mountain of work. If we can't get the page to save, we need to carefully weigh the worth of the edit as compared to the work put into the translation. In some cases, it is probably better to skip the edit. Meanwhile, we should try to get our arms around ''why'' the extension refuses to save sometimes. --[[User:Jomegat|Jomegat]] ([[User talk:Jomegat|talk]]) 21:39, 8 December 2014 (EST) | ||
Revision as of 03:39, 9 December 2014
I am struggling with the t tags. After I enter more info I get conflicts over the tags. I just delete tags until I can save the info, but that is obviously not the answer. JadeDragon (talk) 14:05, 6 December 2014 (EST)
- Do you mean the translate tags? What kind of conflicts do you get? What does the error message say, if there is one? --w126jep (talk) 20:59, 7 December 2014 (EST)
- Stops me from saving the edit. I'll copy the message here next time.JadeDragon (talk) 05:12, 8 December 2014 (EST)
- I've seen that before as well. My approach is usually to add whitespace around the tags (carriage returns, etc). The tutorials for the translate extension make vociferous admonitions against messing with the tags. I assume it creates havoc. --Jomegat (talk) 18:54, 8 December 2014 (EST)
- For some reason I'm just understanding now that JadeDragon is deleting the tags and then saving the page. This indeed does create havoc. The translations are separated into chunks and each chunk is assigned a number, which you see above or the side (ex. <--T:24-->). A translator then can translate the page chunks at a time.
- When these tags are deleted, the extension then has to reassign all the chunks after the page is saved. This means that the previous translations are then nulled or voided and will often have to be again translated. Leave the tags be and just add the info. The extension will then let translators know that there are new pieces that have to be translated or that the previous chunks have to be updated. Try not to delete the tags or move them around, unless you are going to do the translating.
- While they might be visually distracting, but they are important to keep in place for the translations. --w126jep (talk) 19:05, 8 December 2014 (EST)
- I've seen that before as well. My approach is usually to add whitespace around the tags (carriage returns, etc). The tutorials for the translate extension make vociferous admonitions against messing with the tags. I assume it creates havoc. --Jomegat (talk) 18:54, 8 December 2014 (EST)
- Stops me from saving the edit. I'll copy the message here next time.JadeDragon (talk) 05:12, 8 December 2014 (EST)
- I'm pretty sure he was not deleting them because they were visually distracting, but rather, because the extension prevents him from saving under some unknown circumstance. It's better to add some white space or non-printable text (surround with <!-- this won't print -->). But, no, do not delete them. It undoes a mountain of work. If we can't get the page to save, we need to carefully weigh the worth of the edit as compared to the work put into the translation. In some cases, it is probably better to skip the edit. Meanwhile, we should try to get our arms around why the extension refuses to save sometimes. --Jomegat (talk) 21:39, 8 December 2014 (EST)
