MadCap Lingo Versionen

MadCap SoftwareWerkzeuge zur Dokumenterstellung
Version 12.x (30. Apr. 2026)

Erfahren Sie, was sich in den einzelnen Releases geändert hat – mit Details zu Funktionen, Verbesserungen und behobenen Problemen.

Jan
Feb
Mär
Apr
Mai
Jun
Jul
Aug
Sep
Okt
Nov
Dez
MadCap Lingo 12 (Build: 12.0.9616)Hauptversion30. Apr. 2026
Funktionen
  • Command Line Enhancements:
    • Create projects from the command line.
    • Reference JSON files.
    • Many more commands available.
  • File List Progress Column:
    • See the progress of each file.
    • Shown in percentages.
  • Microsoft Translator Region:
    • Select a specific region when using Microsoft Translator.
    • Helps prevent issues with machine translation.
  • Pseudo Translate:
    • Pre-translate files with pseudo translate.
    • Helps to see how translations might affect page structure.
  • QA Reports Ignore Case:
    • Improve report results by ignoring case.
    • Use for inconsistency in translation of repeated source segments.
    • Also used for repeated target segments with varying source.
  • Translation Memory (TM) Suggestion Highlight:
    • Changed content is highlighted when using translation memory.
    • Helps with usability.
Korrekturen
  • Align project does not align the file list upon project creation despite the file names being identical.
  • Applying Translation Memory to project is causing Tag errors.
  • Changes are not showing in Lingo after a Diff.
  • Performing a project update in Git bound Lingo project results in generation of <ph> tags in topics.
  • Lingo - Update project (bound to Git) causes files to revert back to untranslated status shown by diffing.
  • Conditioned stylesheet classes are not being honored when filtering by target and do a project update.
  • Update fails with "'MadCap' is an undeclared prefix." error if updated files are missing MadCap namespace.
  • Updated the SQL Server Express download URL.
  • Single quotes added around URL in content tag.
  • Space is being appended at the beginning of exported segments in this project.
  • Parts of a Lingo project are reverting to English after export.
  • Translating variables with a comma removes deliminator backslash from exported projects. 
  • Lingo Command Line: Re-Exporting with -appendLanguage deletes existing content OR duplicates language code at end of topic.
  • Untranslated segments in exported Flare project after merging bundles from translation tools although the segments are translated in Lingo. 
  • Missing SVG Images when exporting Lingo project back to Flare.
  • Snippets with conditions are imported without honoring topic snippet conditions and exporting conditioned out text when flattened in Lingo.
  • Lingo strips everything after the :root in stylesheet when exporting Project.
  • Lingo adds a space between image and condition tag in exported project.
  • Translated flattened block snippet has extra p tags in the exported project.
  • Lingo to support Trademark symbol in file names.
  • Spaces between sentences should not be preserved when translating to Japanese.
  • Missing Files after Updating the Lingo project.
  • Replace all does not work and returns with errors.
  • Files referenced in linked tocs aren't getting added for translation when filtering by target.
  • Lingo: Conditions applied to variables are lost when flattened.
  • Micro Content is not included for translation when filtering by target.
  • Language Skin generated in Lingo does not appear when a filter is selected.
  • Not able to add a client name when creating project from command line.
  • Not able to set a File filter connection when creating project from command line.
  • Lingo - not able to set Termbase connection when creating project from command line.
  • Title and alt text for buttons are not being parsed for translation.
  • Getting unable to parse errors for files that include this svg image.
  • Lingo imports files not associated with the TOC when filtering by target — if the target has a template page assigned and that template page includes a FAQ proxy linked to a micro content file containing linked topics.
  • Files marked with an exclude condition in the TOC are still imported into Lingo when filtering by target— if the target has a template page assigned and that template page includes a FAQ proxy linked to a micro content file containing linked topics.
  • Lingo imports files not associated with the TOC when filtering by Print targets.
  • Files marked with excluded condition in the TOC are still imported into lingo when filtering by Print targets.
  • Files marked with excluded condition in the TOC are still imported into lingo when filtering by target.
  • Lingo imports files not associated with the TOC when filtering by target.
  • MadCap | submitQuestionButton does not get registered as a string that needs to be translated.
  • Custom stylesheet classes with path to image files are exported wrapped with quotes.
  • Getting Unable to parse headerFile.h into Xliff when importing any Flare project in debug mode.
  • Not all custom UI Text is listed for translation under the skin file.
  • Importing a ZIP is causing exceptions.
  • Lingo: Text with "\" in a snippetVariable is not being extracted from a Flare project into Lingo.
  • Text between two code elements do not show up as its own text in Lingo.
  • When segment includes cross reference followed by hyperlink using variable URL, variable is included as plain text and switched with cross reference.
  • "Failed to open startup file: Specified argument was out of the range of valid values. Parameter name: <br> node not supported in xliff 1.2" when topic contains a br tag inside of a conditionalized table within a list and the condition is excluded.
  • log4j-core-2.9.0.jar Vulnerability.
  • ORE when translating with DeepL or MT caused by specific element structure in Flare project.
  • Lingo command line option to create an XLIFF bundle is case-sensitive.
  • Sending a topic with snippet conditions shows the conditioned out content when translating the bundle and when it's merged back.
  • Generating a Bundle causes System ArgumentOutOfRangeException: "Parameter name: <MadCap:snippetBlock> node not supported in xliff 1.2".
  • XLF files are corrupted after creating a bundle and results in extra / incorrect segments.
  • Lingo Crashes when generating an Xliff Bundle.
  • Lingo 11 r3 QA report links open preview of file.
  • If Source XLF doesn't have seg-source elements, Lingo with throw Object Reference Error when running QA Project and translate with MT.
  • MadCap Lingo: Spaces are lost when splitting segments in Lingo.
  • SRX tool is not getting applied when there's a span wrapping content.
  • Unable to save the correct tags to TM causing a mismatch.
  • Constraint Failed: "Unique constraint Failed: Markup.segment_id.Markup.Location when uploading a file in this project to a local TM.
  • Getting an exception followed by a hard crash when opening a topic that contains text followed by more text styled with a css variable.