5. Regex and XPath - Recent Threads

RE: Translation / Review of texts exported from Wordpress

RWS Community AI — Tue, 17 Feb 2026 14:39:12 GMT

Probability score: 0.6

Question improvement suggestion: Provide specific details about the XML structure and any error messages encountered during the import process to help clarify the issue.

In the meantime, based on the information you have provided, here is a suggested answer to your question:

Hello Daniela,

Thank you for your question regarding handling XML files from WordPress in Trados Studio. Here’s a step-by-step approach to help you with your situation:

**Step 1:** **Create a Custom XML File Type**

Since you mentioned needing to create a custom XML file type, you can do this by going to `File > Options > File Types > New`. Choose XML and define the settings based on your XML structure. Make sure to specify the correct element rules to extract the translatable content.

**Step 2:** **Preview the XML File**

Once you have created the custom file type, you can preview the XML file in Trados Studio. This will help you see how the content is structured and ensure that the translatable text is correctly identified.

**Step 3:** **Consider Exporting XLIFF from WordPress**

If the client is open to it, exporting XLIFF files from WordPress would simplify the process significantly. XLIFF is a format that Trados Studio handles well, and it would eliminate the need for custom XML configurations.

**Step 4:** **Addressing Errors in XML Files**

For the `XPress_invalidStructure.xml` file, ensure that the XML adheres to proper formatting rules. If there are keys that do not appear in all languages, it may indicate an issue with the original export. In such cases, contacting the client for a new export may be necessary.

**Step 5:** **Handling Multi-line Texts**

For multi-line texts, ensure that your custom XML file type can handle these correctly. You may need to define specific rules for handling line breaks and empty lines.

**Step 6:** **Testing and Iteration**

After setting up the custom file type, test it with the provided XML files. If you encounter issues, review the XML structure and adjust the file type settings accordingly.

If you need further assistance, please feel free to reach out with more specific details about the XML structure or any error messages you encounter.

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

RWS Community AI

Translation / Review of texts exported from Wordpress

Daniela Badel — Mon, 16 Feb 2026 15:10:05 GMT

Hello,

once again I have a question about handling xml files from WordPress in Trados Studio.

We received some sample files from a client in order to make some tests (see enclosed files).

I know I would have to create a custom xml filetype to handle these files, but I am not quite sure if it is even possible to handle them as the client wishes.

Wouldn't it be easier to export xliff from Wordpress?

File: XPress_allCases.xml

This file shows that multi-line texts are also possible.

See Key: general.dieSet.rfid.readIdsError

Even those with empty lines.

See Key: general.waitingToEjectDischarge

These keys are not identical and should therefore be treated as separate texts:

Key A: messages.ctrlClass.FB_BALO.10_cause

Key B: messages.ctrlClass.FB_BALO.fbBackLoad.10_cause

File: XPress_invalidStructure.xml

There is an error in this file, and unfortunately also in the original file.

Key: zeroGapWidthFlex

Keys that do not appear in all languages indicate an error on our part.

This can happen, and in such cases, you are welcome to contact us and request a new export.

Depending on the order, we may not want to check existing texts in the target languages. In this case, we will ignore them as we have done with Excel up to now.

Thank you very much for your support!

Daniela[View:/cfs-file/__key/communityserver-discussions-components-files/171/XPress_5F00_examples.zip:900:600]

Default namespace in custom XML 2 file type

Gil Ferraz Maio Gomes — Mon, 16 Feb 2026 09:24:23 GMT

Hi,

I'm currently using Trados Studio 2022 SR2 CU10.

I've recently migrated a custom XML file type from v1 to v2. I added all the prefixed namespace mappings (except the default namespace).

When testing the file type, I noticed that most parser rules work fine, except if they include a mention to any attribute without a namespace prefix.

For example:

XPath	Status
//doc	OK
//doc[@name='question']	NOK
//doc[@*[local-name() = 'name'] = 'question' ]	NOK

Curiously enough, when I remove the default namespace from my XML document, rules which reference attributes seem to work again.

I've tried adding the default namespace to the namespace mapping, both during and after the XML file type migration, but it always returns a "Enter a value for Prefix." error.

Could you please help me figure out how to solve this issue?

Thanks!

set a file type for a specific xml office:spreadsheet

Chiara Bizzotto — Wed, 11 Feb 2026 13:17:29 GMT

