Quantcast
Channel: ProZ.com Translation Forums
Viewing all 29881 articles
Browse latest View live

Footnotes I'm unable to see the document that I have to translate

$
0
0
Forum: SDL Trados support
Topic: Footnotes I'm unable to see the document that I have to translate
Poster: Danielle Blanchet

Hi,

First I'd like to say hello. It's my first time on the forum. I've a big problem, the document I have to translate have head page and footnotes, when I'm trying to open it in Trados, I only see the head and the foot to translate. If you can help me it would be appreciated.

testing a regex code

$
0
0
Forum: SDL Trados support
Topic: testing a regex code
Poster: Lenart

Hello everybody,

Could someone please explain me, why the code „sa\s*(?!\w* question)“ matches the word „sa“ in a phrase „par sa question“.

the condition of negative look ahead is fulfilled and I would think that the word „sa“ shouldn't match in this case.

Thank you,

L

testing a regex code | regex engine

$
0
0
Forum: SDL Trados support
Topic: testing a regex code
Poster: NeoAtlas
Post title: regex engine

First, the regex engine matches “sa”.

Then the engine tries to match spaces, as many as possible. It matches 1 space and tries with this first (it it failed, it would try with no spaces at all). So trying with 1 space, note the actual position is after the space of “sa ”.

Then the engine processes the negative lookahead. Inside the lookahead it can't match “\w* question” (remember where is actual position) so the engine notes success and captures “sa ” (with the mentioned space). The engine doesn’t try more possibilities (I mean, zero spaces) once notes success (lookarounds work in this way).

Note that if the string were “par sa question question” the lookahead would match “ question” (I mean, the second ”question“), and because it’s a negative lookahead, the same regex wouldn’t match anything.

I hope this helps,

… Jesús Prieto …

testing a regex code | thank you

$
0
0
Forum: SDL Trados support
Topic: testing a regex code
Poster: Lenart
Post title: thank you

thank you Jesús, this was very helpful!

Open Analysis.xml or convert to Analysis.xlsx

$
0
0
Forum: SDL Trados support
Topic: Open Analysis.xml or convert to Analysis.xlsx
Poster: Hans Lenting

How can I read a Studio report in XML format outside of Studio or convert it to an Excel sheet?

Open Analysis.xml or convert to Analysis.xlsx | Inside Excel

$
0
0
Forum: SDL Trados support
Topic: Open Analysis.xml or convert to Analysis.xlsx
Poster: Adrien Esparron
Post title: Inside Excel

[quote]Hans Lenting wrote:

How can I read a Studio report in XML format outside of Studio or convert it to an Excel sheet? [/quote]

Did you try with MS Excel?

Data, External Data, Other sources...

Here a screenshot with the French version :

Hope this helps!

testing a regex code | another related question

$
0
0
Forum: SDL Trados support
Topic: testing a regex code
Poster: Lenart
Post title: another related question

I wrote this code (?negative look behind!EU:)EU:(?!EU:)

I would like a code to identify segments where the word „EU:“ appears only once. However in a following segment „EU:“ appears 3x and the code is still applied. So something is wrong. Can somebody please explain me why the criteria of this code is fulfilled in a following case?

source segment: „(voir, en ce sens, arrêts du 15 mai 2014, Briels e.a., C-521/12, EU:C:2014:330, points 28 et 29 ; du 21 juillet 2016, Orleans e.a., C-387/15 et C-388/15, EU:C:2016:583, point 48, ainsi que du 26 avril 2017, Commission/Allemagne, C-142/16, EU:C:2017:301, points 34 et 71).“

Thank you,

L

[Edited at 2018-07-16 12:41 GMT]

[Edited at 2018-07-16 12:42 GMT]

[Edited at 2018-07-16 12:43 GMT]

Studio 2017 - "move to next segment" not working anymore | Different behaviour of "Control + Down" desperately needed

$
0
0
Forum: SDL Trados support
Topic: Studio 2017 - "move to next segment" not working anymore
Poster: Hans Geluk
Post title: Different behaviour of "Control + Down" desperately needed

