Re: Improvements for cross-referencing
On 4/8/20 8:05 AM, Daniel wrote:
> Just a couple of rough ideas that I think would improve working with
> cross-references. Maybe some of them are already worked on. I'd be
> interested to know.
>
> I guess one of the advantages of LyX is that working with texts is
> pretty nice even without generating a preview. Seeing versions of
> references that indicate their content, as is already the case for
> citations, is helpful in that respect.
>
> Maybe there could be a switch for this between (global) content labels
> and prefix+label-name labels because some people might like to see
> label names rather than content previews (although a tool-tip should
> also reveal the prefix+label-name, I guess)?
>
> The content-previews have already been (partly) implemented for
> LyXHTML. For example, a reference to the first numbered section shows
> "Section 1" (though currently this reference appears only in capitals
> rather than being responsive to the capitalization feature in LyX). I
> guess the LyXHTML of a reference and its content preview should be the
> same and progress made on one part can be used in the other. Due to
> recent progress, counters are highly customizable which makes content
> labels even more attractive. For textual references, the content of
> the element could be used that is already shown in the outliner.
I did think about this when doing the LyXHTML work, precisely for the
reasons you mention, but never got around to implementing it. I doubt it
would be terribly difficult to do at this point. Maybe a good summer
project for me.
> Ideally, these "labels" would be customizable so that the content
> label string can be customized in the same way as label strings and
> counters (as in "section \thesection" and "(\roman{enumiii})"). Again
> some shared features. There would be commands for different cross
> reference types, maybe "RefLabelString", "EqRefLabelString",
> "FormatLabelString", and "NameRefLabelString". Again, these
> customization could be utilized by LyXHTML as well.
We have the PrettyFormat tag, which is what controls the HTML output of
formatted references. What are you imagining that the others would do?
(FYI, all that was done before I added refstyle support. That's why the
caps and plurals aren't supported (yet).)
You're also right, of course, that this could be used in the TOC.
Riki
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Build failed in Jenkins: Build branch "master" ยป ubuntu-xenial-qt4-autotools-extended #1853
https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/1853/--
[...truncated 1575 lines...]
chmod a-w lyx-2.4.0dev
test -d lyx-2.4.0dev/_build || exit 0; \
dc_install_base=`CDPATH="${ZSH_VERSION+.}:" && cd lyx-2.4.0dev/_inst && pwd |
sed -e 's,^[^:\\/]:[\\/],/,'` \
&& dc_destdir="${TMPDIR-/tmp}/am-dc-$$/" \
&& am__cwd=`pwd` \
&& CDPATH="${ZSH_VERSION+.}:" && cd lyx-2.4.0dev/_build/sub \
&& ../../configure \
\
\
--srcdir=../.. --prefix="$dc_install_base" \
&& make \
&& make dvi \
&& make check \
&& make install \
&& make installcheck \
&& make uninstall \
&& make distuninstallcheck_dir="$dc_install_base" \
distuninstallcheck \
&& chmod -R a-w "$dc_install_base" \
&& ({ \
(cd ../.. && umask 077 && mkdir "$dc_destdir") \
&& make DESTDIR="$dc_destdir" install \
&& make DESTDIR="$dc_destdir" uninstall \
&& make DESTDIR="$dc_destdir" \
distuninstallcheck_dir="$dc_destdir" distuninstallcheck; \
} || { rm -rf "$dc_destdir"; exit 1; }) \
&& rm -rf "$dc_destdir" \
&& make dist \
&& rm -rf lyx-2.4.0dev.tar.gz lyx-2.4.0dev.tar.xz \
&& make distcleancheck \
&& cd "$am__cwd" \
|| exit 1
configuring LyX version 2.4.0dev
checking for build type... development
checking for version suffix...
checking whether Qt5 is disabled... no
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking what packaging should be used... posix
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether UID '0' is supported by ustar format... yes
checking whether GID '0' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking for a Python interpreter with version >= 2.7.0 or 3.5.0... python3
checking for python3... /usr/bin/python3
checking for python version... 3.5
checking for python platform... linux
checking for python script directory... ${prefix}/lib/python3.5/site-packages
checking for python extension module directory...
${exec_prefix}/lib/python3.5/site-packages
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for ar... ar
checking the archiver (ar) interface... ar
checking for ranlib... ranlib
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking whether the compiler is clang... no
checking for at least C++11 mode... -std=c++14
checking whether STL is libstdc++... yes
checking whether STL is libstdc++ using the C++11 ABI... yes
checking for correct regex implementation... yes
checking for std::call_once availability... yes
checking for gcc... gcc
checking whether we are using the GNU Objective C compiler... no
checking whether gcc accepts -g... no
checking dependency style of gcc... gcc3
checking dependency style of gcc... (cached) gcc3
checking for extra library directory... NONE
checking for extra include directory... NONE
checking for extra lib+include directory... NONE
checking for main in -lshlwapi... no
checking for main in -lpsapi... no
checking for main in -lgdi32... no
checking for main in -lole32... no
checking whether to use included boost library... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking whether printing callstack is possible... (cached) yes
checking whether make_unique is defined by header memory... yes
checking size of wchar_t... 4
checking for wchar_t... yes
checking for unsigned long long int... yes
checking for long long int... yes
checking for ld used by
Re: Improvements for cross-referencing
On 2020-04-08 14:05, Daniel wrote: The content-previews have already been (partly) implemented for LyXHTML. For example, a reference to the first numbered section shows "Section 1" (though currently this reference appears only in capitals rather than being responsive to the capitalization feature in LyX). I guess the LyXHTML of a reference and its content preview should be the same and progress made on one part can be used in the other. These labels could also be used in the outliner. Currently, I have a number of non-descriptive entries in the TOC where I use NameRefs, such as 4. # reconsidered and the # It would be nicer to see the NameRef content instead of the hash. Daniel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