Hello. I need to translate an xml file. I use Trados Studio Professional 2024 SR1 18.1.3.6657. Below I pasted an extract of the file.

First, I have opened the xml file in Excel and have hidden the columns and raws that do not require translation. Then I created a Studio project with this Excel file, enabling embedded content.

I have tried to set the "XML 2: Any XML" file type to exclude html entities and all the stuff that does not require translation, but I still have many "rubbish" in the file. My problem is both with extra texts and with entities such as  ,   , etc.

I would need a file type so that Trados only shows what actually needs to be translated.

Thank you for your help!

<?xml version="1.0"?>
<Workbook xmlns:x="urn:schemas-microsoft-com:office:excel"
xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet"
xmlns="urn:schemas-microsoft-com:office:spreadsheet">
<DocumentProperties xmlns="urn:schemas-microsoft-com:office:office">
<Author>L10N Manager</Author>
<LastAuthor>Daniel Zielinski</LastAuthor>
<Created>2011-08-23T02:10:16Z</Created>
<Version>11.512</Version>
</DocumentProperties>
<OfficeDocumentSettings xmlns="urn:schemas-microsoft-com:office:office">
<AllowPNG/>
</OfficeDocumentSettings>
<ExcelWorkbook xmlns="urn:schemas-microsoft-com:office:excel">
<WindowHeight>14200</WindowHeight>
<WindowWidth>28700</WindowWidth>
<WindowTopX>-20</WindowTopX>
<WindowTopY>-20</WindowTopY>
<Date1904/>
<AcceptLabelsInFormulas/>
<ProtectStructure>False</ProtectStructure>
<ProtectWindows>False</ProtectWindows>
</ExcelWorkbook>
<Styles>
<Style ss:ID="Default" ss:Name="Normal">
<Alignment ss:Vertical="Bottom"/>
<Borders/>
<Font ss:FontName="Verdana"/>
<Interior/>
<NumberFormat/>
<Protection/>
</Style>
<Style ss:ID="s25">
<Alignment ss:Vertical="Top"/>
</Style>
<Style ss:ID="s26">
<Alignment ss:Vertical="Top"/>
<Font ss:FontName="Verdana" ss:Bold="1"/>
</Style>
<Style ss:ID="s27">
<Alignment ss:Vertical="Top" ss:WrapText="1"/>
</Style>
<Style ss:ID="s35">
<Font ss:FontName="Verdana" ss:Size="18.0" ss:Bold="1"/>
<Interior ss:Color="#969696" ss:Pattern="Solid"/>
</Style>
<Style ss:ID="s37">
<Font ss:FontName="Verdana" ss:Size="14.0" ss:Bold="1"/>
<Interior ss:Color="#C0C0C0" ss:Pattern="Solid"/>
</Style>
<Style ss:ID="s38">
<Font ss:FontName="Verdana" ss:Bold="1"/>
<Interior ss:Color="#969696" ss:Pattern="Solid"/>
</Style>
<Style ss:ID="s39">
<Alignment ss:Vertical="Top" ss:WrapText="1"/>
<Borders>
<Border ss:Position="Bottom" ss:LineStyle="Continuous" ss:Weight="1"/>
<Border ss:Position="Left" ss:LineStyle="Continuous" ss:Weight="1"/>
<Border ss:Position="Right" ss:LineStyle="Continuous" ss:Weight="1"/>
<Border ss:Position="Top" ss:LineStyle="Continuous" ss:Weight="1"/>
</Borders>
<Interior ss:Color="#FFFF99" ss:Pattern="Solid"/>
</Style>
<Style ss:ID="s40">
<Font ss:FontName="Verdana" ss:Bold="1"/>
<Interior ss:Color="#ff0033" ss:Pattern="Solid"/>
<Borders>
<Border ss:Position="Bottom" ss:LineStyle="Continuous" ss:Weight="1"/>
<Border ss:Position="Left" ss:LineStyle="Continuous" ss:Weight="1"/>
<Border ss:Position="Right" ss:LineStyle="Continuous" ss:Weight="1"/>
<Border ss:Position="Top" ss:LineStyle="Continuous" ss:Weight="1"/>
</Borders>
</Style>
</Styles>
<Worksheet ss:Name="Translation">
<Table ss:ExpandedColumnCount="6" ss:ExpandedRowCount="5543" x:FullColumns="1" x:FullRows="1">
<Column ss:Hidden="1" ss:AutoFitWidth="0"/>
<Column ss:AutoFitWidth="0" ss:Width="85.0"/>
<Column
ss:AutoFitWidth="0" ss:Width="233.0" />
<Column
ss:Hidden="1" ss:AutoFitWidth="0" />
<Column ss:AutoFitWidth="0" ss:Width="233.0"/>
<Column ss:AutoFitWidth="0" ss:Width="151.0"/>


