lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Issue with Embedding LilyPond Files in Second Column of LaTeX Table


From: Peter X
Subject: Issue with Embedding LilyPond Files in Second Column of LaTeX Table
Date: Fri, 16 Aug 2024 09:29:48 -0700

Dear LilyPond Community,

I hope this message finds you well. I'm reaching out because I've encountered an issue when attempting to embed LilyPond files into the cells of a LaTeX table, specifically when these files are placed in the second column of the table.

### Issue Description:
When I embed LilyPond files in the **first column** of a table, everything works as expected, and the table renders without any issues. However, when I try to place a LilyPond file in the **second column**, the compilation fails with the following error:

```plaintext
stack traceback:
        [C]: in function 'error'
        ...al/texlive/2024/texmf-dist/scripts/lyluatex/lyluatex.lua:1315: in function 'lyluatex.lua.file'
        [\directlua]:1: in main chunk.
        ...
l.1720 ...{file_02_unfold.ly}}
                                        \\ \hline
```

### Table Structure:
Here’s a simplified version of the table structure I'm working with:

```latex
\begin{table}[H]
    \centering
    \small
    \caption{Example Table}
    \label{tab:example}
    \begin{tabular}{|c|c|}
    \hline
    \textbf{Column 1} & \textbf{Column 2} \\ \hline
    Placeholder 1 & Placeholder 2 \\ \hline
    \lilypondfile[staffsize=10, noindent]{file_01.ly} & Placeholder 4 \\ \hline
    \lilypondfile[staffsize=10, noindent]{file_02.ly} & Placeholder 6 \\ \hline
    \lilypondfile[staffsize=10, noindent]{file_03.ly} & Placeholder 8 \\ \hline
    \end{tabular}
\end{table}
```

### Observations:
- Embedding in the **first column** works perfectly.
- Attempting to embed LilyPond files in the **second column** causes the error mentioned above.
- The issue persists even after trying to encapsulate the LilyPond code within `\minipage` or `\parbox`.

### Request for Assistance:
Has anyone encountered a similar issue or have any insights on why embedding in the second column might be causing this problem? I would appreciate any guidance or suggestions on how to resolve this issue while maintaining the intended table structure.

Thank you for your support!

Best regards,  
Peter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]