WordPress.org

Ready to get started?Download WordPress

Translate WordPress

Tagged: suggestion Toggle Comment Threads | Keyboard Shortcuts

  • Charles Frees-Melvin 11:13 pm on October 2, 2013 Permalink | Log in to leave a Comment
    thee17 • en-ca.wordpress.org editor
    Tags: suggestion   

    It would be great if we could edit the readme.html from within rosetta possibly with a short code that auto inserts the version and the wp-config-sample.php from strings in GlotPress and have the compiler script automatically pull them and make those files. It would allow more rapid push out of new releases/updates without the need for tagging the new version in SVN. In theory, if the version number gets auto filled in the readme.html with this method, it would also allow the core admins to push all the translations too for a security release if there are no changed strings.

     
    • Andrew Nacin 5:34 am on October 3, 2013 Permalink | Log in to Reply

      Definitely something we’ve talked about before. There are a number of potential issues. A lot of installs have their own readme.html file, with the actual filename translated as well. Thus it would ship next to the American English readme.html. We could encourage this for all languages, but then we’d have a conflict for non-American English translations. Or we could discourage this, thus readme.html would always reflect the local language. But when you start dealing with updates, versus just a standard download package, things get a bit messy.

      When using an American English install, WordPress currently downloads only changed files when updating to a minor release. Since we know which files changed and we know that no strings changed, it’s entirely fine to do so. We’re nearing the point of “language packs” that would update po and mo files separately. Unfortunately, this readme.html file remains a thorn, especially with the version number. It’s not a big deal if the translated readme says “3.5” but the actual install is 3.5.1. But, if a translator is simply replacing readme.html, then we’re going to stomp on their changes. Now, I don’t necessarily mind this as users aren’t relying on their readme once they are installed (or at all — it’s a bit of an anachronism). It’s also no different from when a user opts to update to WordPress in English before a zip is ready.

      Oh, and some include a translation of the license file, too.

      I think we’re at the point where, at the very least, Rosetta can replace a placeholder for you inside readme.html. Then you could just always take the trunk or branch dist files which will have nothing more than a readme.html and wp-config-sample.php. Over time I’m very happy to see newer tools here.

  • Diana 2:01 am on August 2, 2013 Permalink | Log in to leave a Comment
    Dianakc • br.wordpress.org validator
    Tags: , suggestion   

    Hello, I just thought that Translate extension can help on Codex i18n. This extension provide an Glotpress-like interface to translate stable docs. This page is an example, the top link Translate this page lead to the translation interface. Though languages must be added prior to users submit translations, just like the wiki concept there is no need to approve every translations by default, that is, the translation works like editing a wiki article.

    Not sure if someone noticed but the KDE project and Translatewiki.net use this extension :)

     
  • Mattias Tengblad 2:14 am on May 19, 2013 Permalink | Log in to leave a Comment
    DaMsT • sv.wordpress.org editor
    Tags: suggestion, time format,   

    When you edit the time format on the settings screen, it may be difficult to see which format is which (at least for the non php date savvy), especially given that the current time is used to display the examples. If you change the format in the morning Swedish time it would look like this:

    01:34 = [h:i]
    1:34 = [g:i A]
    01:34 = [H:i]

    Perhaps we should add information to the different formats to clarify what’s what?

    Something like:

    01:34 = [h:i] (12h format)
    1:34 = [g:i A] (12h format)
    01:34 = [H:i] (24h format)

    Your thoughts?

     
    • Ze Fontainhas 4:59 pm on May 22, 2013 Permalink | Log in to Reply

      Makes perfect sense to me. It would also make sense to not use the current time as an example, but rather a fixed time string which always illustrates the differences, as in 01:34, 1:34pm, 13:34, and so on.

  • akerbeltzalba 11:43 am on April 18, 2013 Permalink | Log in to leave a Comment
    akerbeltzalba
    Tags: , suggestion   

    Out translations have just come out on Android :) Thanks!
    A couple of observations/suggestions, if I may:

    • the only way to make it show up in languages which are not the system language of Android is to use an additional app to create a “fake locale”. Given that WP supports way more languages than Android does, I really think it’s time for a manual language selection option in the Settings. Most “normal” users won’t know about force-locale – or even what a locale is – and so won’t know how to look for a fix. I know space in settings is always at a premium but this – from an l10n perspective – is really a vital usability issue. This is especially true on non-Android systems. There is no app on Windows Phone or iPhone that even allows me to fake a locale, so even if I translated the UI for iPhone, no-one could access it because you cannot select the UI language manually.
    • somewhat related, it seems to pull some data (the dates) from the OS too, so because the OS in my case is English, the stats page shows localized UI but the dates in English. Perhaps these could be added to the po so the UI is consistent?

    Other than that I’m very pleased :)

     
  • Wacław Jacek 9:28 pm on March 20, 2013 Permalink | Log in to leave a Comment
    waclawjacek • pl.wordpress.org editor
    Tags: licensing, suggestion   

    It’s not very clear what licence the translations fall under, judging from the PO file headers generated by GlotPress. It’s also not clear what the project is, though the PO files probably aren’t published anywhere aside from the translation packages. Another thing is that there should be a notice saying “by submitting your translations you agree that you’re licensing them under the GNU GPL” or a checkbox that you mark upon registration, so that the translations are actually licenced to be distributed with WordPress.

     
  • MONDOHA Maoulida 12:08 am on January 1, 2013 Permalink | Log in to leave a Comment
    mondoha13
    Tags: active, , , not suggested, suggestion   

    Hi
    I’d like to know how to translate a project in a language that is not suggest .
      In fact I want to translate BuddyPress in Swahili and Shi komori but these 2 languages ​​are not suggest.
    How to activate these languages. thank you

     
    • Ze Fontainhas 2:19 pm on January 4, 2013 Permalink | Log in to Reply

      I’ve added Swahili to BuddyPress on Translate WordPress (it’s probably a good idea to try to get in touch with the team ah http://sw.wordpress.org, which seems to be dormant, too).

      Shikomor is a whole other question however. Wikipedia lists 4 codes for the 4 variants, as there seems to be no general, meta-code for simply Shikomor, i.e. zdj – Ngazidja dialect, wni – Ndzwani (Anjouani) dialect, swb – Maore Comorian, wlc – Mwali dialect.

      In order to add support for it, we’ll need to know which variant we’re talking about.

  • Ulrich 3:10 pm on September 27, 2012 Permalink | Log in to leave a Comment
    grapplerulrich
    Tags: suggestion   

    Is there any plans to translate numbers? WordPress at the moment only supports Latin numbers.

     
  • Diana 2:00 am on May 25, 2012 Permalink | Log in to leave a Comment
    Dianakc • br.wordpress.org validator
    Tags: , suggestion   

    In Menu creation panel, I suggest “Menu Areas” instead of “Theme Locations”, quite more self-explanatory.

     
    • Andrew Nacin 10:20 pm on May 30, 2012 Permalink | Log in to Reply

      It’s been like this since version 3.0. Ideally we do a second pass on menus and make the whole experience a bit better. Perhaps create a Trac ticket if you feel strongly about the renaming.

  • talipprofile 5:38 am on December 18, 2011 Permalink | Log in to leave a Comment
    talipprofile • az-tr.wordpress.org editor
    Tags: , suggestion, tr_AZ   

    Hi again Mr. Zé .
    Thanks. I’ve read all the information on the “draft handbook” post and everything is clear to me now. And I’m ready and up for it to get started.

    1-WordPress.org username of the administrator: your username
    “talipprofile”
    2-Language code: fr
    “tr”
    3-Language name, both the English and the native name: French, Français (note that in this case ‘Belgium French, Français de Belgique’ would be acceptable too)
    “Turkish” and “Türkcə” or “Azerbaijan Turkish” and “Azərbaycan Türkcəsi”
    4-(if applicable) Country code: be
    “az”
    5-(if applicable) Country name, both the English and the native name: Belgium, Belgique
    “Azerbaijan” and “Azərbaycan”

    And, I have a group of Azerbaijanian friends and linguistics professors at my university who I requested to cooperate on other cms translation projects before.
    So, what’s the next stop to start the process with having “http://i18n.svn.wordpress.org/tr_AZ/”, “http://tr-az.wordpress.org” “http://tr-az.support.wordpress.org” and so on?

    Kind regards.

     
    • 3:11 pm on December 18, 2011 Permalink | Log in to Reply

      Does Turkish Azerbaijani have a direct relation to South Azerbaijani (azb), or is it a subdivision of it (as in Turkey and Iran)? See also the entry for North Azerbaijani (azj).

    • Talip 7:20 am on December 19, 2011 Permalink | Log in to Reply

      No. Turkish language has no relation with Iran (www.tdk.gov.tr/lehceler). And, the term of “South Azerbaijani” and “Yeraz/Yerevan Azerbaijani” bornt after the subdivision of Azerbaijan’s lands.

      In the region, Turkish Language Association (http://en.wikipedia.org/wiki/Turkish_Language_Association) is a more reliable source about the Turkish language family. Azerbaijani Turkish is a dialect which is used in many cities of Turkey too. Especially in Igdir City (I’ve been in there), Kars City, Istanbul and in the highlands of Turkey’s east and north. (ethnologue.com tells only about Kars City) . Republic of Azerbaijan and Nakhchivan Autonomous Republic uses Azerbaijani Turkish officially.

      And as I lived in the highlands of Trabzon (it’s so far from Azerbaijan), it took only few weeks me to get used to life in Azerbaijan.

      ( Else, http://www.trt.net.tr/trtavaz/ is an international broadcaster of Turkish dialects. )

      • Talip 7:35 am on December 19, 2011 Permalink | Log in to Reply

        Turkey uses “Istanbul Agzi” (Istanbul dialect of Turkish) and Istanbul’s mean time (GMT +2) for convenience. Otherwise, Turkey have no difference with Azerbaijan literally.

      • 10:00 am on December 19, 2011 Permalink | Log in to Reply

        Ready: rosetta site, svn (and perms), GlotPress projects.

        • Talip 5:21 pm on December 19, 2011 Permalink | Log in to Reply

          Okey. But I think there’s one mistake. You adjusted it as “az-tr.wordpress.org” but, language code is “tr” and country code is “az” . You placed it reverse. I guess it must be like that, “tr-az”.wordpress.org http://i18n.svn.wordpress.org/“tr_AZ”/ . I don’t know if it’s so important or not. Maybe it’s just nominal but i’m quite perfectionist . ( ;

          Thanks. Good luck.

          • 5:52 pm on December 19, 2011 Permalink | Log in to Reply

            I’m confused now. “az-tr” indicates “Azerbaijani, as spoken in Turkey”. Were you requesting the opposite (i.e. “Turkish, as spoken in Azerbaijan”)?

    • Talip 6:37 pm on December 19, 2011 Permalink | Log in to Reply

      Yes. For sure. Turkish language spoken in Azerbaijan as it’s written in the headline of the rosetta site as “Azərbaycan Türkcəsi” = “Azerbaijani Turkish” . I think I sent all the details clearly in my first post:

      1-WordPress.org username of the administrator:
      “talipprofile”
      2-Language code:
      “tr”
      3-Language name, both the English and the native name:
      “Turkish” and “Türkcə” or “Azerbaijani Turkish” and “Azərbaycan Türkcəsi”
      4-(if applicable) Country code: be
      “az”
      5-(if applicable) Country name, both the English and the native name:
      “Azerbaijan” and “Azərbaycan”

      I guess you were confused because I wrote with long paragraphs.. )

      • Talip 6:46 pm on December 19, 2011 Permalink | Log in to Reply

        And I’m organizing a meeting with the translation team. At Qafqaz University, we’ll coordinate the translation process with a students’ social club. As I read in the rules at handbook, it’s not allowed to use “WordPress” name in a domain. Could we establish a students’ social club at our university named like “WordPress Translators” ? Any problem with this? Because I think in this way I can attract more students as translators in Baku.

      • 7:32 pm on December 19, 2011 Permalink | Log in to Reply

        My confusion stems from the fact that Turkish is not listed as a language spoken in Azerbaijan.

        • Talip 10:17 pm on December 19, 2011 Permalink | Log in to Reply

          Oh I see. I get the point now. Everything is okey then ) . Sorry for taking your time. Wish me well about coordinating my translation team. ; )

  • Wacław Jacek 11:31 am on October 6, 2011 Permalink | Log in to leave a Comment
    waclawjacek • pl.wordpress.org editor
    Tags: , suggestion,   

    The Polish translation contains a pl_PL.php file, which comprises a function that does month name declension. It seems such .php files aren’t used on WordPress.com, which seems reasonable from a security standpoint, but it results in month names being improperly displayed on Polish WordPress.com blogs. Is it possible to implement a system that would allow such functions after, e.g., reviewal from a WordPress.com staffer? You can see the entire file here: http://i18n.svn.wordpress.org/pl_PL/tags/3.2.1/dist/wp-content/languages/pl_PL.php.

    P.S.: A “com” tag would be nice. :)

     
  • Wacław Jacek 11:20 am on July 25, 2011 Permalink | Log in to leave a Comment
    waclawjacek • pl.wordpress.org editor
    Tags: , suggestion   

    Since this blog serves as both a place for announcements and discussion, it’s quite hard to filter out the /really/ important messages, such as new version notifications. Because of that, I have an idea – maybe a new blog could be created, e.g. wppolyglots-announcements (though that is a really long name), on which only important announcements from the core developer team would be posted?

     
    • Mattias Tengblad 11:37 am on July 25, 2011 Permalink | Log in to Reply

      Please no. Not yet another blog. Let’s just put the resources on creating a proper translation team portal @ wp.org with bbPress and/or BuddyPress.

      • Wacław J. 2:25 pm on July 25, 2011 Permalink | Log in to Reply

        It doesn’t have to be a blog, it could be anything that could be easily distinguished from other WP Polyglots messages as important (particularly by automated e-mail filters :)).

        • Wacław J. 2:28 pm on July 25, 2011 Permalink | Log in to Reply

          Sorry for doubleposting. Another way to do it would require announcement posters to tag their messages with “announcement”, then we could use this: http://wppolyglots.wordpress.com/tag/announcement/feed/ (But since this requires doing this by hand, it’s probably not the best idea. Maybe change the blog a bit so this is done automatically?)

          • Andrew Nacin 4:48 pm on July 25, 2011 Permalink | Log in to Reply

            I’ve nearly used the announcement tag. Next time I need it, I’ll add it to the tag policy and implement it on previous announcements.

            We can also make these more prominent soon.

          • Mattias Tengblad 5:06 pm on July 25, 2011 Permalink | Log in to Reply

            I like the concept of having a channel specific for announcements.We probably need one for requests too. This does on the other hand make things very cluttered here (as per your point) but to scatter it over even more sites is not good.

            Like I’ve suggested a bunch of times, we should be hosted at wp.org, we should be able to have a platform a bit more suitable (bbPress/BuddyPress) for communication rather than a blog for the whole translation community of WordPress. I don’t quite get why these kind of suggestions are constantly ignored.

            Get me right, P2 is a nice platform, but not for this many people and this kind of flow of posts.

  • Rafa Poveda 3:14 pm on July 15, 2011 Permalink | Log in to leave a Comment
    bi0xid • es.wordpress.org editor
    Tags: suggestion   

    Hello there.

    Zé gave me the idea and I have been thinking in have a localized P2 to the translation community in Spanish. I have tried to create it with the most logical name, but i had this message:

    The address es_es.wordpress.com is reserved and cannot be registered.

    Do you think it will be a good idea to ask for this locale references to work with translation communities? I mean:

    • en_US.wordpress.com
    • es_ES.wordpress.com
    • pt_BR.wordpress.com
    • and so on…
     
    • 3:47 pm on July 15, 2011 Permalink | Log in to Reply

      That message is wrong, actually. It should be “Only lowercase letters and numbers allowed”, as on first signup (I’ll relay it to the devs). I’m no apologist of standardizing such blog names on .com for the obvious reasons that the names might already exist and .com doesn’t allow recycling/reassigning them.

      I’m also not sure if it’s necessary to have the blog live on .com. Our own (pt_PT) is a network site of the main site, self-installed. That said, everyone is free to do it, of course. Just choose your own name. Whichever solution is centrally implemented (if it is at all) in the future is safe, with the export/import tools, anyway.

      What we could debate with @nacin is the possibility of having the option to have a p2 dependent on the main xx.wordpress.org install. Maybe.

      Other opinions?

    • 3:49 pm on July 15, 2011 Permalink | Log in to Reply

      Also, the concept of en_US made me smile :)

    • Mark Thomas Gazel 6:35 pm on July 15, 2011 Permalink | Log in to Reply

      I like the idea. I am working on something P2 driven on the danish site which I would simply call a teamblog. Wouldn’t team-locale e.g. team-da_DK.wordpress.org or team-pt_BR.wordpress.org work?

      But I’m still a little hesitant towards using P2 for the team. As have been noticed in this P2-blog here, there are some disadvantages. Threads get lost or forgotten quickly and don’t get brought up to front when they get new comments.

      So I’m also thinking about bbPress and making a Team Forum instead. Especially when bbPress as a plugin merges better with the websites theme. It will get mixed up in the rest of the (support)forums and won’t be a small closed group (or feel like it), but as Zé has pointed out you will be able to mark threads as [Resolved] and you can revive old threads and such.

      There is pro and cons for both scenarios. P2 is great for quick, shortlived, in the moment communication while bbPress is better for longer in debt discussions and have some tools for working with threads and topics.

      • 6:46 pm on July 15, 2011 Permalink | Log in to Reply

        team-da_DK.wordpress.org seems awfully convoluted… maybe da_DK.wordpress.org/team?

        If I’m reading your comment correctly, you’d advocate both a P2 *and* a forum? As in a forum separate from the main locale forum? Not sure I like the idea.

        As to

        you will be able to mark threads as [Resolved]

        don’t underestimate @nacin‘s skills of beating a P2 into submission. Enough said ;)

        • Mark Thomas Gazel 7:48 pm on July 15, 2011 Permalink | Log in to Reply

          No, I meant that both P2 and a forum had advantages, but I wouldn’t use both at the same time. Just that it’s hard to decide which would work best.

          Actually you only need the da-prefix as in da.wordpress.org :-)

          I’m sure @nacin is very focused at making P2 suit our needs.

      • Rafael Poveda - RaveN 6:47 pm on July 15, 2011 Permalink | Log in to Reply

        I think sticky posts can easily resolve this problem :)

    • Rafael Poveda - RaveN 8:25 pm on July 15, 2011 Permalink | Log in to Reply

      O_o my e-mail comments notifications are now in… any other language I don’t know?

      Du kan se alle kommentarer til dette indlæg her:

    • Mattias Tengblad 11:03 pm on July 15, 2011 Permalink | Log in to Reply

      Isn’t this making things even more complicated then it needs to be? Why not just create one install with bbPress as suggested earlier (http://wppolyglots.wordpress.com/2011/05/30/is-it-just-me-or-is-this-solution/ and http://wppolyglots.wordpress.com/2011/03/24/i-am-getting-a-bit-concerned-about-how/)? In other words create a bbPress install on .org for polyglots and in this install create team specific sub-forums.

      • 11:21 pm on July 15, 2011 Permalink | Log in to Reply

        The discussion is not about all polyglots per se, but rather about the discussion within each language.

        • Mattias Tengblad 11:27 pm on July 15, 2011 Permalink | Log in to Reply

          I get that, still doesn’t see the point. We already got the ability to create local forums, why create yet an other platform? If the point is to organize the individual teams then I stand by my earlier words. To split things up even more is just a bad idea.

      • 11:24 pm on July 15, 2011 Permalink | Log in to Reply

        Ok, reread and noticed the sub-forums point. Forum vs P2 is the whole point of this discussion, yes.

        • Rafael Poveda - RaveN 12:47 pm on July 17, 2011 Permalink | Log in to Reply

          Here goes my opinion. My problem with sub-forums is that they don’t have a good notifications system (e-mail, jabber…), a very useful thing. With P2 we have a real-time-like system.

          Maybe real-time is not neccessary, but it’s very useful when more than 2 people are working in a release.

  • Jiehan Zheng 12:00 pm on June 8, 2011 Permalink | Log in to leave a Comment
    jiehanzheng • cn.wordpress.org editor
    Tags: , , suggestion,   

    This post concerns the Chinese Credits page. Hope @nacin and @vanillalounge or anyone else this may concern could take a look.

    First I am happy to see that the Chinese separator (“、”) is in place on the contributor’s list, but there’s an imperfection that in Chinese we use “。” rather than “.” to indicate the ending of a sentence. So I have one suggestion: to substitue “.” with “。”, or you can just remove the ending period.

    I just discovered that this is managed by the po translation files. So no need to fix on the API side. Sorry for this. Please see my next issue:

    Another thing I want to report is that the current translator list is inaccurate for Chinese. I don’t know how about other languages, but for Chinese it is not. None of the current 4 “validators” indicated on the Credits page is a currently active validator. It should have jiehanzheng (me) for WordPress, and musiclog for bbPress Plugin. kingler and Paveo also worked on WordPress, but they no longer do. Please help remove those who are inactive if possible.

    Thank you.

     
  • Mark Thomas Gazel 12:06 pm on April 29, 2011 Permalink | Log in to leave a Comment
    culturemark • da.wordpress.org editor
    Tags: suggestion   

    Is there a feed or something like that from GlotPress, that i.e. can be listet in a widget or something on the locale sites?

    Or maybe just a function with some daily og weekly statistics on how many string that’s left and how many that have been approved since last. Or something like that.

     
  • jenialaszlo 10:09 pm on April 19, 2011 Permalink | Log in to leave a Comment
    jenialaszlo
    Tags: , , suggestion   

    GlotPress project for bbPress? I am not seeing a bbPress project here: http://translate.wordpress.org/projects although it seems like it would be logical (nice, convenient) to have one. What do you think – pros/cons?

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel