How to handle missing <sense> tags

[nkprasad12]

I've been making some corrections in a local repository for my personal use.

For a few entries I notices that what was intended to be an individual "sense" entry was accidentally included as part of another, i.e I see
<sense ... >[sense X text] (α) [sense Y text]<sense>

I would like to add the missing sense tag, so that it's: <sense ... >[sense X text]</sense><sense>[sense Y text]<sense>, but I'm unsure of which ID I should assign to the new sense. Should the new sense be given:

• the lowest free ID (which preserves backwards compatibility, but meaning the IDs aren't in order anymore), or
• the ID in "order" (which requires changing all sense items that come after)?

e.g. should

<sense id="n123.6" >[sense X text] (α) [sense Y text]</sense>
<sense id="n123.7">[sense Z text]</sense>`

become

<sense id="n123.6" >[sense X text]</sense>
<sense id="n123.8">[sense Y text]</sense>
<sense id="n123.7">[sense Z text]</sense>

or

<sense id="n123.6" >[sense X text]</sense>
<sense id="n123.7">[sense Y text]</sense>
<sense id="n123.8">[sense Z text]</sense>

[lcerrato]

@nkprasad12
Hi,
we generally supplement with a, b, c etc. for missing entries or missing senses.

[nkprasad12]

Thanks @lcerrato - I was also wondering how the two versions of L&S in this repo are kept in sync. Is there a way to generate one from the other? Or do changes need to be manually applied to both documents?

[lcerrato]

@nkprasad12
There is very little active editing so I manually change both versions.
We should probably just adopt the Unicode version, but the repository is still in transition and I need to be sure that downstream resources are not affected.