Login

Recent searches

No recent searches

Search options

Not available on wake.st.
wake.st is one of the many independent Mastodon servers you can use to participate in the fediverse.
the personal instance of Liaizon Wakest

Administered by:

Server stats:

1
active users

wake.st: AboutPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.6

#internationalization

0 posts0 participants0 posts today
Public
China Business Forum

The 2024 #China #Huangshan #Book #Fair commenced on November 15 in #Hefei, #Anhui Province, showcasing a dynamic integration of thematic development, #internationalization, #digitalization, and #lifestyle integration. This year’s fair features an array of #cultural activities, including #exhibitions, book sales, #industry #forums, #reading initiatives, cultural #livestreams, and interactive #digital experiences. cnbusinessforum.com/2024-china

China Business Forum · 2024 China Huangshan Book Fair: A Blend of Culture, Innovation, andExperience culture, innovation, and global exchange at the 2024 Huangshan Book Fair, featuring 300,000 books, international publishers, and cutting-edge digital experiences.
Public
UNDLTD

I think I'm generally satisfied with how I operate computers. It feels similar to playing a musical instrument: there is this satisfying feeling of being able to achieve things "through" the instrument without thinking *about* the instrument.

But there is one pain point I have regardless of which DE or even OS I use, and I don't yet know how to solve it:

Switching keyboard layouts.

I type a lot in Ukrainian. But I also type a lot in English or run commands or use programs that don't understand keyboard shortcuts when the layout isn't English / Latin script.

(I actually use Programmer's Dvorak for English, but that's a different story that just makes the layouts even more apart from each other than otherwise - because of the number row and punctuation differs).

And I'm pretty strongly a keyboard-oriented user. I do most of stuff using the keyboard.

But I often find myself using the wrong layout to type something or to send commands / shortcuts. Again and again.

(That gets even more complicated when running virtual machines - imagine having to think about nested combinations of keyboard layouts... Agh.)

It just *feels wrong* to have to be switching layouts back and forth *at all*. To have to manage *state* in your head about which layout you are in, all the time.

I envy those users who manage to live mostly with a single keyboard layout.

I am actually thinking about the possibility of using some kind of "out-of-band" input channel to "dictate" the layout I want at all times. For each single keystroke.

Something like the pedal on the piano.

That would be so awesome...

#UX#Internationalization#Accessibility
Public *
lil5 :golang: 🌱 :react:

Crowdin uses git wrong
crowdin.com/

With the crowdin github integration it first downloads the entire repository _every commit_ then syncs the translations with what it has.

Is #codeberg translate better in this department?

#crowdin #localization #management #platform #collaborative #internationalization #translation tool

CrowdinCrowdin | Localization Management Platform for agile teamsCrowdin's localization management platform is a technology solution for your team.
Public *
treefit

Question for people with experience in other languages that have their own scripts (non ascii latin scripts):

Is it common for websites to use non-ascii/unicode/punycode for their domains?

Please comment with examples and which language/script it is.

· 7 people · Closed
#unicode#localisation#domains
Public
Tirifto :korektu_min:

So apparently server administrators on the #Fediverse won’t be able to name custom emoji in their native languages and expect them to work in Mastodon, because according to @Gargron non-ASCII signs are hard to input and diacritics shouldn’t change the meaning of words:

https://github.com/mastodon/mastodon/pull/28572#issuecomment-1878952504

No, in my view emoji identifiers shouldn’t be ‘straightforward to input for everyone’. Custom emoji are local to a server; they should be straightforward to input for the users of that server. People from other servers don’t ever have to type their names (unless their administrators choose to add them to their own server), so their ability to type them is completely irrelevant.

Why should a server made specifically for people speaking Russian or Japanese have to use ASCII for their emoji identifiers? Their users have no trouble typing Cyrillic or Kanji signs; it’s what they already do when they make a post; it’s how they normally talk. Why force them to use a different language/alphabet when typing emoji identifiers?

Moreover, linking the username issue makes no sense whatsoever. Usernames are typed across servers and it makes sense to impose stricter technical limitations so more people can read, write and recognise them. This is not the case for emoji; you rarely ever need to type other servers’ emoji identifiers. Normally you don’t even get to see them; you only get to see the picture they represent! Assuming server admins do their job responsibly, there is zero added confusion for anyone involved.

I understand that Unicode is complex, language support is challenging and compromises might be necessary at times. But can we please accept the existence of different languages and writing systems as a reality that we should try to accommodate for, rather than change or circumvent? Yes, a and á are different signs. Yes, they might radically change the meaning of a word. That’s not a proposition for us to accept or reject; that’s the reality of our multilingual world, and should be the basis of our discussion.

jam.xwx.moeMansardo Jamada
#lang_en#accessibility#a11y
Public
Ben Myers 🦖

📝 New post! “Lost in Translation: Tips for Multilingual Web Accessibility”

Does your site's accessibility hold up across languages?

I wrote about the practical tips I wish I'd had for making sure that accessibility efforts and internationalization/localization efforts alike don't leave out disabled speakers of other languages than our own.

benmyers.dev/blog/multilingual
#accessibility #internationalization #a11y #i18n

Ben Myers · Lost in Translation: Tips for Multilingual Web AccessibilityPractical tips I wish I'd had for navigating the intersection between web accessibility and internationalization/localization.
Public
W3C Developers

In an evolving world, @w3c faces challenges such as the impact of #AI deployment and misinformation. Addressing these while preserving the openness of the Web require documenting the foundational principles of W3C, rooted in #interoperability, #accessibility, #internationalization and #privacy The "Vision for W3C" document is presented by w3c.social/@tzviya #w3cTPAC
▶️ w3.org/TR/w3c-vision/
▶️ w3.org/2023/09/TPAC/ac-vision (🎬 w/ slides and transcript)

On #YT: youtu.be/uDEsXozzxik

Snapshot of the recorded talk of Tzviya Siegman where she goes over the slide (#2) "What is the Vision", at W3C TPAC 2023
SearchLive feeds
About