Duplicate id

[libre75]

Hi Guys, the validator signals me an error while reading "duplicate '_s'
I don't understand what this duplication is, I don't see it, can you help me?
Here is the code:

<div style="clear:both; mso-break-type:section-break; page-break-before:auto"><p style="font-size:16pt; line-height:150%; page-break-before:always"><span style="font-family:Arial, sans-serif; font-size:16pt; font-weight:bold">Prima </span><a id="_s"></a><span style="font-family:Arial, sans-serif; font-size:16pt; font-weight:bold">settimana</span></p>

[DiapDealer]

It means that some other element in the same file has the id "_s". That's not allowed.

[Turtle91]

Just a piece of, unasked for, advice:

Try not to use inline styles unless it is absolutely necessary. It bloats your code, making it much harder to edit, and longer for the device/app to load and render.

Instead, use a CSS file. Your HTML code will look something like this:

instead of:
<div style="clear:both; mso-break-type:section-break; page-break-before:auto">
<p style="font-size:16pt; line-height:150%; page-break-before:always">
<span style="font-family:Arial, sans-serif; font-size:16pt; font-weight:bold">Prima </span>
<a id="_s"></a>
<span style="font-family:Arial, sans-serif; font-size:16pt; font-weight:bold">settimana</span></p>

use CSS:
h3 {font-size:2em; font-family:Arial, sans-serif; font-weight:bold}

and HTML:
<h3>Prima settimana</h3>

[DNSB]

Another piece of unasked for advice, if you are creating an ebook that will be read by others, do not force fonts. Fonts which look good on your LCD monitor are very often not as good looking on a smaller device or an e-Ink display. You may also want to consider that fonts such as Arial which is owned by Monotype and has a cost associated with embedding are a bad choice when producing books for others to read.

Two other items are specifying fonts sizes in absolute values (16pt in your sample) is not a good idea and you might also want to remove the Microsoft specific bits since there is no guarantee that your renderer will understand it (a renderer is the software that translates your work into pixels) or handle a failure to understand it correctly.

[JSWolf]

Originally Posted by Turtle91

Just a piece of, unasked for, advice:

Try not to use inline styles unless it is absolutely necessary. It bloats your code, making it much harder to edit, and longer for the device/app to load and render.

Inline code is NEVER necessary. There's never any reason to use it.

[JSWolf]

Yet another piece of unasked for advice.

Take the Word document and remove all formatting and use styles properly. If you use styles, you will avoid a lot of that very messy code that you have in your Word document. That will make your ePub a lot neater and easier to edit. If you don't understand styles or want to see how to use styles, have a look at this video.

[DiapDealer]

OK folks. Enough of the unasked for advice. It's starting to feel a bit like the OP is being ganged up on. Are we really THAT bored that we have to completely dissect a code snippet that was posted instead of just answering the simple question asked? One thing at a time.

This place can be intimidating enough for neophytes. No need for the information overload.

[DNSB]

Originally Posted by DiapDealer

OK folks. Enough of the unasked for advice. It's starting to feel a bit like the OP is being ganged up on. Are we really THAT bored that we have to completely dissect a code snippet that was posted instead of just answering the simple question asked? One thing at a time.

This place can be intimidating enough for neophytes. No need for the information overload.

Bored? Kinda. I'm working from home and, in many ways, its even worse than the late shift when I went into work. The number of distractions there were fewer so I tended to concentrate.

That said, being bored is no real excuse for taking that boredom out on the OP.

[Hitch]

Originally Posted by DiapDealer

OK folks. Enough of the unasked for advice. It's starting to feel a bit like the OP is being ganged up on. Are we really THAT bored that we have to completely dissect a code snippet that was posted instead of just answering the simple question asked? One thing at a time.

This place can be intimidating enough for neophytes. No need for the information overload.

I'm absolutely that bored. While my biz is still muttering along, the entire damn world feels like we're in a GradeC Made-for-SciFi movie. It's tedious as hell.

(Altho I do agree, ganging up is not needed for any purpose. Forums...it's always the way...everybody does it, albeit here typically well-intentioned...)

Hitch