I have the same problem and I think that the function "Move to next segment" is wrongly programmed by SDL.

When I review my own (already confirmed) translation in the Editor, I desperately need a way to quickly move to the next segment without confirming anything, especially for long segments. I just want to be moved to the next segment. I hate to have to scroll with my mouse, use "Control + Alt + Enter" (which reconfirms my segment unnecessarily) or click on the scroll bar with my mouse. Hence, I hate reviewing my translations in Trados.

Again: just move me to the next segment. Why would SDL care if the segment is confirmed or not?

Let me know if I'm missing something, if I'm silly or if this can be taken into account for Trados 2019.

Thanks!

[Edited at 2018-07-16 16:52 GMT]

Studio 2017 - "move to next segment" not working anymore | Autohotkey script

$
0
0
Forum: SDL Trados support
Topic: Studio 2017 - "move to next segment" not working anymore
Poster: Nora Diaz
Post title: Autohotkey script

Hi Hans,

I don't think it's realistic to expect for this to be implemented soon, but the good news is that you can use an AutoHotkey script to give you this functionality immediately. I saw your idea post in the SDL Community and added my reply there, but here it is again:

This is the AHK script I use to move to the next segment without confirming or changing anything else:

#IfWinActive ahk_exe SDLTradosStudio.exe
;------------------------------------------------------------------------------
;Go to next segment
;------------------------------------------------------------------------------
PgDn::
Send ^{PgDn}
Send {Down}
Send ^{PgUp}
return

This uses the Page Down key as the hotkey, but you can easily adapt it to use whatever key or key combination you'd like to use.

If you're new to AutoHotkey, all you need to do is:

1. Download AutoHotkey and install it. ( [url removed] )
2. Right click in any folder where you'd like to save the script, select New - AutoHoktey Script, then give this file any name you'd like (such as Move to Next Segment)
3. Open this file with a text editor (I like Notepad++), copy and paste the script above into the body of the file.
4. Save the file
5. Double-click the file to load the script

After doing this, pressing the hotkey, in this case Page Down, will perform the desired action of moving the cursor to the next segment.

Studio 2017 - "move to next segment" not working anymore | Thank you Nora

$
0
0
Forum: SDL Trados support
Topic: Studio 2017 - "move to next segment" not working anymore
Poster: Stepan Konev
Post title: Thank you Nora

for your script.

My AHK is portable, probably this is why there is no Autohotkey Script option in the 'New' menu. If somebody else uses portable AHK, create a new 'Text Document' (txt) file and after pasting Nora's script, change 'txt' to 'ahk'.

However, I suppose going one segment up is as useful as going to next. I am not that smart in AHK as Nora, but I added a 'mirrored' half of the same script to read as follows:

#IfWinActive ahk_exe SDLTradosStudio.exe
;------------------------------------------------------------------------------
;Go to next segment
;------------------------------------------------------------------------------
PgDn::
Send ^{PgDn}
Send {Down}
Send ^{PgUp}
return

#IfWinActive ahk_exe SDLTradosStudio.exe
;------------------------------------------------------------------------------
;Go to previous segment
;------------------------------------------------------------------------------
PgUp::
Send ^{PgUp}
Send {Up}
Send ^{PgDn}
return

Now it works in both directions.
Thank you again.

[Edited at 2018-07-17 03:17 GMT]

Studio 2017 - "move to next segment" not working anymore | CTRL+DOWN/UP shortcuts?

$
0
0
Forum: SDL Trados support
Topic: Studio 2017 - "move to next segment" not working anymore
Poster: NeoAtlas
Post title: CTRL+DOWN/UP shortcuts?

[quote]Hans Geluk wrote:

