mirror of
https://github.com/Frumph/comic-easel.git
synced 2026-07-22 01:15:22 -04:00
[GH-ISSUE #23] According to GlotPress, CE is "not properly prepared for localization" (failed import) #21
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JN-Squire on GitHub (Jan 4, 2017).
Original GitHub issue: https://github.com/Frumph/comic-easel/issues/23
So I discovered GlotPress and figured it would be much easier to create and maintain localizations of the plugin with this tool (for now). But it displays the following error:

The help page says "it usually means that something is wrong with the text domain" and talks about getting details through a Slack channel.
So in order to solve this bug, I suggest we get first the details of the failed import @Frumph : do you think you could do it? It would be really helpful.
@Frumph commented on GitHub (Jan 5, 2017):
Does it say "why" it doesn't think it's not properly prepared for localization .. cause codestyle localization is loading it just fine
@JN-Squire commented on GitHub (Feb 24, 2017):
Yes it does.

I just figured how to find the info in the #meta-language-packs channel in the WlordPress Slack group. Here is the screenshot of what happened at the import:
It looks like to needs a special kind of text domain declaration in the file header.
According to the Translations FAQ,
So fixing this bug probably implies to change the "Text Domain" (currently "@ comiceasel" in MO and PO files if I got it right) in ComicEasel plugin header to "comic-easel"?
@Frumph commented on GitHub (Feb 24, 2017):
Okay, will add.
@JN-Squire commented on GitHub (Mar 7, 2017):
@Frumph There, I edited the files. Now we will only know if the requirements are meet once it gets imported in the WordPress repository.
Edit: Since an update on WordPress.org seems needed in order to test the fix, I also updated the readme.txt file. Trying to be careful, I mentioned the GlotPress compatibility is experimental.
@Frumph commented on GitHub (Mar 8, 2018):
added to github, seemed it didnt stick