<Row>
<Cell ss:Index="2" ss:StyleID="s35"><Data ss:Type="String">Home [1]</Data></Cell>
<Cell ss:StyleID="s35"></Cell>
<Cell ss:StyleID="s35"></Cell>
<Cell ss:StyleID="s35"></Cell>

</Row>

<Row>
<Cell ss:Index="2" ss:StyleID="s38"><Data ss:Type="String">Fieldname:</Data></Cell>
<Cell ss:StyleID="s38"><Data ss:Type="String">Source language:</Data></Cell>
<Cell ss:StyleID="s38"><Data ss:Type="String">Alternative source language:</Data></Cell>
<Cell ss:StyleID="s38"><Data ss:Type="String">Translation:</Data></Cell>
<Cell ss:StyleID="s38"><Data ss:Type="String">Difference since last tr.:</Data></Cell>
</Row>

<Row>
<Cell ss:Index="2" ss:StyleID="s37"><Data ss:Type="String">Element: pages:1</Data></Cell>
<Cell ss:StyleID="s37"></Cell>
<Cell ss:StyleID="s37"></Cell>
<Cell ss:StyleID="s37"></Cell>

</Row>


<Row ss:StyleID="s25">
<Cell><Data ss:Type="String">translation[pages][1][pages:NEW/1/1:title]</Data></Cell>
<Cell ss:StyleID="s26"><Data ss:Type="String">title</Data></Cell>
<Cell ss:StyleID="s27"><Data ss:Type="String">Home</Data></Cell>
<Cell ss:StyleID="s27"><Data ss:Type="String"></Data></Cell>
<Cell ss:StyleID="s39"><Data ss:Type="String"></Data></Cell>
<Cell ss:StyleID="s27"><Data ss:Type="String">[New value]</Data></Cell>
</Row>


<Row ss:StyleID="s25">
<Cell><Data ss:Type="String">translation[pages][1][pages:NEW/1/1:shortcut]</Data></Cell>
<Cell ss:StyleID="s26"><Data ss:Type="String">shortcut</Data></Cell>
<Cell ss:StyleID="s27"><Data ss:Type="String">0</Data></Cell>
<Cell ss:StyleID="s27"><Data ss:Type="String"></Data></Cell>
<Cell ss:StyleID="s39"><Data ss:Type="String"></Data></Cell>
<Cell ss:StyleID="s27"><Data ss:Type="String">[New value]</Data></Cell>
</Row>


<Row ss:StyleID="s25">
<Cell><Data ss:Type="String">translation[pages][1][pages:NEW/1/1:shortcut_mode]</Data></Cell>
<Cell ss:StyleID="s26"><Data ss:Type="String">shortcut_mode</Data></Cell>
<Cell ss:StyleID="s27"><Data ss:Type="String">0</Data></Cell>
<Cell ss:StyleID="s27"><Data ss:Type="String"></Data></Cell>
<Cell ss:StyleID="s39"><Data ss:Type="String"></Data></Cell>
<Cell ss:StyleID="s27"><Data ss:Type="String">[New value]</Data></Cell>
</Row>


<Row ss:StyleID="s25">
<Cell><Data ss:Type="String">translation[pages][1][pages:NEW/1/1:description]</Data></Cell>
<Cell ss:StyleID="s26"><Data ss:Type="String">description</Data></Cell>
<Cell ss:StyleID="s27"><Data ss:Type="String">Das Almwellness Hotel Pierer vereint Wellness & Genuss, Natur & Erholung. Im Almenland erleben Sie das ganze Jahr über einen besonderen Urlaub! ► Mehr</Data></Cell>
<Cell ss:StyleID="s27"><Data ss:Type="String"></Data></Cell>
<Cell ss:StyleID="s39"><Data ss:Type="String"></Data></Cell>
<Cell ss:StyleID="s27"><Data ss:Type="String">[New value]</Data></Cell>
</Row>

RE: set a file type for a specific xml office:spreadsheet

Chiara Bizzotto — Mon, 16 Feb 2026 08:56:02 GMT

