Is it OK to use the literal characters…

Welcome to the official blog of the translator team for the WordPress open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project. This is where we discuss all things related to translating WordPress. Follow our progress for general updates, status reports, and debates.

We’d love for you to help out!

Translate WordPress

You can help translate WordPress to your language by logging in to the translation platform with your WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ account and suggesting translations (more details).

Want to help in managing and validating translations? Get in touch with the existing language team and follow the glossaries & style guides if the team has them.

Don’t see your language? You can request support for it.

Weekly Meetings

We have meetings every week on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. in polyglots (the schedule is on the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. of this page). You are also welcome to ask questions on the same channel at any time!

Posting here

In order to post to this site, you will need to log in with your wordpress.org account. Your first post may take a while to show up, as it is moderated. Please follow our tag policy when posting.

#polyglots

Zé 3:01 pm on October 13, 2011

I usually tend to go with whatever is in the original, literals and codes, and haven’t had any problems this far.
- Wacław J. 3:05 pm on October 13, 2011
  
  The point is I’d like to use literal characters all the time instead of the codes, not only when there’s a literal in the original. Is that OK? Not only could I then see if the character’s correct right away and generally have less clutter in the translations, they’re also easier to type if you use a compose key (e.g. ComposeKey + , + ” = „).
  - Zé 3:33 pm on October 13, 2011
    
    Unless you verify each occurrence against the source code (which is easy to do right from GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org.), I wouldn’t advise on doing that systematically. There may be instances where the stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. isn’t being escaped, and that might lead to php errors.
    - Wacław J. 3:39 pm on October 13, 2011
      
      Ah, right, obviously, but I mean the curly quotes. 🙂 I’d leave the " quotes as they are.
Nikolay Bachiyski 1:55 pm on October 17, 2011

Yes, it’s perfectly OK to use valid UTF-8 characters anywhere in the translations.

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. tend to use the HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. entity if one exists, which is to make the source-code as little prone to encoding problems as possible.
- Wacław J. 2:39 pm on October 17, 2011
  
  I see. Thanks!

Translate WordPress

Weekly Meetings

Posting here

Share this:

Site resources