When copying tags, other special characters are copied instead of spaces
Categories
(support.mozilla.org :: Localization, defect)
Tracking
(Not tracked)
People
(Reporter: mad_maks, Unassigned)
Details
For some time (several weeks), when localizing support articles, tags containing spaces are incorrectly copied to the clipboard. As a result, after insertion, these tags do not work correctly. You have to manually delete everything and insert right spaces.
Examples of such tags:
- illustrations containing spaces in the tag with link to the image;
- constructions of the form {for fx108};
- links to articles (I discovered this today) of the form "Article title|link text".
See https://support.mozilla.org/nl/forums/l10n-forum/716114?last=84682
reproduce
- Edit a article marked as need update
- copy from the en-US version a tag like {for fx108}
- paste the tag into the l10n version
- press example of content
- the tag is in the text, you see {for fx108}
- remove the copied tag en type it yourself
- press example of content
- the tag works as expected
Comment 1•1 year ago
|
||
Hey Tim,
Thanks for capturing this issue into a bug report. When you mention "press example of content", do you mean to select Content Preview button? And when you do that, the exact line "{for fx108}" showed in the preview instead of acting as a tag as it is intended?
Reporter | ||
Comment 2•1 year ago
|
||
yes sorry i re translate the dutch version of sumo to English, i mean indeed Content Preview
If you have copied the tag then it will show the wording of the tag as text and does not work
Comment 3•1 year ago
|
||
Morphing this into type: bug.
Hey Tim,
Unfortunately, I am unable to reproduce this issue.
Is this still occurring for you? If yes, could you please help us by attaching a screencast to this ticket? It would help greatly.
Thank you!
I haven't experienced this for about a week. It looks like it's fixed.
Reporter | ||
Comment 5•11 months ago
|
||
sorry for the late response, just tested it and it works now for me. If somebody report this again in the forum i will reopen this bug, for now closing.
Description
•