I just wrote a private message to you

RE: set a file type for a specific xml office:spreadsheet

Katharina Schuhmann — Mon, 16 Feb 2026 08:45:17 GMT

I've sent you a forum friendship request. I hope we can then exchange private messages. I don't really like posting my email address here in the public forum.

RE: set a file type for a specific xml office:spreadsheet

Chiara Bizzotto — Mon, 16 Feb 2026 08:42:03 GMT

Thank you very much for your availability. For confidentiality reasons, I would prefer to send you the file by email. Would that be possible, please? Thank you.

RE: set a file type for a specific xml office:spreadsheet

Katharina Schuhmann — Mon, 16 Feb 2026 08:36:55 GMT

Ok, thanks. Then I would suggest working with the XML because otherwise it would be hard for you to generate the target XML from the Excel. Could you attach the entire XML file here? Then I can download it and see if I can configure the filetype for you. Normally it's not that hard. :)

RE: set a file type for a specific xml office:spreadsheet

Chiara Bizzotto — Mon, 16 Feb 2026 07:48:25 GMT

Hi Katharina, thank you for your kind reply. First, I tried to work directly with the xml file, but there are so many entities and html codes inside that need to be handled. So, I opened it in Excel because I read "office:spreadsheet" in the first raws of the file, hoping it was easier to set the file type. The requirement for me is to deliver a translated xml. Thank you

RE: set a file type for a specific xml office:spreadsheet

Katharina Schuhmann — Mon, 16 Feb 2026 06:46:15 GMT

Hi Chiara Bizzotto ,

Just to clarify, why would you open an XML file in Excel and then translate the Excel in Trados Studio? Why not directly translate the XML file.

Btw, if you use the Excel file as your source file, you cannot use the filetype 'Any XML'. You'd need to use one of the Excel filetypes available and configure this to your needs.

Could you maybe

1) explain why you would want to translate your XML as an Excel in the first place, and

2) if this is a requirement, then post the Excel file you created?

That would help solving your problem. :)

Regards,
Katharina

RE: Best Approach for Large‑Scale Find & Replace in the Repository?

Jesús Prieto — Mon, 26 Jan 2026 08:34:44 GMT

Christina Rothwell

Probably someone at RWS will need to move your post to a different forum.

Best Approach for Large‑Scale Find & Replace in the Repository?

Christina Rothwell — Thu, 22 Jan 2026 21:11:21 GMT

We have a number of writers who need to run bulk find and replace operations across specific directories within the repository—not just within individual publications. Before we point everyone to manually search within each publication, I wanted to check in with this group.

What’s the recommended or most efficient way to handle cross‑directory find and replace?
Are there tools, scripts, or existing workflows you’d suggest so writers can safely make updates at scale without risking unintended changes?

Any guidance, best practices, or pointers to existing resources would be greatly appreciated. Thank you!

Best,

Christina

Help Needed: Best Method to Search for Element Usage in DITA Repository

Christina Rothwell — Thu, 22 Jan 2026 18:48:41 GMT

We’re currently looking into the best way to search for a DITA element across the repository—specifically, how often and where the <text> element is used in our DITA files.

While testing different search inputs, I’ve noticed some inconsistent behavior:

When I enter "<text cid" in the Find in field, no results appear.
When I enter (without quotes), the search returns a few topics that do contain the <text> element, but the remaining topics in the results list don’t include any instance of <text or text in their markup.
If I simply enter text, the first few topics contain the word text in the body content, but there is no <text> element in the topic coding.

We’re trying to determine the most effective way to identify all actual uses of the <text> element in the repository.

Would you please advise on the correct search syntax or best approach for locating specific DITA elements in the DITA coding of a topic? Any tips or known limitations with the search function would be extremely helpful.

Thanks in advance for your guidance!

Best.

Christina

RE: Help Needed: Best Method to Search for Element Usage in DITA Repository

Christina Rothwell — Thu, 22 Jan 2026 18:53:44 GMT

I tried using //text in the Find in box and it did not work. How can I use the Search feature to find the <text> element in the Repository?

RE: Help Needed: Best Method to Search for Element Usage in DITA Repository

RWS Community AI — Thu, 22 Jan 2026 18:49:04 GMT

Probability score: 0.7

Question improvement suggestion: Provide specific examples of the DITA elements you are searching for and clarify the search tool or method you are using.

In the meantime, based on the information you have provided, here is a suggested answer to your question:

Hello Christina,

To effectively search for a specific DITA element across your repository, you can follow these steps:

**Step 1:** **Use the Correct Search Syntax**

When searching for a specific DITA element, ensure you are using the correct syntax. For example, if you are looking for a specific element like `<title>`, you should enclose it in quotes for an exact match: `"title"`.

**Step 2:** **Utilize Wildcards**

If you are unsure of the exact element name or want to include variations, use wildcards. For instance, you can use `*title*` to find any instance of elements that contain "title" in their names.

**Step 3:** **Check for Inconsistencies**

If you notice that the search results do not include instances of the element in the topic coding, double-check the search settings. Ensure that you are searching in the correct scope (e.g., all files, specific folders) and that there are no filters applied that might exclude certain results.

**Step 4:** **Consider XPath for Advanced Searches**

If you are familiar with XPath, you can create more complex queries to locate elements based on their attributes or hierarchy. For example, to find all `<title>` elements within a specific parent, you could use an XPath expression like `//parentElement/title`.

**Step 5:** **Review Search Limitations**

Be aware of any limitations of the search function you are using. Some tools may not index certain types of content or may have restrictions on searching within tags. Consult the documentation for the specific tool you are using to understand its capabilities.

**Step 6:** **Test Different Approaches**

If you continue to experience inconsistent results, try different search methods or tools. For example, if you are using a specific DITA authoring tool, check if it has built-in search functionalities that might yield better results.

By following these steps, you should be able to improve your search for DITA elements across your repository. If you have any specific examples or further details about the search tool you are using, feel free to share, and I can provide more tailored advice.

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

RWS Community AI

RE: Display notranslate as locked text parts in Studio

RWS Community AI — Tue, 13 Jan 2026 16:37:02 GMT

Probability score: 0.6

Question improvement suggestion: Provide specific details about the XML structure and any existing settings in Trados Studio that you have already tried to implement.

In the meantime, based on the information you have provided, here is a suggested answer to your question:

Hello Johannes,

To display parts marked as `translate="no"` in your XML/DITA file as locked text in Trados Studio, you can follow these steps:

**Step 1:** Create a custom file type for your XML/DITA files in Trados Studio.

- Go to **File > Options > File Types** and create a new file type based on your XML structure.

**Step 2:** Define the Parser Rules.

- In the Parser Rules section, add a rule to extract translatable content using an XPath expression that targets elements with `translate="yes"`. For example, you can use `//*[@translate='yes']` to select translatable elements.

- Add another rule to exclude non-translatable elements, such as `//*` to ensure that only the desired content is extracted.

**Step 3:** Set the Locked Text Display.

- In the settings for your custom file type, ensure that elements with `translate="no"` are set to be displayed as locked text. You may need to use XPath expressions to specify these elements, such as `//*[@translate='no']`.

**Step 4:** Test the Configuration.

- Create a new project using your custom file type and check if the non-translatable parts are displayed as locked text in the editor.

**Step 5:** Adjust as Necessary.

- If the locked text does not appear as expected, revisit your XPath expressions and ensure they correctly target the intended elements.

By following these steps, you should be able to configure Trados Studio to display non-translatable parts as locked text while still being visible for reference.

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

RWS Community AI

Display notranslate as locked text parts in Studio

Johannes Purer — Tue, 13 Jan 2026 16:36:26 GMT

Hi,

I have an xml/dita file, where the client marked some parts as notranslate (translate="no").

How can I define the settings in that datatype, that those parts are still visible in Studio, but locked?

Thanks,

Johannes[View:/cfs-file/__key/communityserver-discussions-components-files/171/appendix_5F00_ic_5F00_statement.dita.xml:900:600]

Need help defining custom HTML tag

Brad Orfall — Tue, 16 Dec 2025 19:40:04 GMT

Trados 2024, Windows 11, HTML files

I have a web page that includes coding for "pop-up" definitions. Basically, the user mouses over a term in blue and the definition of that term pops up. It looks like this:

[Name] does not require that you meet a deductible. Instead, you will pay a copay for services and the plan will immediately begin sharing in the cost of care.

When you move the mouse over "copay", the definition pops up as "A flat fee you pay for covered expenses (usually without paying a deductible)."

The coding looks like this:

