Machine translation often does a better job with paragraphs because the
words are in context. Single word labels such as "Logging" are what gets it
confused because it can't always figure out if that's about log files or
felling trees.

Op di 10 aug. 2021 om 15:27 schreef Dave <hastings.recurs...@gmail.com>:

> Gotcha, I don’t know Russian so I didn’t know that. the admin ui has very
> limited English to translate there aren’t paragraphs, unless you want the
> results translated, otherwise it’s pretty straight forward I would have
> thought
>
> > On Aug 10, 2021, at 9:19 AM, Stephen Boesch <java...@gmail.com> wrote:
> >
> > automated translations are rough at best
> >
> >> On Tue, 10 Aug 2021 at 06:16, Dave <hastings.recurs...@gmail.com>
> wrote:
> >>
> >> Cant chrome translate the page or is there too much JavaScript?
> >>
> >>> On Aug 10, 2021, at 8:44 AM, Eric Pugh <
> ep...@opensourceconnections.com>
> >> wrote:
> >>>
> >>> Nothing built in today.   The Solr GUI is written in AngularJS, and
> >> while it references support for i18n, no one has taken that step.
> >>
> https://docs.angularjs.org/guide/i18n#how-does-angularjs-support-i18n-l10n-
> >>>
> >>> This type of feature is why we’d love to see someone step up and move
> >> the GUI to more modern platform that more easily supports this kind of
> >> feature.
> >>>
> >>>> On Aug 10, 2021, at 6:36 AM, Егор Иванов <egorvlz...@gmail.com>
> wrote:
> >>>>
> >>>> Hello, my name is Egor
> >>>> Is there any way to translate Solr's GUI to russian?
> >>>> Looking forward to hearing from you
> >>>
> >>> _______________________
> >>> Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467
> |
> >> http://www.opensourceconnections.com <
> >> http://www.opensourceconnections.com/> | My Free/Busy <
> >> http://tinyurl.com/eric-cal>
> >>> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
> >>
> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw
> >
> >>
> >>> This e-mail and all contents, including attachments, is considered to
> be
> >> Company Confidential unless explicitly stated otherwise, regardless of
> >> whether attachments are marked as such.
> >>>
> >>
>

Reply via email to