nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Special chars on importing html

aby_sam

I have a peculiar problem. When I import an html file, a special character "ï»¿" gets tagged to the beginning of html file I import to TeamSite.
Is this a known issue in TS 6.0? Any clue towards resolution.

TS 6.0
AIX 5.2

Thanks in advance

Find more posts tagged with

Comments

ISCBorisB

I have a peculiar problem. When I import an html file, a special character "ï»¿" gets tagged to the beginning of html file I import to TeamSite.
Is this a known issue in TS 6.0? Any clue towards resolution.

TS 6.0
AIX 5.2

Thanks in advance

Check if your original files have this symbols at the beginning.

What you see is Byte Order Mark (BOM) character that indicates big/little endian addressing for UTF 16/32 or simply Unicode marker for UTF 8.
That often originates from Unicode-enabled software including editors like UltraEdit. If that's your case, check software settings,
you can usually switch that "unsolicited service" off

aby_sam

Thanks for your reply. But this special char. doesn't appear, when I download the html file to local machine. When I import it back to the WA, I see the issue.
However when I create a new file with ANSI encoding, the issue doesn't occur.
Is the process invloved in TS import also a cause for the problem.

ISCBorisB

What is the tool you use to "create a new file" ? Is it unicode enabled?
Please note that the presence or absence of BOM is often transparent in Unicode tools.

But this special char. doesn't appear, when I download the html file to local machine

What did you use to look at the file? Note that even OOTB Win Notepad is Unicode nowdays. Look at the file in hex mode ot "type" it from cmd.

Is the process invloved in TS import also a cause for the problem

GroupedIntervals.zip

chandraiw

"type" it from cmd.

can't trust this one as it is dependent OS locale/user encoding settings. but, (as mentioned) a hex editor rocks!

ISCBorisB

can't trust this one as it is dependent OS locale/user encoding settings. but, (as mentioned) a hex editor rocks!

I would disagree. Granted, you can not trust "type" for proper unicode symbols rendition.
However, if BOM character is present type will dutifully "type" it

chandraiw

if BOM is present

I would mark that Smiley Happy

ISCBorisB

I would mark that

What I meant was that it would type BOM itself. File content proper will look the same, BOM or no BOM