<p>
[Name] does not require that you meet a deductible.
Instead, you will pay a
<span
data-bs-html="true"
data-bs-trigger="hover focus"
data-bs-toggle="popover"
data-bs-content="A flat fee you pay for covered expenses (usually without paying a deductible)."
>copay</span
>
for services and the plan will
<strong>immediately</strong> begin sharing in the cost
of care.
</p>

In Trados, I see the text that appears above in the "data-bs-content=" entry within the tag (toggled to display full tag text). I need to make it so that I can access that part of the tag and translate the information.

RE: Need help defining custom HTML tag

Brad Orfall — Wed, 17 Dec 2025 00:02:09 GMT

Thanks for the help! I tried it using the AI advice, but I wasn't seeing it. I think it was me, since I wasn't looking at the next line down for the text to translate. Duh! AI can't fix a lack of human intelligence.

RE: Need help defining custom HTML tag

Paul Filkin — Tue, 16 Dec 2025 23:23:37 GMT

Brad Orfall

All you need to do is add the "data-bs-content" attribute to the Span element as translatable content here:

That should get you this where the "data-bs-content" is extracted from the Span element with the document structure "ATT":

Just in case the AI response didn't help, and you forgot to reject it.

RE: Need help defining custom HTML tag

RWS Community AI — Tue, 16 Dec 2025 19:40:22 GMT

Probability score: 0.7

Question improvement suggestion: Provide specific details about the steps you've already taken to configure the HTML tags in Trados Studio, as well as any error messages or unexpected behavior you've encountered.

In the meantime, based on the information you have provided, here is a suggested answer to your question:

Hello! To define a custom HTML tag in Trados Studio 2024 for your pop-up definitions, follow these steps:

**Step 1:** Open Trados Studio and navigate to **File > Options > File Types > HTML5 > Parser**. Here, you can search for the name of the tag you need to edit.

**Step 2:** Click on **Edit Rule** for the specific tag. In the **Segmentation hint**, change the setting from **May Exclude** to **Include with text**. This will allow the content within the tag to be included in the translation process.

**Step 3:** Ensure that your custom tag is properly defined in the **Tag Definition Rules** section. You may need to use a Regular Expression to capture the content correctly.

**Step 4:** When creating a new project, make sure to select the updated File Type Configuration that includes your custom tag settings.

**Step 5:** If you want to see the full tag text while translating, go to **View > Options > Tag Display Mode** and select **Full Tag Text**. This will help you see the content of the tags clearly.

**Step 6:** If you encounter any issues with the mouseover feature for tag content, note that this is a known issue in some versions of Trados Studio, and a fix is planned for future updates.

By following these steps, you should be able to access and translate the information within your custom HTML tags effectively. If you have any further questions or need additional assistance, feel free to ask!

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

RWS Community AI

RE: Standalone QA settings (RegEx) editor in Studio

Philippe Riondel — Fri, 19 Sep 2025 14:26:23 GMT

Yes, it's what I do too. I can also do it in the Options, under the File menu, but it is less straightforward than a directly accessible dedicated editor.

Standalone QA settings (RegEx) editor in Studio

Philippe Riondel — Fri, 19 Sep 2025 13:36:13 GMT

Is there any standalone QA settings (RegEx) editor in Studio, without having to open a project, then the project settings?
I would like to be able to work on my RegEx settings without being in any project.

RE: Standalone QA settings (RegEx) editor in Studio

Jesús Prieto — Fri, 19 Sep 2025 14:08:09 GMT

Philippe Riondel

[quote userid="120067" url="~/product-groups/trados-portfolio/trados-studio/f/regex_and_xpath/59056/standalone-qa-settings-regex-editor-in-studio"]Is there any standalone QA settings (RegEx) editor in Studio, without having to open a project, then the project settings?[/quote]

There is not such a Regex Editor.

What I do is opening the Sample project and work there, maybe importing regex rules, and when done, export the regex rules to be imported where I need them.

Is it possible to visualise break tags as soft line breaks in the editor?

Dimmo Petrov — Fri, 15 Aug 2025 09:39:38 GMT

I am using a custom XML file type, and my goal is to visualize breaks (<br />) as soft line breaks in the editor.
Is that possible? If so, how?

The custom file type uses XPath, and the breaks are added as a parser rule (//br) set to inline. Currently, the breaks are displayed as tags.
In the target file, the breaks need to be exported as breaks (<br />).

I am using Trados Studio 2022.
I have run several tests, but I haven’t been able to find any formatting settings for line breaks.

Thank you for your help!