WordPress.org

Making WordPress.org

Opened 4 years ago

Closed 3 years ago

Last modified 3 years ago

#1076 closed enhancement (fixed)

Setup potbot for WordCamp.org

Reported by: iandunn Owned by: iandunn
Milestone: Priority: normal
Component: WordCamp Site & Plugins Keywords:
Cc:

Description

Currently the only was to support localization is to create individual pot templates for each plugin/theme, and ask translators to manually download them, edit with something like PoEdit, then send us the new one. Then a dev has to diff it, review and commit.

It'd be much easier for everyone if we used potbot and GlotPress, like WordPress.org does.

Change History (16)

#1 @iandunn
4 years ago

  • Owner set to nacin
  • Status changed from new to assigned

@nacin, can you take a look at this when you get time, or point me in the right direction if it's something I can do?

#2 @richardmtl
4 years ago

  • Cc richard@… added

#3 @iandunn
4 years ago

I forgot to mention, the text domain is wordcamporg.

This ticket was mentioned in Slack in #meta by iandunn. View the logs.


4 years ago

#5 @ocean90
4 years ago

  • Owner changed from nacin to ocean90

#6 @ocean90
4 years ago

In 1901:

Translate: Add dashicon for new WordCamp project.

See #1076.

#7 @ocean90
4 years ago

https://meta.trac.wordpress.org/browser/sites/trunk/wordcamp.org/public_html/wp-content is now available at https://translate.wordpress.org/projects/meta/wordcamp.

Some gettext calls are using a different textdomain, that should be fixed at some point.

This ticket was mentioned in Slack in #meta-i18n by ocean90. View the logs.


4 years ago

This ticket was mentioned in Slack in #meta by ocean90. View the logs.


4 years ago

#10 @ocean90
4 years ago

Related changesets: [2238-2239]

@iandunn Are the language files already downloaded by a bot? What's missing here?

#11 follow-up: @iandunn
4 years ago

The only piece left is to automate the installation and updating of the compiled localization binaries. WordPress.org already has a lang-update.sh script which does that, so we’d just need to modify it to work on WordCamp.org. The only potentially significant change would be pulling the list of locales from GlotPress via an API, since GlotPress isn't installed locally like it is on WordPress.org. We could just svn checkout the locales folder or something too, if an API isn't readily available.

It doesn't sound like that's a priority for 2016, though.

#12 in reply to: ↑ 11 @ocean90
4 years ago

  • Owner ocean90 deleted
  • Status changed from assigned to reviewing

Replying to iandunn:

.. The only potentially significant change would be pulling the list of locales from GlotPress via an API, since GlotPress isn't installed locally like it is on WordPress.org.

You can use https://translate.wordpress.org/api/languages for all locales and their data and https://translate.wordpress.org/api/projects/meta/wordcamp to get the locales of the WordCamp project.

#13 @iandunn
4 years ago

Awesome, thanks :)

#14 @iandunn
4 years ago

  • Owner set to iandunn
  • Status changed from reviewing to accepted

After we get this working for the wordcamporg text domain, we should also look into syncing all Core localizations and then those for plugins and themes that don't use wordcamporg, like CampTix.

#15 @iandunn
3 years ago

  • Resolution set to fixed
  • Status changed from accepted to closed

The script to automatically update localizations was added in [wordcamp2216]. It'll run once a day at midnight UTC.

#16 @SergeyBiryukov
3 years ago

#2108 was marked as a duplicate.

Note: See TracTickets for help on using tickets.