Update header.phtml #23

milotype · 2019-03-24T11:54:39Z

To improve the multilinguality of the website in web-search results, I propose some changes in the meta tags of the of the „header.phtml” file. The idea is to use translated text for the other languages.

Changes would be made for:
a) meta property="og:title"
b) meta property="og:description"
c) meta name="description"

It has something to do with php stuff. As I’m not a programmer, I’m not sure if this solution works, nor if it is legit. But something similar is being used in the „menu.phtml” file.
!!! Please see the diff between my new file and the orig file on master !!!

P.S.
I’ve checked my „experiment” at https://metatags.io/
It seems that html-tags within then strings don’t matter (which I was afraid of).

If my changes don’t work, maybe somebody knows how to handle the issue. But that would probably be something for a feature request ...

To improve the multilinguality of the website in web-search results, I propose some changes in the meta tags of the <head> of the „header.phtml” file. The idea is to use translated text for the other languages. Changes would be made for: a) meta property="og:title" b) meta property="og:description" c) meta name="description" It has something to do with php stuff. As I’m not a programmer, I’m not sure if this solution works, nor if it is legit. But something similar is being used in the „menu.phtml” file. !!! Please see the diff between my new file and the orig file on master !!! P.S. I’ve checked my „experiment” at https://metatags.io/ It seems that html-tags within then strings don’t matter (which I was afraid of). If my changes don’t work, maybe somebody knows how to handle the issue. But that would probably be something for a feature request ...

milotype · 2019-03-24T14:21:25Z

