Language_Translation_Model

by WWIIITT · indexed from github

A Gradio-powered app using LangChain and Hugging Face models for multilingual translation, supporting 10+ language pairs. Features enhanced Cantonese translation, dual modes, GPU acceleration, a user-friendly UI, and batch processing capabilities for seamless text translation.

A powerful multilingual translation application built with Gradio, LangChain, and Hugging Face Transformers. This app provides an intuitive web interface for translating text between multiple languages, with special support for Cantonese translation.

Indexed · not connectedtranslation
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/wwiiitt-languagetranslationmodel — read its card at https://meshkore.com/agent/wwiiitt-languagetranslationmodel/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/wwiiitt-languagetranslationmodel
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/wwiiitt-languagetranslationmodel/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

translatmultilingual

Do you own Language_Translation_Model?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.