Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

notify.gov homepage future content update - character sets & languages partners use #2159

Open
dmvancura opened this issue Nov 26, 2024 · 1 comment
Assignees
Labels

Comments

@dmvancura
Copy link

dmvancura commented Nov 26, 2024

explore adding copy about the languages partners have sent messages in via notify.gov

google doc comments for reference:
Elizabeth Ayer - Q2AAFDA, 11:25 AM Nov 18 - ultimately would be nice if this were a link to supported languages

Deana VanCura - QQ-C, 1:16 PM Nov 18 - is there an exhaustive list of languages supported by Notify.gov and this could be a good one for Phase 2, as for this Phase 1, we're not linking to any new content from the homepage

Cathy Beil - Q2AAFD, 1:28 PM Nov 18 - Notify supports character sets, not specific languages. And the number of languages a character set is used for can change! (I read about an indigenous language recently 'picking' a character set to use for written comms.) So, I don't know that we'll ever have an exhaustive list of languages, but a list of supported character sets might make sense.

Deana VanCura - QQ-C, 2:00 PM Nov 18 - i wasn't sure, so i'm happy i asked. and this could be food for brainstorming thoughts: 1. providing a full set of characters sets or the most commonly used by partners so far 2. list of languages that have been sent by partners.

Deana VanCura - QQ-C, 3:23 PM Nov 18 - hi again, i did some overthinking, fact finding, and talked to cliff... notify.gov supports more than 30 character sets, but it has a single character set/encoding with UTF-8. that means I wouldn't suggest we show 30 characters sets. but we could consider something like what i'm added here at the beginning of the sentence (and then disregard my comment from 2pmET)

Steven Reilly - Q2AAFDA, 4:10 PM Nov 18 - I worry a bit that this is too technical for normal people, but not technical enough to appease techies. It's hard to strike that balance in a sentence!
Would it work to say something like:

  • Send messages in your recipient's preferred language
    and/or
  • Notify has delivered messages in __ languages

Steven Reilly - Q2AAFDA, 4:12 PM Nov 18 - And even though we don't support languages, potential partners might still like seeing a list of languages that other partners have used. We'd just want to say "including" to not imply that it's limited to those

Elizabeth Ayer - Q2AAFDA, 5:38 PM Nov 18 - Oh yeah, I'd also advocate keeping our wording around languages rather than character sets, at least for now.

Elizabeth Ayer - Q2AAFDA, 5:39 PM Nov 18 - And this really was just a note for the future because the topic deserves a page; I didn't think anything should change now!

Deana VanCura - QQ-C, 5:16 PM Yesterday - hi! making sure this is carried into future conversations. marking as a ticket in github, tagging and closing this comment

google doc for reference https://docs.google.com/document/d/1fn3eHUjyJJcdZUnpqhp_q_sUddRZBK4pbs0SA-Zl7rU/edit?usp=sharing

@dmvancura dmvancura moved this to 🔜 Backlog in Notify.gov product board Nov 26, 2024
@dmvancura dmvancura changed the title about notify content in phase 2 - character sets & languages partners use notify.gov homepage content in phase 2 - character sets & languages partners use Nov 26, 2024
@dmvancura dmvancura changed the title notify.gov homepage content in phase 2 - character sets & languages partners use notify.gov homepage future content update - character sets & languages partners use Dec 5, 2024
@dmvancura
Copy link
Author

title is now more accurate based on originating conversation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 🔜 Backlog (Less than 3 Months)
Development

No branches or pull requests

4 participants