I have the same problem and I think that the function "Move to next segment" is wrongly programmed by SDL.
[…]
Again: just move me to the next segment. Why would SDL care if the segment is confirmed or not?
Let me know if I'm missing something, if I'm silly or if this can be taken into account for Trados 2019.
[Edited at 2018-07-16 16:52 GMT] [/quote]
May I suggest the default shortcuts CTRL+DOWN and CTRL+UP to move 1 segment up or down? Don't they work for you?

testing a regex code | Your lookahead doens't work…

$
0
0
Forum: SDL Trados support
Topic: testing a regex code
Poster: NeoAtlas
Post title: Your lookahead doens't work…

Your lookahead doesn't work for the same reason that
EU:(?=EU:)
doesn't match
EU:XXXEU:
Lookaheads don't mean “anywhere ahead”, only “just ahead”.

You'd need this regex:
EU:(?=.*?EU:)
to match:
EU:XXXEU:

Same thing about lookbehind.

Once explaind, this regex may work:
(?[minor than sign]!EU:.*?)EU:(?!.*?EU:)
to match “EU:” appearing only once.

You may need to change it, but It's a good starting point.

Please let us know whether it works, otherwise, I'm curious to know your final regex.

… Jesús Prieto …

SDL Trados Studio quotation marks | Problem solved - editor option

$
0
0
Forum: SDL Trados support
Topic: SDL Trados Studio quotation marks
Poster: Luca Pesenti
Post title: Problem solved - editor option

Hi everybody,

Please check your Editor options:

File -> Options -> Editor -> Auto-correct -> Replace straight quotes with Smart Quotes.

P.s. Don't be so hard with developers!!!

Issues with TM, multi-term termbase, and creating return packages in SDL Trados 2017

$
0
0
Forum: SDL Trados support
Topic: Issues with TM, multi-term termbase, and creating return packages in SDL Trados 2017
Poster: Elisabeth Lauffer

Hi all,

I'm new to SDL Trados 2017 and have been struggling a lot with setup and finalizing projects — I'm worried clients might start sending fewer projects if I continue to have such trouble with the software!

The first issue I've found is that setting up projects (receiving the package from the client, opening it in Trados, setting up TM and termbase) doesn't align with the Trados training tutorials, which I've now watched several times. It seems that when I upload the single file for translation, this separates the document from the rest of its corresponding files. When I simply click on the downloaded package (thus opening it in Trados), I find that I do not get the same pop-up screens to walk me through setting up the TM and termbases.

I believe I have correctly set up some TMs, but I get *so* few exact or fuzzy matches (even for things I KNOW I have translated earlier in the project, meaning I have to scroll back to see how I translated it the first time) that I fear I'm doing this wrong, too. As far as the file-based multi-term termbase is concerned, when I try to navigate through the file tree, all I find is empty folders where the client-provided TMs were located.

Finally, once I've gotten through translating the document, saved, and x'ed out of Editor, I have been unable to create return packages — the button is grayed out. I've therefore had to send the .sdlxliff and finalized Word doc or PPT back, which is obviously less than ideal.

Can anyone help? These are rudimentary questions, but these issues are causing me a great amount of anxiety and frustration!

Many, many thanks in advance!

How to filter source=target segments in Trados 2017

$
0
0
Forum: SDL Trados support
Topic: How to filter source=target segments in Trados 2017
Poster: Samuel Murray

Hello everyone

In Trados 2017, I need to find segments where source = target. According to [url= [url removed] ]this post[/url], there is such an option in Trados 2017 but I can't find it. The post says "Use the advanced display filter and then under the 'Filter Attributes' tab use the 'Copied from source' option in the 'Origin' group" but I don't see an advanced display filter. I only have "Display filter", on the Review tab, and there's no advanced under it, and no filter attributes etc.

Any advice appreciated.
Thanks


How to filter source=target segments in Trados 2017 | Right hand side of Editor or View ribbon

$
0
0
Forum: SDL Trados support
Topic: How to filter source=target segments in Trados 2017
Poster: NeoAtlas
Post title: Right hand side of Editor or View ribbon

By default, the advanced display filter is on right hand side of the Editor (it’s one of those auto-hidden windows). If you can’t see it, you may have closed it.
In this case, you can still find the advanced display filter in the View ribbon.

