News:

BB code in posts seems to be working again!
I haven't turned on every single tag, so please let me know if there are any that are used/needed but not activated.

Main Menu

Teams Meeting

Started by Yacine, July 11, 2024, 08:54:13 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Yacine

Quote from: Nikolay on July 15, 2024, 12:15:33 PMJust wondering if you guys are using telegram?
It could be a group/channel for the announcements.
I have that biased opinion that is something where "righties" and other extremists meet.
But if it has clear advantages over the forum, I would be ready to try it.
On the other hand every update in a thread here is displayed on the top of the recent posts. And we don't target people showing up once a month.
Yacine

Yacine

#16
Quote from: Surrogate on July 15, 2024, 01:52:21 PM
Quote from: Yacine on July 15, 2024, 10:15:31 AMPeople who showed interest are
My spoken English is terrible!
I understand 70% of what is said (the best I understand is the speech of Eastern Europeans).
Almost no one understands what I say)
I can just listen to what is being said.
In times of AI, one might look at live translation? I know for sure that Teams offers a transcript option. So it basically understands what is said. It should technically be possible to send that to a live translator?
LOL, I feel like in an epsiode of Star Trek. The known world is getting smaller and the boundaries further away.
Yacine

wapperdude

#17
QuoteI feel like in an epsiode of Star Trek.

How quaint.
Visio 2019 Pro

Yacine

#18
@surrogate,
(sorry to all the others for riding this horse to death) I consulted my currently preferred AI. Here's the summary of our conversation.

# Live Translation in Microsoft Teams for Multilingual Technical Forums

## Context and Requirements
- Active technical forum looking to start meeting in Microsoft Teams
- Members from various countries, including Russia
- Some members can read and write English well but struggle with listening and speaking
- Need for a cost-effective and simple "live translation" solution in both directions
- Preference to use Teams for its presentation capabilities

## Proposed Solution: Microsoft Teams Integrated Translation

### Key Features
1. Built-in live captioning and translation for meetings
2. Available in many Teams versions
3. No additional software required
4. Individual language settings for each participant

### How It Works
1. Start a Teams meeting
2. Enable live captions
3. Set spoken language and caption language in settings
4. Each participant can choose their preferred translation language

### Activation Steps
1. Join a Teams meeting
2. Click on three dots (...) in meeting controls
3. Select "Turn on live captions"
4. Go to "Live caption settings"
5. Choose "Spoken language" and "Caption language"

### Tips for Effective Use
- Speak clearly and at a moderate pace
- Avoid background noise
- Prepare a glossary for technical terms and share in chat

### Limitations
- Translation quality may vary for highly technical terms
- Not all languages available for translation
- Requires stable internet connection

## Language Dynamics in Multilingual Meetings

### Scenario
- Main presentation language: English
- Russian speakers need translation from English to Russian
- Occasional need for translation from Russian to English for questions/comments
- Potential for other languages (e.g., German) in the mix

### Proposed Workflow
1. Main presentation in English
  - Russian speakers set "Spoken language" to English, "Caption language" to Russian
2. Questions/comments in Russian
  - English speakers switch: "Spoken language" to Russian, "Caption language" to English
3. Use chat for quick translations of short contributions in other languages

### Challenges and Solutions
- Frequent switching between multiple languages (e.g., German, English, Russian) is complex
- Suggestions:
  a) Focus on two main languages (English and Russian)
  b) Set "language blocks" (e.g., 15 minutes English, 5 minutes for Russian questions)
  c) Utilize chat for translations of brief contributions in other languages

## Best Practices
1. Establish clear rules for language switching
2. Inform participants about translation feature usage before the meeting
3. Conduct a brief testing phase at the beginning of each meeting
4. Assign a "technical moderator" to assist with issues

## Alternative for Older Teams Versions
If integrated translation is unavailable:
1. Use Microsoft Translator in a separate window
2. Create a translation room
3. Share the code with participants
4. Each person types in their preferred language, translated for all

## Visual Aid
A flow diagram has been created to illustrate:
1. Main presentation in English with Russian translation
2. Russian contributions with English translation
3. Chat usage for brief multilingual contributions

## Conclusion
While not perfect, this approach offers a structured method for conducting multilingual technical discussions in Microsoft Teams. It balances the need for clear communication with the practical limitations of current translation


Unbenannt.PNG
Yacine

wapperdude

How archaic.  Need a universal translator or a C3P0. 

Universal => takes whatever received language that's presented, converts to a universal machine language and providing a universal database, then outputs in whatever desired receiving language.  Bi-directional.

