Index-related entries

[trshemanske]

Created with explanatory text since I presume the Index entries will not be rendered.

[trshemanske]

Yes; this is why I raised this question in an earlier email.

The real issue for me is that rendering the index occurs only in backmatter, so would the example have two fragments, one with section and one with backmatter?, e.g.,

<FRAGMENT parents="section subsection">
<definition xml:id="def-subgroup">
  <statement>
    <p>
      A <term>subgroup</term> <m>H</m> of a group <m>G</m> is <ellipsis/>.
      <idx><h>subgroup</h></idx>
    </p>
  </statement>
</definition>
</FRAGMENT>

<FRAGMENT parents="backmatter">
 <title>Backmatter</title>
      <index>
        <title>Index</title>
        <index-list/>
      </index>
</FRAGMENT>

Do you think that will render in your system?

That is why I included explanatory text. If the Index will render as I suggested above, happy to make the changes

Tom

On Mon, Nov 11, 2024 at 3:20 PM Jason Siefken @.***> wrote:

@.**** commented on this pull request.

In packages/docs/pages/reference/elements/h.mdx https://github.com/siefkenj/pretext-book/pull/103#discussion_r1837151090 :

+notation\trianglelefteq +normal subgroup + + + +In the example above, we gave a reference to a `normal subgroup`, but the only +Index entry is to `normal` as a subcategory to `subgroup`. To clarify this, we +may want to include either a standalone entry for `normal subgroup`, or perhaps if one is also going to discuss normal field extensions, to +include it as a secondary entry under `normal`. + +ptx-example + +normal subgroup + +<normalfield extensionGalois +<normalsubgroup

If I understand correctly, these examples won't render anything because they only show up in the index? If so, I think rendering the index should be part of the example.

— Reply to this email directly, view it on GitHub https://github.com/siefkenj/pretext-book/pull/103#pullrequestreview-2428097817, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANHA5DADCWUZ3AIWATNGFK32AEGP5AVCNFSM6AAAAABRQSC6IKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDIMRYGA4TOOBRG4 . You are receiving this because you authored the thread.Message ID: @.***>

-- Thomas R. Shemanske Grantham, NH

[siefkenj]

Ah, I haven't responded to that email.

No, everything should go in one fragment. Something like

<FRAGMENT>
<section><subsection>
<definition xml:id="def-subgroup">
  <statement>
    <p>
      A <term>subgroup</term> <m>H</m> of a group <m>G</m> is <ellipsis/>.
      <idx><h>subgroup</h></idx>
    </p>
  </statement>
</definition>
</section></subsection>

<backmatter>
 <title>Backmatter</title>
      <index>
        <title>Index</title>
        <index-list/>
      </index>
</backmatter>
</FRAGMENT>

fragments have no way to "talk to each other", so separate fragments would not be able to reference material from one another.