[Online Help] Assistance with translating the Online Help Files

uli · 2016-04-18 18:27:35

When I supply you with something like the English Github directory/file structure from pophelp master, that’s something you can work with, right?

uli · 2016-04-18 20:00:48

Import capabilities have been removed recently from the admin side, do I remember that correctly (so no need to keep that in admin/about_privileges.textile)? If so: Please delete that from the current English pophelp file (2x).

Last edited by uli (2016-04-18 21:44:06)

uli · 2016-04-18 20:28:10

The pophelp link for Article > Article image currently opens the same pophelp as Article > Article title. If that isn’t gone with the new Github pophelp directory/file assignment: Please make the necessary changes.

Last edited by uli (2016-04-18 21:45:55)

uli · 2016-04-18 21:31:25

Please, somebody tell me about the h1-naming-scheme inside the pophelp files, as I think there are inconsistencies in the English version already that would multiply into all translations.

Almost all h1s are set up according to the scheme “Menu item > Page object”, e.g. “Preferences: Apply rel=“nofollow” to comments?”

But then there are some h1s like e.g. “Files: Categories” (in category/article_category.textile) that should –– according to the above scheme –– actually be “Categories: File category”. Also, all files in directory article have an h1 starting with “Articles” that should –– in my understanding –– be “Write”, referring to the page they’re on.

gaekwad · 2016-04-20 08:31:35

uli wrote #298677:

When I supply you with something like the English Github directory/file structure from pophelp master, that’s something you can work with, right?

Yes.

philwareham · 2016-04-20 08:36:56

Hi Uli,

Please bear in mind that the pophelps don’t just cover v4.6 – there are help files that are still needed for users of v4.5 or earlier. The import help being an example of that.

philwareham · 2016-04-20 08:37:49

uli wrote #298680:

Please, somebody tell me about the h1-naming-scheme inside the pophelp files, as I think there are inconsistencies in the English version already that would multiply into all translations.

Almost all h1s are set up according to the scheme “Menu item > Page object”, e.g. “Preferences: Apply rel=“nofollow” to comments?”

But then there are some h1s like e.g. “Files: Categories” (in category/article_category.textile) that should –– according to the above scheme –– actually be “Categories: File category”. Also, all files in directory article have an h1 starting with “Articles” that should –– in my understanding –– be “Write”, referring to the page they’re on.

Please open an issue in the repo for this.

gaekwad · 2016-04-20 08:37:58

uli wrote #298680:

Please, somebody tell me about the h1-naming-scheme inside the pophelp files, as I think there are inconsistencies in the English version already that would multiply into all translations.

Almost all h1s are set up according to the scheme “Menu item > Page object”, e.g. “Preferences: Apply rel=“nofollow” to comments?”

But then there are some h1s like e.g. “Files: Categories” (in category/article_category.textile) that should –– according to the above scheme –– actually be “Categories: File category”. Also, all files in directory article have an h1 starting with “Articles” that should –– in my understanding –– be “Write”, referring to the page they’re on.

I had a similar question, actually. My understanding is that Write is used to make an article, and articles are viewable from the articles pane. The subject is the article rather than the pane heading itself – I think.

gaekwad · 2016-04-20 08:40:08

philwareham wrote #298710:

Please open an issue in the repo for this.

Done: github.com/textpattern/pophelp/issues/27

philwareham · 2016-04-20 08:40:14

It should probably be changed to ‘Write’ for consistency, I think.

gaekwad · 2016-04-20 08:43:34

philwareham wrote #298713:

It should probably be changed to ‘Write’ for consistency, I think.

I’ll take dibs unless you want to pull rank, PW.

philwareham · 2016-04-20 08:44:49

Be my guest! :) I will then put in RPC.

gaekwad · 2016-04-20 08:46:34

Done in GitHub: github.com/textpattern/pophelp/commit/89a09484cecd8cd3c05863310c856d19782d18d9

Last edited by gaekwad (2016-04-20 08:47:00)

philwareham · 2016-04-20 09:10:46

OK thanks, now in RPC too.

uli · 2016-04-20 12:31:25

Thanks for the answers, guys, and thanks, Pete, for opening the Github issue.

I found one more issue in en-en, in files/upload.textile. It says there:

Use the Textile code to render graphics within articles, the Textpattern code to place graphics on your page templates, or HTML code to place the graphics elsewhere.

Several points:

There’s no code (might have differed in ancient versions, but should we still serve v4.0.n?) but links to popup windows. No code there, either, but one can create code with these. So it should be worded to reflect that.
The code created there doesn’t render graphics but download links (we’re on the Files panel).
forms (Textpattern ~) should also be mentioned, for sake of completeness, I think.
If I’m not totally wrong the word “elsewhere” can also be “everywhere”, which I––mistakenly––read the first time.

Just a reminder: You didn’t seem to touch on the following point.

uli wrote #298679:

The pophelp link for Article > Article image currently opens the same pophelp as Article > Article title. If that isn’t gone with the new Github pophelp directory/file assignment: Please make the necessary changes.

Last edited by uli (2016-04-20 13:01:29)

Textpattern CMS

Textpattern CMS support forum

#1 2016-04-18 18:27:35