C3P0 => has exhaustive Multilanguage database with interpretive, learning skills, and can instantly reformulated any incoming communication to desired output.  Also bidirectional.

AI meets StarTrek, StarWars
Visio 2019 Pro

Paul Herber

#20
I think you'd all be better sticking a Babel Fish in your ear!
Electronic and Electrical engineering, business and software stencils for Visio -

https://www.paulherber.co.uk/

Surrogate

#21
Quote from: Yacine on July 15, 2024, 03:20:47 PMBut if it has clear advantages over the forum, I would be ready to try it.
On the other hand every update in a thread here is displayed on the top of the recent posts
About a year ago we compare opportunities of forums and messangers:  Does this forum need its own jabber chat or Telegram channel.
IMHO Forums are best)
PS In 2019 I conducted a webinar about Visio for the Moscow MS office. The webinar was in Russian in MS Teams.
It turned out that they had a corporate analog of YouTube, where my webinar was posted with English subtitles. In some places, the English translation contained many obscene words).

hidden layer

I'm sure that native English (as well as Americans) speaker understand whatever the dialect or accent may be.

Think of taxi driver in UK. Or Indian IT-call-center-experience.
For me as a lousy English speaker it's very difficult to get a clue out of it.

And I guess someone can translate it to plain English if required.

Paul Herber

#23
Quote from: hidden layer on July 16, 2024, 07:58:16 AMI'm sure that native English (as well as Americans) speaker understand whatever the dialect or accent may be

There are jokes that start:
There were 6 men, one from Glasgow, one from Cardiff, one from Somerset, a Geordie, a Scouser, a Lancastrian, and a gentleman from Yorkshire. 7 men!

Ecky thump, eee bah gum, that man.
'an that's we'out the wazzocks an' emmets!
D'ye ken?
Electronic and Electrical engineering, business and software stencils for Visio -

https://www.paulherber.co.uk/

wapperdude

#24
After reading this, I think I understand... Except, who's Ken?   👀. 🤔. There's one or 2 jokes this reply...or more.  😉😄😄😄
Visio 2019 Pro

hidden layer

Quote from: Paul Herber on July 16, 2024, 03:25:50 PMEcky thump, eee bah gum, that man.

but this is intentionally for not-to-be-understood-by-"foreigners", right?
Like my grandchildren who speaks Italian if I shall not understand ;)

wapperdude

A line was cast and tackled a fish, Confused, the intent was scaled back, and the thought released.
Visio 2019 Pro

Yacine

#27
Quote from: Paul Herber on July 16, 2024, 03:25:50 PM
Quote from: hidden layer on July 16, 2024, 07:58:16 AMI'm sure that native English (as well as Americans) speaker understand whatever the dialect or accent may be

There are jokes that start:
There were 6 men, one from Glasgow, one from Cardiff, one from Somerset, a Geordie, a Scouser, a Lancastrian, and a gentleman from Yorkshire. 7 men!
Ecky thump, eee bah gum, that man.
'an that's we'out the wazzocks an' emmets!
D'ye ken?

Sorry guys, I just can't stop cheating. At least I managed to get a right AI-prompt:

Ey up, duck! You're not wrong there. Whether you're a Geordie, Scouser, or a posh Southern softie, we all speak the King's English, don't we? And yo, my American homies, we feel ya too!
Listen up, Visio-heads! We're all on the same flowchart here, ya dig? Politics, worldviews, and disasters got nothin' on our shared passion for shapes and connectors. We're like one big happy family tree diagram!
Real talk, fam: We're just tryna level up this God-tier tool. Visio's our jam, and we're here to make it pop like a perfectly aligned auto-connect!
So, let's keep it 100 and stay cool as a SmartShape. At the end of the day, it's all gucci in our Visio hood. Peace out, and may your connectors always snap!


... and back to myself.
I don't know if we really need such an in depth understanding in our daily workflows and processes. They remain astonishing anyway.
Most of our communication is performed with simplified English. That's fine. Why would the remaining world need to know the subtleties of dialects anyway.
We're working with a lingua franca that happens to be English. It could all the same have been Esperanto or Interlingua, or worse ;).


At the end of the day:
- No one should be afraid of insufficient English knowledge. We'll judge you on your Visio knowledge only, not English.
- just kidding. Every honest newbie is welcome. (As long as he/she swears that there is no shapesheet, but the shapesheet ;) )
Yacine

Browser ID: smf (possibly_robot)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 4: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 394 (show)
Files included: 32 - 1207KB. (show)
Memory used: 1295KB.
Tokens: post-login.
Cache hits: 14: 0.00158s for 26,767 bytes (show)
Cache misses: 3: (show)
Queries used: 16.

[Show Queries]