[Edited at 2018-07-18 10:10 GMT]

How to filter source=target segments in Trados 2017 | Thanks, found it

$
0
0
Forum: SDL Trados support
Topic: How to filter source=target segments in Trados 2017
Poster: Samuel Murray
Post title: Thanks, found it

[quote]NeoAtlas wrote:
By default, the advanced display filter is on left hand side of the Editor (it’s one of those auto-hidden windows). If you can’t see it, you may have closed it. In this case, you can still find the advanced display filter in the View ribbon. [/quote]

Thanks. It took a while to find it, but I got it. If I have ever closed that window, it must have been a long, long time ago (I don't think I ever did, though). On my installation, the "tab" for that filter sat on the right-hand side of the Trados window (to the right of the Editor).

It also took me a while to figure out how to to dock it (you have to click-and-hold the pane's title bar, move it a bit, and then wait for some semi-transparent positioning "buttons" to appear, and then you must move your mouse to the button for the position that you're looking for, without releasing the mouse button). I still haven't figured out how to turn it into a tab again -- the tab was there initially (on the side), but then I clicked it and it turned into a pane, and the tab is no longer there, so now I have to use the ribbon to enable it each time.

My ribbon is set to display both icons and commands, but the advanced filter still displays only as an icon. To get to it, go View > Information and click the icon that looks like an open drain. In fact, all the features in the "Information" section of the View tab are just icons, and you have to hover your mouse on them to see what they mean.

==

Anyway, my original question was about filtering source = target, and I still don't know how to do it. Paul's post says to use the "Copied from source" option in the "Origin" section of the filter, but that doesn't get me the results I'm looking for -- it yields segments that [u]used be[/u] source=target but no longer are (and actual existing source=target segments do not appear).

[Edited at 2018-07-18 09:11 GMT]

How to filter source=target segments in Trados 2017 | Right, sorry and an app

$
0
0
Forum: SDL Trados support
Topic: How to filter source=target segments in Trados 2017
Poster: NeoAtlas
Post title: Right, sorry and an app

[quote]Samuel Murray wrote:
On my installation, the "tab" for that filter sat on the right-hand side of the Trados window (to the right of the Editor)[/quote]
Ops!, so sorry, I meant that "right".

[quote]Samuel Murray wrote:
Anyway, my original question was about filtering source = target, and I still don't know how to do it. Paul's post says to use the "Copied from source" option in the "Origin" section of the filter, but that doesn't get me the results I'm looking for -- it yields segments that [u]used be[/u] source=target but no longer are (and actual existing source=target segments do not appear).
[/quote]
Please install the free app Comunity Advanced Display Filter from the AppStore, a much more powerful filter. I have it installed so I keep the Advanced Display Filter always closed. In the Segment tab you’ll find the Source text equals target text option.

I hope it helps,
… Jesús Prieto …

Replace with tab, Trados 2017

$
0
0
Forum: SDL Trados support
Topic: Replace with tab, Trados 2017
Poster: Samuel Murray

G'day everyone

How can I find {{X}} and replace it with a tab, in Trados 2017?

Thanks
Samuel

Problem with field codes when translating Word doc

$
0
0
Forum: SDL Trados support
Topic: Problem with field codes when translating Word doc
Poster: Steven F Smith

I am using SDL Trados Studio 2015 to translate a Word document which contains field codes for intradocument hyperlinks to tables, section headings, etc.

When these field codes appear in the middle of a segment they are shown as vertical bars and I can transfer them to the target segment.

However, when a sentence starts with a field code (e.g. '[Section 1] describes...'), the field code is omitted from the source segment in Studio. It is not even separately segmented, just omitted entirely. I only know it is there by checking the Word document. The field code is retained in the cleaned up file but then needs to be moved to the correct part of the translated sentence.

Are there any solutions for this?

[Edited at 2018-07-19 10:08 GMT]
Viewing all 29881 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>