mirror of https://github.com/koala73/worldmonitor.git synced 2026-04-26 01:24:59 +02:00

Files

Elie Habib 07d0803014 Add WTO trade policy intelligence service with tariffs, flows, and barriers (#364 )

* feat: add WTO trade policy service with 4 RPC endpoints and TradePolicyPanel

Adds a new `trade` RPC domain backed by the WTO API (apiportal.wto.org) for
trade policy intelligence: quantitative restrictions, tariff timeseries,
bilateral trade flows, and SPS/TBT barrier notifications.

New files: 6 protos, generated server/client, 4 server handlers + shared WTO
fetch utility, client service with circuit breakers, TradePolicyPanel (4 tabs),
and full API key infrastructure (Rust keychain, sidecar, runtime config).

Panel registered for FULL and FINANCE variants with data loader integration,
command palette entry, status panel tracking, data freshness monitoring, and
i18n across all 17 locale files.

https://claude.ai/code/session_01HZXyoQp6xK3TX8obDzv6Ye

* chore: update package-lock.json

https://claude.ai/code/session_01HZXyoQp6xK3TX8obDzv6Ye

* fix: move tab click listener to constructor to prevent leak

The delegated click handler was added inside render(), which runs
on every data update (4× per load cycle). Since the listener targets
this.content (a persistent container), each call stacked a duplicate
handler. Moving it to the constructor binds it exactly once.

https://claude.ai/code/session_01HZXyoQp6xK3TX8obDzv6Ye

---------

Co-authored-by: Claude <noreply@anthropic.com>

2026-02-25 10:50:12 +00:00

2.5 KiB

Raw Blame History

News Translation Analysis

Current Architecture

The application fetches news via src/services/rss.ts.

Mechanism: Direct HTTP requests (via proxy) to RSS/Atom XML feeds.
Processing: DOMParser parses XML client-side.
Storage: Items are stored in-memory in App.ts (allNews, newsByCategory).

The Challenge

Legacy RSS feeds are static XML files in their original language. There is no built-in "negotiation" for language. To display French news, we must either:

Fetch French feeds.
Translate English feeds on the fly.

Proposed Solutions

Option 1: Localized Feed Discovery (Recommended for "Major" Support)

Instead of forcing translation, we switch the source based on the selected language.

Implementation:
- In src/config/feeds.ts, change the simple URL string to an object: url: { en: '...', fr: '...' } or separate constant lists FEEDS_EN, FEEDS_FR.
- Pros: Zero latency, native content quality, no API costs.
- Cons: Hard to find equivalent feeds for niche topics (e.g., specific mil-tech blogs) in all languages.
- Strategy: Creating a curated list of international feeds for major categories (World, Politics, Finance) is the most robust & scalable approach.

Option 2: On-Demand Client-Side Translation

Add a "Translate" button to each news card.

Implementation:
- Click triggers a call to a translation API (Google/DeepL/LLM).
- Store result in a local cache (Map).
Pros: Low cost (only used when needed), preserves original context.
Cons: User friction (click to read).

Option 3: Automatic Auto-Translation (Not Recommended)

Translating 500+ headlines on every load.

Cons:
- Cost: Prohibitive for free/low-cost APIs.
- Latency: Massive slowdown on startup.
- Quality: Short headlines often translate poorly without context.

Recommendation

Hybrid Approach:

Primary: Source localized feeds where possible (e.g., Le Monde for FR, Spiegel for DE). This requires a community effort to curate feeds.json for each locale.
Fallback: Keep English feeds for niche tech/intel sources where no alternative exists.
Feature: Add a "Summarize & Translate" button using the existing LLM worker. The prompt to the LLM (currently used for summaries) can be adjusted to "Summarize this in [Current Language]".

Next Steps

Audit src/config/feeds.ts to structure it for multi-language support.
Update rss.ts to select the correct URL based on i18n.language.

2.5 KiB Raw Blame History