Great call going with TexSoup instead of regex—you’re right that regex would quickly fall apart with nested LaTeX structures like your \tasks command. TexSoup parses LaTeX into a structured tree, so extracting those key-value pairs is straightforward once you know how to access the right attributes.

Here’s how to turn those \newcommand entries into a Python dictionary:

from TexSoup import TexSoup

# Load the LaTeX file
soup = TexSoup(open('slatex.tex'))
newcommands = list(soup.find_all('newcommand'))

# Build the key-value dictionary
latex_vars = {}
for cmd in newcommands:
    # Extract the command name (strip the leading backslash)
    cmd_name = str(cmd.args[0]).strip('\\')
    # Extract the full value (preserves nested LaTeX)
    cmd_value = str(cmd.args[1])
    latex_vars[cmd_name] = cmd_value

# Test it out—this will show the full itemize block for \tasks
print(latex_vars['tasks'])

Breakdown of the Code: #

• Each cmd in newcommands is a TexCmd object. The args attribute holds the two arguments passed to \newcommand:
  • cmd.args[0] is the command name (e.g., \startDate). Converting it to a string and stripping the backslash gives you your dictionary key.
  • cmd.args[1] is the content inside the second set of braces. Converting this to a string preserves all nested LaTeX (like the itemize environment for \tasks), which regex would struggle to capture correctly.

Updating Values and Writing Back to LaTeX #

Once you have user input from your Django form, you can modify the TexSoup object directly and save it back to the file. For example:

# Example: Update project name with user input
user_project_name = "My Awesome Django Project"
for cmd in newcommands:
    cmd_name = str(cmd.args[0]).strip('\\')
    if cmd_name == 'projectName':
        # Replace the placeholder with user input
        cmd.args[1] = user_project_name
        break

# Write the modified LaTeX to a new file
with open('updated_slatex.tex', 'w') as f:
    f.write(str(soup))

This approach safely handles special LaTeX characters and nested structures—something regex can’t reliably do without complex recursive patterns.

Why TexSoup Beats Regex Here #

Regex might work for simple one-line commands, but for multi-line values with nested braces (like \tasks), you’d need a recursive regex to match the correct closing brace. That’s tricky to implement and prone to breaking if your LaTeX structure changes. TexSoup’s parsed tree approach avoids all that headache.

Hope this helps you build your dynamic form and PDF generation workflow smoothly!

Content sourced from Stack Exchange, question by user3687308