You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems to have done a nice job on the Georgian declarations. It could be worth asking Frederik to sanity check some of the arabic before going all out on arabic-relevant countries. We don't have a lot of merges to compare but the three that have been merged match other transliterations in the entity.
should we promote it from zavod.shed to zavod.helpers.names? or perhaps an explicitly LLM namespace is important in helpers.
to expand to other crawlers, should we just pick any crawlers with names consistently in a non-latin script, prioritising countries where business is done in multiple scripts?
if you still reckon an enricher is ideal, maybe now is the time to try it with a couple of datasets, e.g.
To be used for description text, but also for people names:
(Passing in
context
so that we can usecontext.cache
)See:
https://cloud.google.com/translate/docs/basic/translate-text-basic
It would be cleaner if we made this an enricher that puts the translated statements into a bespoke dataset.
The text was updated successfully, but these errors were encountered: