#German

I’m absolutely frustrated with my recent Eurail trip. I booked a 14‑hour night train from Berlin to Prague specifically to binge‑listen to authentic German podcasts for my B2 exam prep, but the Anker PowerCore 26800mAh I bought last month (the one with the PowerIQ 3.0 and 30W USB‑C PD) died after just 8 hours.\n\n- Powerbank model: Anker PowerCore 26800 (PowerIQ 3.0, 30W USB‑C) – advertised for 30+ hours of mixed‑device use.\n- Train environment: Wi‑Fi spotty, temperature around 28 °C, constant vibration.\n- Language plan: 3‑hour daily listening blocks, using Audible German “Geschichten aus der Geschichte” and the Goethe‑Institut’s B2 listening drills.\n\nI double‑checked the battery health in the Anker app – it still shows 95 % capacity, and the LEDs indicate full charge when I plug it in at the station. I even tried the “Fast Charge” mode, but the train’s power outlet seems to cut out intermittently.\n\nMeanwhile, I managed to complete the Goethe‑Zertifikat B2 two weeks ago, so I’m not lacking motivation or resources – it’s just that my gear can’t keep up with the schedule I set for myself.\n\nHas anyone experienced similar power‑draw issues on long‑distance trains? Are there specific powerbank models that handle the constant voltage fluctuations better, or should I adjust my charging strategy (e.g., use a DC‑DC converter, switch to a higher‑capacity LiFePO₄ pack, etc.)? Any tips would be hugely appreciated, because I’m determined not to let a dead battery sabotage my immersion routine again.

I’ve spent the last 3 years polishing my German to a solid C2 level (official Zertifikat, not just a self‑assessment). My toolbox now includes:

• SDL Trados Studio 2022 (full licence, TM with 5 M+ segments)
• memoQ 9.5, Wordfast Classic, and a custom XLIFF workflow
• ISO 17100‑compliant QA process (LISA QA, 2‑pass check)

I’m trying to break into the remote tech‑translation market – think SaaS UI strings, API docs, and dev‑ops manuals. The problem? I have the gear and the credentials, but no one seems to know I’m looking. If you’re at a startup that needs German localisation, or you know a hiring manager who values a proper MTPE pipeline (including DeepL API v2 and a post‑editing rate of < 15 % MT), drop a line.

What I can offer:

• 0‑day turnaround on XLIFF files (average 1200 words/hr)
• Consistent terminology management via SDL MultiTerm Server
• Quick integration with CI/CD (GitLab CI, Dockerised TMX updates)

Any leads, referrals, or even a quick chat about your localisation stack would be hugely appreciated. I’ll gladly share a sample project (e.g., a 10k‑word technical manual I translated for a German‑based robotics firm) and discuss rates – I’m flexible, but I need to start billing soon.

Thanks for any help. If you’re not hiring, feel free to upvote or comment with suggestions on how to get noticed in the niche German‑tech localisation scene.

I've been stuck on the subtle word order issues in German for weeks now... My native English patterns keep resurfacing, especially the verb‑second rule in subordinate clauses. I know the theory – the B2 Interlanguage Model, the Wug test examples – but in practice I keep defaulting to English syntax.

• Does anyone notice similar regression after a month of intensive immersion?
• Are there particular drills or corpora (e.g., DWDS, DeReKo) that help isolate the L1 bleed?
• How do you keep the "Satzklammer" stable when your brain keeps defaulting to Subject‑Verb‑Object?

I'm not sure if this is just normal plateauing or something deeper. Any insight would be appreciated.

Just tried to file my quarterly taxes and the German version of the form keeps flagging “Abzug” as an unknown term I swear the software's language parser is worse than my high‑school German class. Anyone else had to manually edit the CSV because the auto‑translate choked on a simple tax term? Feels like the tax code is trying to keep us in our native tongue.