4e1213fbd1
Two adjacent i18n leaks in /tools/fristenrechner "Was kommt nach…" mode,
same pattern as t-paliad-112's deadline_rules fix but on event_deadlines:
A) title_de empty for all 70 rows. The DTO already falls back to title
silently, so DE locale rendered English titles ("Statement of Defence",
"Decision of the EPO", …). Backfilled via mig 035 with UPC RoP DE
terminology that matches the trigger_events.name_de translations from
mig 033, so the picker label and the deadline row read the same.
B) notes column carries English text on rows 50, 52, 70 (DE-named column
was DE-only in spec, but seeds slipped EN strings through). Mig 036
adds a parallel notes_en column following the t-112 mig 032 pattern,
copies the existing English into notes_en, and replaces notes with
proper DE for those three rows.
Render path:
- service: select notes_en, plumb through EventDeadlineResult.NotesEN
- frontend: getLang() === "en" ? (notesEN || notes) : notes (mirrors the
proceeding-tree timeline branch already in fristenrechner.ts)
14 lines
570 B
SQL
14 lines
570 B
SQL
-- Reverses 036_event_deadlines_notes_en. Restores the original English
|
|
-- notes for rows 50/52/70 from notes_en, then drops the column.
|
|
|
|
UPDATE paliad.event_deadlines SET notes = CASE id
|
|
WHEN 50 THEN 'Or 20 Working days, whichever is longer'
|
|
WHEN 52 THEN 'Or 20 Working days, whichever is longer'
|
|
WHEN 70 THEN 'The 262.2 application can also be filed for opponent submissions to protect confidential information disclosed by the opponent.'
|
|
ELSE notes
|
|
END
|
|
WHERE id IN (50, 52, 70);
|
|
|
|
ALTER TABLE paliad.event_deadlines
|
|
DROP COLUMN IF EXISTS notes_en;
|