special question about cross-references

[autocart]

Hello,
I am still evaluating Flare. Anyway, I am wondering ...

Sometimes I want to cross reference other chapters by name (like "see chapter XY").
Sometimes these are shorter sub-chapters, of which even 2 or 3 might fit on the same page.
In some special cases, one of these sub-chapters, which I want to reference from another sub-chapter (on the same hirarchy level), happens to be the very next sub-chaper (right after the one from where I want to reference it).

In this case I don't want the reference to say "see chapter XY", but to say "see next chapter".
Of course the cross reference should be smart enough so that in case that I change the structure of the chapters (e.g. if I insert another chapter inbetween these two or if I move one of the two chapters), that the cross reference also changes its text (on its own, whithout having to touch it) accordingly to "see chapter XY" and vice versa.

Is this possible? (I hope I explained it well enough.)

[NorthEast]

Try {pageref} - it's a context-sensitive cross-reference.
It's in the help: http://help.madcapsoftware.com/flare2017r2/Content/Nav-Links/Shared/Cross-References/Creating-Context-Sensitive-Cross-References.htm

[Nita Beck]

I think you've explained it well enough. Unfortunately, I don't think that there's a way for Flare to render xrefs such as "See next chapter" or "See previous chapter".

However, it can easily do something similar for pages, as in "See 'xxx' (next page)" or "See 'xxx' (below)". The term of art is a "context-sensitive cross-reference". You can read more about them here: http://help.madcapsoftware.com/flare201 ... rences.htm.

I'm not sure that you're going to be Flare to refer to chapters as "above/previous" or "below/next" because, by design and assuming you're using the {chapnum} auto-number format, each chapter will need to start on a new page. Breaking to a new page is necessary for the {chapnum} counter to increment.

HTH

(Hi Dave! Didn't see you standing there!)

[autocart]

Hello u 2,
Thx for the answers. Helped a lot.
I found that one can (even) customize the terms used by those context sensitive xrefs (see picture below, ).

2 new question, though:

1) Can I disable some of these formats, e.g. if I do not (ever) want the {pageref} to turn into "on the facing page", can I disable the CrossReferenceOnFacingPage-format all together (instead of "just" changing the text)?

2) I am thinking, maybe, by adjusting those replacement-texts in the language skin, I could to what I originally intended after all.
However, it would make sense to have different sets of "mappings" defined for these context sensitive xrefs in order not to loose the original or "normal" mapping.
For this purpose, could I not use other languages as well to define different mappings in those other languages and then, depending on which behavior I want, I assign the corresponding language to each context sensitive xref?
Or is there an official/better way of how to do that than using such a work around (if it would even work this way)?