Content, more management less system
by Al Thomas
Slightly tongue in cheek title, but the idea is to use what we have already in a more effective way.
What follows leads to a simpler set up than present, but more consistent and productive! It assumes fairly static content, only published infrequently, but allows individuals to experiment as much as they like. It is a practical application of the separation of content from styling. It also loses the curly braces stuff and the PO files. Can't be done? Read on, in rough note form:
1. Use mod_rewrite RewriteCond %{HTTP:Accept-Language}
No need for choose site language drop down
If no relevant file use default language
No need to worry about language specific URLs
No HTTP redirects, but mod_rewrite points path to relevant language directory, or default language if relevant file is not translated
2. Use HTML fragments for content, styled separately with CSS
Master directory with default language, contains header, navigation, footer and content fragments
Directory is listing of available content that needs translating, so content list held in one place. Translators can pick the file they want to translate. mod_rewrite will point to default language file if a translation is not present.
No need to learn yet another set of codes for a given CMS, just a few good old HTML tags - H1,H2, P, IMG, A, UL, OL and LI should be good enough for most? This needs to clear guidance from experience.
Clean HTML. No indentation, Line break in source for new section. Minimise use of class, id and div.
Translators don't need to see header stuff, etc. only HTML content fragment.
Only problem is TITLE and META name=description translations. Use <!-- --> and script below to extract?
Need to view HTML fragment. OK in Firefox. Has to have .html extension in Opera. Crashed Midori. OK in IE6.
Need to make sure UTF-8(?) works in text editors, saving, viewing, distributing.
3. Use git to manage the HTML fragments
Authentication scheme already in place
Distributed system. Translators can work on one page only and feed back to head translator. Flexibility in working.
Allows changes to be made clear through diffs.
Each language has its own directory accessed using mod_rewrite
Recommend minimal set of git commands for translators. clone --depth ?, commit -a translated_fragment, patch?
Allows string freeze using a tag
4. Script to combine fragments
CSS, javascript accessed outside of HTML fragments so can be worked on separately to text.
Separation of style from content.
Script pulls together header fragment, main navigation fragment, relevant content fragment and footer fragment.
This is essentially a rationalisation of the existing set up in an attempt to make things clearer and simpler. Ending up with a few directories only such as:
http://git.fedorahosted.org/git/?p=fedora-web.git;a=tree;f=fedoraproject....
Get prototype up and working in next two months. Need one or two translators to test. Need to produce documentation of process, specifically how to use git and how to edit HTML fragment (don't translate class and id attributes). Work towards simplicity and clarity of procedure before communicating with rest of team. Identify any problems that need to be resolved.
I'm away next week so won't be able to elaborate on this for a while. Happily produce the relevant mod_rewrite commands when I'm back.
All the best
Al
14 years
"fedoraproject" Domains Dispute Registration Announcement
by Luke Luo
(If you are NOT CEO,please forward this to your CEO, because this is urgent.Thanks.)
Dear CEO,
We are the department of registration service in China. we have something need to confirm with you. We formally received an application on May 28 2010, One company which self-styled " TUREV GROUP CO.,LTD." are applying to register "fedoraproject" as Net Brand name and CN&ASIA domain names as below :
fedoraproject.com.hk
fedoraproject.com.tw
fedoraproject.hk
fedoraproject.in
fedoraproject.tw
After our initial examination, we found that the Net brand name applied for registration are as same as your company's name. These days we are dealing with it, hope to get the affirmation from your company. If your company and this"TUREV GROUP CO.,LTD."as the same company,there is no need reply to us,We will accept their application and will register those for them immediately.
If your company has no relationships with that company nor do not authorized,please reply to us within 7 workdays,if we can't get any information from yours over 7 workdays,we will unconditionally approve the application submitted by “TUREV GROUP CO.,LTD."
Thanks for your cooperation.
Best Regards,
Luke Luo
Auditing Department
14 years
Please make the torrent download link More Visible
by Mustafa Qasim
Hi,
You have done a great work and I liked the Fedora 13 download page but
I would ask why the website team didn't made the torrent download link more
visible to users. I personally prefer torrents as it's much faster and I do
serve the community by seeding. I had uploaded 586GB of Fedora 13 Alpha from
my PC last time. I think majority of users as far I know prefer torrents.
So, there should be the torrent link along all the download now buttons or
at least it should be mentioned at the top front of Get Fedora page under
the Other Options section.
It would be great if you can update it on early basis. For further releases
please keep the torrent links on more visible sections of get Fedora page.
--
Regards,
Mustafa Qasim
Executive II, IP Core
Worldcall Telecommunications Ltd. (An Omantel Company)
http://blog.mustu.info
Disclaimer: This message and any files transmitted with it are confidential
and privileged. If you have received it in error, please notify the sender
by return e-mail and delete this message from your system. If you are not
the intended recipient you are hereby notified that any dissemination, copy
or disclosure of this e-mail is strictly prohibited.
14 years
Fwd: FC13 infofeed RSS coming?
by Rahul Sundaram
-------- Original Message --------
Subject: FC13 infofeed RSS coming?
Date: Tue, 25 May 2010 17:54:05 -0400
From: Bill Davidsen <davidsen(a)tmr.com>
Reply-To: Community support for Fedora users
<users(a)lists.fedoraproject.org>
To: Community support for Fedora users <users(a)lists.fedoraproject.org>
I normally follow updates to official releases on the infofeed RSS, since it
tells me not only what was changed but for new apps, what the app does.
Hopefully now there will be one for FC13 as well.
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
14 years
Gone for the next week or so
by Ricky Zhou
Hi, I'll be mostly offline for the next week (and possibly longer) due
to some family health issues.
Thanks, and hope to be back soon,
Ricky
14 years
Browser compatibility testing (in this case, for Spins pages)
by Mel Chua
How do we do browser compatibility testing for Fedora webpages? I
couldn't find notes for this on the wiki, but I may just be missing
something.
The question that prompted this (from Sean Daly of the Sugar Labs
project, copied):
> [http://spins.fedoraproject.org/soas/] is not
> showing any text on my old Mac
> running a very old version of Safari (v1.3.2). Displays OK in Firefox
> though. I don't suppose there is a plain-html version available, or a
> way to warn users their browser is bad?
--Mel
14 years