Also, it would be good to automatically add the lang-attribute within the <html> tag, depending on the laguage of the generated file (probably with some php calling, like lang="<?= $language; ?>.). Sorry that I don't know how to implement that. :-(
For instance, the resulting croatian page would have the following:
<html xmlns="http://www.w3.org/1999/xhtml" lang="hr">

fellen

I will look for this after the 3.5 release this weekend.

fellen · 2019-03-25T15:40:55Z

externals/header.phtml

    <meta property="og:type" content="website"/>
    <meta property="og:url" content="https://www.gnucash.org/"/>
    <meta property="og:image" content="https://www.gnucash.org/externals/logo_w120.png"/>
    <meta property="og:site_name" content="GnuCash"/>
-    <meta property="og:description" content="A personal and small-business financial-accounting software, licensed under GNU/GPL and available for Linux, Windows, Mac OS X, BSD, and Solaris."/>
+    <meta property="og:description" content="<?=T_("<span class="gnucash">GnuCash</span> is personal and small-business financial-accounting software, freely licensed under the <a href="https://www.gnu.org/">GNU</a> GPL and available for GNU/Linux, BSD, Solaris, Mac OS X and Microsoft Windows.")?>"/>


This line has several issues, see "Coding" Style in Website Maintenance.

As you seem more fluent in web design, you could improve the wiki page, too.

To prevent flame wars, we try to avoid specific keywords like "Gnu" and "Microsoft".
@gjanssens @jralls Your opinion?

IMHO "double entry accounting" should become part of the keyword list. Suggestion?

In order to avoid "Gnu" and "Microsoft", as well as to add "double entry accounting" into the meta-tag Description, my proposal would be:
<span class="gnucash">GnuCash</span> is a personal and small-business financial software with double entry accounting, licensed under the <a href="https://www.gnu.org/">GPL</a> and freely available for Linux, BSD, Solaris, Mac OS X and MS Windows.
This could be done either by changing the current original string in the po file (#: index.phtml:38), or by adding a new string to the po file. In both cases translations would need to be updated.

BTW, separate descriptions tags in the area of html files are nowadays not recommended any more.

Alternative:
instead of "… freely available for …", it could be "… a free personal …"

<span class="gnucash">GnuCash</span> is a free personal and small-business financial software with double entry accounting, licensed under the <a href="https://www.gnu.org/">GPL</a> and available for Linux, BSD, Solaris, Mac OS X and MS Windows.

The standard term is "Free Open Source" or sometimes "Free/Libre Open Source". Capitalize Free because it's Free as in Freedom as opposed to free as in free beer.
The core of GnuCash is double-entry accounting and the target user population is personal and (very) small business.

I have mixed feelings about the name GNU/Linux, I think it's RMS taking credit for more than GNU is due.
OTOH it should be "Apple MacOS™" (it's not "Mac OS X" anymore) and "Microsoft Windows™", those are the registered trademark names of the operating systems.

Linux too: https://www.linuxfoundation.org/trademark-usage/
More about the story behind gnu vs. linux: https://www.linuxtoday.com/infrastructure/2007091401526opll

externals/header.phtml

fellen · 2019-08-15T05:49:02Z

In between I created https://wiki.gnucash.org/wiki/Website_Maintenance#Metatags to collect some relevant info.

Because Google restricts the length of the description to 105 chars and generates keywords from it in descending priority, I would drop company names.

My personal preference of terms:

Double-entry accounting
Free open source software
personal and small-business
for Linux, Windows, Macos, BSD ...

Has anybody recently built for Solaris? Our wiki page is from 2007 (2.2.0)

jralls · 2019-08-15T15:52:47Z

We should probably remove all mention of Solaris. Aside from museums with old Sun workstations it's nowadays used only on Oracle servers.

As for BSD, OpenBSD and FreeBSD seem to work more-or-less OK, NetBSD has some issues.

fellen · 2020-10-06T04:03:22Z

@milotype I had not realized, your description was the first sentence from index. So I have merged commit 062affd as preview in our beta branch. You can review it at https://www.gnucash.org/beta.

Note: Quotes inside of quotes needs escaping as you remember from https://wiki.gnucash.org/wiki/Translation#Special_characters_and_other_tips. But in this case that was not sufficient as we had 3 levels of quotes. So I have finally choosen strip_tags($description) in the meta section. there is still much to do, but you had a very good idea.

milotype · 2020-10-06T18:47:42Z

@fellen Thanks for looking into it ... https://www.gnucash.org/beta returns a 404 Not Found page. If there's anything I can help with, please let me know.

fellen · 2020-10-06T20:33:29Z

https://www.gnucash.org/beta returns a 404 Not Found page.

Sorry, beta is no page, but a directory. It should be
https://www.gnucash.org/beta/

If there's anything I can help with, please let me know.

Yes,

testing, most changes affect metadata, visible in "Page source text"[?],
adding good test services to https://wiki.gnucash.org/wiki/Website_Maintenance#Testing, …

Known issues:

og:url should return the current page instead of the start page.
some pages still needs to set the description - my next target.

fellen · 2021-01-02T15:26:23Z

I am closing this PR. Almost all aspects have been merged in between.
The exception is the content of externals/global_params.php:$default_description, but that is now discussed in PR #41 .

fellen reviewed Mar 29, 2019

View reviewed changes

fellen closed this Jan 2, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update header.phtml #23

Update header.phtml #23

milotype commented Mar 24, 2019

milotype commented Mar 24, 2019

fellen left a comment

fellen Mar 25, 2019

milotype Mar 29, 2019

milotype Mar 29, 2019

jralls Mar 30, 2019

jralls Mar 30, 2019

fellen Mar 31, 2019 •

edited

Loading

fellen commented Aug 15, 2019

jralls commented Aug 15, 2019

fellen commented Oct 6, 2020

milotype commented Oct 6, 2020

fellen commented Oct 6, 2020

fellen commented Jan 2, 2021

Update header.phtml #23

Update header.phtml #23

Conversation

milotype commented Mar 24, 2019

milotype commented Mar 24, 2019

fellen left a comment

Choose a reason for hiding this comment

fellen Mar 25, 2019

Choose a reason for hiding this comment

milotype Mar 29, 2019

Choose a reason for hiding this comment

milotype Mar 29, 2019

Choose a reason for hiding this comment

jralls Mar 30, 2019

Choose a reason for hiding this comment

jralls Mar 30, 2019

Choose a reason for hiding this comment

fellen Mar 31, 2019 • edited Loading

Choose a reason for hiding this comment

fellen commented Aug 15, 2019

jralls commented Aug 15, 2019

fellen commented Oct 6, 2020

milotype commented Oct 6, 2020

fellen commented Oct 6, 2020

fellen commented Jan 2, 2021

fellen Mar 31, 2019 •

edited

Loading