Sorry about second post about that, but we need language sensitive menu links on wiki.centos.org. For example, if users pick any language and wants to see HowTo section, they need open "Learn" section and find there "HowTo" section, or add language code into every link from menu bar. We should solve this. Can someone help? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-docs/attachments/20151004/10f31e59/attachment.html>
On 4 October 2015 at 17:49, Ilyas Arinov <arinov.ilyas at gmail.com> wrote:> Sorry about second post about that, but we need language sensitive menu > links on wiki.centos.org. For example, if users pick any language and wants > to see HowTo section, they need open "Learn" section and find there "HowTo" > section, or add language code into every link from menu bar. We should solve > this. Can someone help?Just acknowledging your message. Yes, I recall that Akemi asked for help and none has been forthcoming. Jim -- In the absence of Ralph are you able to look at what is required at the lower level, please? Alan.
Hello and thanks. Another question about wiki. Will it be mobile adaptive in future and what common stragegy about wiki site or where can i check this out? Thanks. 2015-10-04 23:53 GMT+06:00 Alan Bartlett <ajb at elrepo.org>:> On 4 October 2015 at 17:49, Ilyas Arinov <arinov.ilyas at gmail.com> wrote: > > Sorry about second post about that, but we need language sensitive menu > > links on wiki.centos.org. For example, if users pick any language and > wants > > to see HowTo section, they need open "Learn" section and find there > "HowTo" > > section, or add language code into every link from menu bar. We should > solve > > this. Can someone help? > > Just acknowledging your message. Yes, I recall that Akemi asked for > help and none has been forthcoming. > > Jim -- In the absence of Ralph are you able to look at what is > required at the lower level, please? > > Alan. > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > https://lists.centos.org/mailman/listinfo/centos-docs >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-docs/attachments/20151005/bd637172/attachment-0002.html>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/10/15 18:49, Ilyas Arinov wrote:> Sorry about second post about that, but we need language sensitive > menu links on wiki.centos.org <http://wiki.centos.org>. For > example, if users pick any language and wants to see HowTo section, > they need open "Learn" section and find there "HowTo" section, or > add language code into every link from menu bar. We should solve > this. Can someone help?Well, it seems you just voluteered ;-) Actually the top bar (called 'navi_bar' in moin) is "static" and defined in the wikiconfig.py file. So I don't think that actually it can support multiple languages dynamically. If someone can have a deeper look at moin and how it can (or not) be done, I guess we're all for it. IIRC someone mentioned in the past another "workaround" : removing all items from navi_bar (like FrontPage, Help, etc ..) and have those replaced with languages that are are already present (and maintained) for the whole wiki, so leading users directly to something like wiki.centos.org/$lang and then forget about navi_bar, and only relying on menu presented on the $lang page itself. That "issue" itself has to be considered, but also the fact that the navi_bar can't be extended to infinity either (moin suggests no more than 6 items in that navi_bar, for readability purposes) - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlYSEtYACgkQnVkHo1a+xU7hSwCaA+wakblZq24PiZ24RA7MOVoy GNkAnj4P2jVOCA7Yh7YCedKa4l8Bt69Q =eFuO -----END PGP SIGNATURE-----
IF there will be any updates or migration to improve language-dependent contents, I will do my best to help you. 2015-10-05 12:04 GMT+06:00 Fabian Arrotin <arrfab at centos.org>:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 04/10/15 18:49, Ilyas Arinov wrote: > > Sorry about second post about that, but we need language sensitive > > menu links on wiki.centos.org <http://wiki.centos.org>. For > > example, if users pick any language and wants to see HowTo section, > > they need open "Learn" section and find there "HowTo" section, or > > add language code into every link from menu bar. We should solve > > this. Can someone help? > > Well, it seems you just voluteered ;-) > > Actually the top bar (called 'navi_bar' in moin) is "static" and > defined in the wikiconfig.py file. So I don't think that actually it > can support multiple languages dynamically. If someone can have a > deeper look at moin and how it can (or not) be done, I guess we're all > for it. > > IIRC someone mentioned in the past another "workaround" : removing all > items from navi_bar (like FrontPage, Help, etc ..) and have those > replaced with languages that are are already present (and maintained) > for the whole wiki, so leading users directly to something like > wiki.centos.org/$lang and then forget about navi_bar, and only relying > on menu presented on the $lang page itself. That "issue" itself has to > be considered, but also the fact that the navi_bar can't be extended > to infinity either (moin suggests no more than 6 items in that > navi_bar, for readability purposes) > > - -- > Fabian Arrotin > The CentOS Project | http://www.centos.org > gpg key: 56BEC54E | twitter: @arrfab > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > > iEYEARECAAYFAlYSEtYACgkQnVkHo1a+xU7hSwCaA+wakblZq24PiZ24RA7MOVoy > GNkAnj4P2jVOCA7Yh7YCedKa4l8Bt69Q > =eFuO > -----END PGP SIGNATURE----- > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > https://lists.centos.org/mailman/listinfo/centos-docs >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-docs/attachments/20151005/24ce2a89/attachment-0002.html>