/srv/irclogs.ubuntu.com/2005/06/30/#ubuntu-doc.txt

=== karlheg [~karlheg@host-250-237.resnet.pdx.edu] has joined #ubuntu-doc
=== karlheg [~karlheg@host-250-237.resnet.pdx.edu] has joined #ubuntu-doc
judaxGreetings01:50
judaxbe back soon03:04
=== FLeiXiuS [~fleixius@pcp0011790326pcs.essex01.md.comcast.net] has joined #ubuntu-doc
=== robitaille [~daniel@d154-5-117-228.bchsia.telus.net] has joined #ubuntu-doc
=== jsgotangco [~jsg@202.57.71.235] has joined #ubuntu-doc
=== Seveas [~seveas@seveas.demon.nl] has joined #ubuntu-doc
=== otep[sch] [~otep@AP-203.167.31.177.sysads.com] has joined #ubuntu-doc
=== jsgotangco [~jsg@202.57.71.235] has joined #ubuntu-doc
=== judax [~judax@ppp-69-148-18-161.dsl.austtx.swbell.net] has joined #ubuntu-doc
=== froud [~sean@ndn-165-139-210.telkomadsl.co.za] has joined #ubuntu-doc
froudAfrican greetings07:52
jeffschhey froud08:00
froudhey jeffsch 08:01
jeffschsay, which tools have trouble with <?yelp:chunk-depth 1?>?08:01
judaxHey froud 08:01
froudjeffsch: well you simply cant validate it08:01
froudto validate you need to comment it out08:01
froudwhy08:02
jeffschit always validated for me...08:03
jeffschwith docbook 4.3 dtd anyway08:03
froudusing what xmllint08:03
jeffschyeah08:03
jeffschdo other tools choke on it?08:03
froudfrom Xerces08:03
froudF A colon is not allowed in the name 'yelp:chunk-depth' when namespaces are enabled. quick-guide.xml file:/home/sean/ubuntu-docs/trunk/gnome/quickguide/C/quick-guide.xml 15:1908:03
jeffschinteresting08:04
froudif xmllint is not giving an error then it is a bug in xmllint :-)08:04
jeffschi was just gonna ask that :-)08:04
froudthe yelp: namespace is not enabled for docbook08:05
=== ealden[class] [~Admi@proxy1.admu.edu.ph] has joined #ubuntu-doc
=== ealden[class] [~Admi@proxy1.admu.edu.ph] has left #ubuntu-doc ["Leaving"]
jeffschi'm thinking just delete the <?yelp:chunk-depth 1?> entirely for the styleguide because yelp is not a target for it08:06
froudmakes sense08:06
jeffschdefault chunk-depth in yelp is 1 anyway, isn't it?08:07
froudyes, if you bump up the number the toc is collapsed to that level08:07
froudor the yelp chunk is done at that level08:07
jeffschok08:08
jeffschI split the style guide into several files because that's what GNOME style guide does08:08
jeffschand to learn a bit more about that stuff at the same time08:09
froudyeah that's ok08:09
froudyou used external entities08:09
jeffschso it won't cause more problems than it solves, you think?08:09
froudno, it is a std practice08:09
jeffschthe only issue i found is in a validating editor such as jedit08:10
jeffschjedit doesn't like it with no dtd declaration08:10
froudyes, because the instances are not valid and well-formed independantly08:10
froudyou must validate from the root08:11
froudor you can use xinclude08:11
froudthat will make each xml-instance valid and well-formed08:11
froudso you can validate the instance08:11
froudbut if you have xrefs to external instances then they will not resolve08:12
jeffschfroud, I could use your help on https://wiki.ubuntu.com/StyleGuide/DocumentStructure08:15
jeffschand https://wiki.ubuntu.com/StyleGuide/DocBookConventions08:15
froudjeffsch: is there such a thing as a constant structure?08:17
jeffschthere are general conventions08:18
jeffschparts, chapters, sections, etc08:18
jeffschwhen to use article tag, when to use book tag08:19
froudthe most structure is in the doctype decl08:19
froudand then the *info nodes08:19
froudand the licenses at the end08:19
froudwhat goes inbetween is variable08:19
jeffschyes, but it is easier to contribute and easier for readers if there is consistency of structure from doc to doc08:21
jeffschconsistency is my main concern08:22
froudHmm, jeffsch I will try to see what is contanstant08:22
froudperhaps this week end08:22
froudI will add it in svn08:22
froudis that ok08:22
jeffschno problem!08:23
jeffschi see that kde docteam has a list of docbook tags that are verboten in kde docs08:23
froudyes08:24
froudwe are not tied to that08:24
jeffschwe must take that into consideration in case any of our kde stuff goes upstream08:24
froudyes,08:24
froudfor stuff that will be in vendor08:24
froudif people want to work in that way08:24
froudI try to do that on books like kynaptic08:25
froudbut lauri watts is strict08:25
jeffschi wonder how much of our stuff will be in vendor08:25
froudnothing08:25
froudvendor is a drop of upstream08:25
froudfor example I will drop kde docs in there08:25
froudthat way we can xinclude to our docs from there08:26
froudbut this is not without problems08:26
froudkde also has a heap of external entities08:26
froudI cant find them now08:26
froudmust speak to lauri about where to find them08:26
froud:-)08:26
jeffschahh, so if we do any work on kde docs in vendor, they will be for the kde docteam, and therefore according to kde style guide?08:27
froudyep yep08:28
froudbut as I undersatnd it, this is a team decision :-)08:29
froudso I am waiting for confirmation08:29
froudI do have one problem though08:29
froudto do with i18n08:29
froudif we use xinclude from vendor/kde08:29
froudhow will people in rosetta translate the parts that are xincludes08:30
jeffschsounds to me like an argument against xincludes08:30
froudso we can work with upstream and benefit, but there is a down side08:31
froudit could be, but I preffer to look at it and resolve the problem08:31
froudwhat I am thinking08:31
froudpreprocess docs that have xinlcudes and output to a completely resolved instance08:32
froudcommit that file to svn08:32
froudupload that to rosetta08:32
froudas pot08:32
froudthen on return route08:32
frouddisagregate08:33
froudand move translations up stream to kde i18n08:33
frouda bit hectic08:33
froudbut technically possible08:33
froudwhat do you think08:33
jeffschI have no doubt that will work, but (speaking for myself only) it sounds like a complicated process with lots of steps08:33
jeffscheach step is an opportunity for screw-up08:33
froudyep yep, I agree08:33
jeffschmy preference is to just copy the stuff over (if allowed by license) and make the docs our own08:34
froudbut do you understand the benefits of xi08:34
froudOk that is one way08:34
froudhave you ever seen howmany commits go to kde docs08:35
froudupstream I mean08:35
jeffschno08:35
froudHmmm :-) many08:35
froudnow if you can harness the upstream comits08:35
froudimagine08:35
froudkde gets commit08:35
froudwe merge it to our vendor08:35
froudour docs are updated08:36
froudpowerful stuff ehe08:36
jeffschyes, provided the upstream stuff stays applicable to us08:36
froudthe trickle down is enormous08:36
froudwell it does08:36
froudI dont see the point in forking upstream08:37
jeffschwhat if kde changes standard menu, and kubuntu does not?08:37
jeffschit is like that in gnome08:37
froudsome stuff we can use and some not08:37
froudwhat can we use08:37
froudfor example the stuff about the kicker08:37
froudor parts of Kcontrol08:38
jeffschfor example, it is more accurate to say that ubuntu desktop is gnome-based than it is to say it is gnome08:38
froudI have a vision that using and repurposing upstream is good08:38
froudjeffsch: agreed08:38
froudtherefore our inlcusion of upstream must be selective08:39
froudand we cannot change xincluded parts that will move upstream to be ubuntu specific08:39
froudwhen making changes in vendor, we must be careful08:39
jeffschhmmm.... careful is hard... more opportunity for screw-up08:40
froudyes, but the power is huge08:40
froudit totally leverages on the power of distributed development08:40
froudthis is wht baz is a long term must08:41
froudwith this power does come an amount of responsability08:41
froudalso consider the two camps work methods08:42
froudat kde everyone with commit can patch a doc without informing th emaintainer08:42
froudat gnome you must first speak to the maintainer08:42
froudso one comes back to the question08:43
froudperhaps it is better just to work upstream08:43
jsgotangcoperhaps08:43
frouddunno08:43
froudthis begs the question, "What are k/ubuntu docs? What is there scope?"08:43
frouds/there/their08:43
jsgotangcoyou're more experienced on this what do you think08:43
froudI think that we need to repurpose upstream to fit the k/ubuntu 08:45
froudbut with that comes challenges as you can see08:45
froudif you look at the outline for kubuntu user guide08:45
froudyou will see that it follows the kubuntu desktop08:45
froudgranted this is kde08:45
froudbut it is not pure kde08:45
froudwhile kde docs are pure kde08:46
froudkubuntu has made changes to kde in order to make it kubuntu08:46
jsgotangcoi dunno maybe later, im in no mood lately to look into these docs08:46
froudk/ubuntu docs are about the changes08:46
froudjsgotangco: :-)08:47
froudjsgotangco: it would make a good team debate :-)08:47
froudit would provide vision, purpose and scope08:47
jsgotangcoi dont think i cannot contribute much in terms of technical stuff because i have none whatsoever08:49
froudjsgotangco: I think it is important that more people undersatnd these issues08:50
froudjsgotangco: otherwise I will make decisions and take more flack :-)08:50
jeffschjsgotangco: you are selling yourself short!08:50
jsgotangcoi think i'll just go back to translating from our team08:50
froudjsgotangco: part of the reason why I am having problems at the team is because of things like this08:51
froudit is hard for me to convey all these things08:51
froudbut equally I need help from team members to make such decisions08:51
froudin the past nobody had such knowledge, but now I see people like jeffsch and gtaylor can help08:52
froudI would hope more will be able to do so08:52
jeffschfroud: then maybe slow down a bit... it may take longer, but in the end it will be stronger08:52
froudjeffsch: yes, I now realise that I must slow down08:53
froudjeffsch: but that has risks08:53
jeffschif the technical hurdle in infrastructure is too big at the beginning, then much time is spent overcoming that hurdle08:54
froudjeffsch: the risk is that much work gets done without consideration and then has to be changed sometime in the future08:54
froudjeffsch: yes, and no writing :-(08:54
froudjeffsch: historicaly I made a technical decision because nobody else could08:55
froudas you can see, that has implicantions08:55
jeffschfroud: yes... you jumped too far ahead for us08:56
=== jsgotangco goes back in a corner doing work
froudyes, and this is why I ask ppl to read Docbook XSL the complete guide08:56
=== jeffsch is glad that at least *somebody* is doing work! :-)
jsgotangco*paid work*08:57
jeffschwow! what's that like?08:57
froudHmm jsgotangco my pay check is a long way off08:57
froudjsgotangco: as you know ;-)08:57
jsgotangcodon't make me feel worse08:58
=== froud gives jsgotangco a love bug hug
jeffschhey jsgotangco, look at https://wiki.ubuntu.com/StyleGuide/WritingForInternationalAudience08:58
jeffschit's pretty much empty, and I have no experience working with translations08:59
jeffschI was hoping that you and mdke could make a contribution to this section of the style guide08:59
jsgotangcoi will research on the styleguide of others, i have no experience on doing this09:00
jeffschsee the gnome style guide. I was thinking of stealing a lot from the translation section of it09:01
jeffschbut I dnon't know what parts are good and what parts are bad (if any)09:01
=== froud goes on school run
jeffschapplicable part of gnome style guide is here: http://developer.gnome.org/documents/style-guide/locale.html09:02
froudjeffsch: you still there09:11
jeffschonly for a couple more minutes09:12
froudI wanted you to see something09:12
froudcan you svn up09:12
jeffschdone09:13
froudthen with pwd trunk/ do make faq-gnome09:13
froudits not totally working, but does what I want for now09:13
froudthen open the output file pr01.html09:13
froud<sect1>09:14
froud            <title>Text Editing</title>09:14
froudnow compare it to in the faqguide09:14
froudfrom line 6909:14
jeffschit's profiled09:15
jeffschi'm guessing. i didn't actually look at it :)09:16
froudyes, so now people can see w orking example ofhow profiles work09:16
froudxsltproc --xinclude --stringparam profile.os "gnome" --stringparam base.dir $(FAQBASE)  $(HTMLXSL) generic/faqguide/C/faqguide.xml09:16
froudif profile.os "kde" then only kde is output09:16
jeffschsay, to change the topic, why do the gnome types use C instead of en?09:17
froudI dunno09:17
froudstrange stuff09:17
froudbut we get a wanted error in our build ;-)09:17
jeffschis there any reason why we have to use C?09:17
jeffschwill it interfere with anything?09:17
froudwhat the error09:18
froudno, the docbook xsl will default to en09:18
jeffschit's not the "expected error" that bothers me.09:18
jeffschit's C instead of en that bothers me09:19
froudoh09:19
jeffschit complicates things09:19
froudits a gnome thang09:19
froudagreed09:19
froudwhat can I do :-)09:19
jeffschif we didn't use C. if we used en instead, would it break anything?09:19
froudyou have a suggestion09:19
froudnot for us09:20
froudif we are shipping html09:20
froudif we ship xml then gnome wants C09:20
jeffschyo mean yelp won't do en?09:20
froudno yelp does not know about en on C09:20
froudonly C09:20
froud:-)09:21
froudI am not sure of the reason for C as apposed to en09:21
froudI just accepted it and made a work around09:21
jeffschok. i have to run. c ya09:22
froudI am already in enough dwang with gnome stuff, don't really want more09:22
froudok c ya09:22
froudme gone to for awhile c ya'll later09:23
=== froud [~froud@ndn-165-139-210.telkomadsl.co.za] has joined #ubuntu-doc
=== jsgotangco [~jsg@202.57.71.235] has joined #ubuntu-doc
=== Seveas [~seveas@seveas.demon.nl] has joined #ubuntu-doc
=== rob^ [~rob@dsl-202-52-55-156.qld.veridas.net] has joined #ubuntu-doc
jsgotangconight all12:50
froudnight12:51
mdkenight jsgotangco :)12:51
mdkemorning everyone else12:51
froudafternoon is after 12 here :-)12:51
mdkenearly 12 here too..12:52
mdkestill12:52
jsgotangcooh yeah12:52
jsgotangcohmmm12:52
jsgotangcofroud, please no infrastructure debates again :(12:53
froudwhy, jeffsch asked12:54
mdkenothing wrong with talking about em12:54
mdkejsgotangco, will you sort a meeting next week btw?12:55
jsgotangcook nvm12:55
jsgotangcohmm a 2-week interval meeting is a good plan12:55
jsgotangcowe still have to sort out some open issues12:55
mdkeyes12:56
jsgotangcoStyleguide for one12:56
mdkenext week then12:56
rob^when is the next meeting planned?12:56
mdkeyeah styleguide number 1 on agenda ;)12:56
jsgotangcolet me check my calendar12:56
mdkemaybe thursday again, if its a good day for peeps12:56
jsgotangcohmmm12:56
jsgotangco30th?12:56
rob^what time zone are you in?12:57
jsgotangcoim in a horrible +8 time zone12:57
rob^ah12:57
jsgotangcowe can revolve around 12UTC and 22UTC12:57
rob^+10 here12:57
jsgotangcobut that would leave jeffsch if we do 12UTC12:57
rob^kilo12:58
jsgotangcoi don't mind 22UTC though12:58
jsgotangco(6AM)12:58
rob^that makes it 8am here12:58
froudmdke: what time is that for us?12:59
mdke22utc is 23 my time12:59
=== froud is hopeless at thse thingy's
mdkemidnight your time12:59
jsgotangcoalright, i'll call up a meeting again for the 30th 22UTC12:59
rob^that time zone are you in froud 12:59
mdkehe's in SA12:59
froudmdke: OK12:59
mdkeUTC +2 iirc12:59
rob^oh.. midnight12:59
jsgotangcoanyone ok with 30th 22UTC12:59
rob^yeah12:59
mdkei am, although I'm sorry for you jsgotangco 01:00
jsgotangcoits ok01:00
jsgotangco6AM the sun is already up01:00
jsgotangcoi can't do 12UTC because jeffsch for sure won't be able to attend01:00
jsgotangcoill put the StyleGuide on top list01:01
jsgotangcobefore anything else01:01
jsgotangcowould a 2 week interval regular meeting be ok with you guys01:01
froud+101:02
=== jsgotangco embraces froud back with arms wide open
jsgotangcoalright, ill whip up an agenda later and email when its done 01:04
jsgotangcoas usual, agenda will be open for suggestions01:04
jsgotangcobut open issues will be tackled first01:05
froudI have no issues01:05
jsgotangcono i meant past issues still open from previous meetings01:05
froudwell no new issues01:05
jsgotangcogreat :P01:05
froudall issues are with you guys :-)01:05
jsgotangcoargghh01:05
jsgotangcogee thanks a lot01:06
froudjust teasing01:06
jsgotangcohmmm koffice in kubuntu instead of ooo01:06
jsgotangcointeresting..01:06
rob^yeah01:06
froudyep01:06
froudRiddell want KOffice01:06
jsgotangcoill leave that to the kde expert (froud)01:06
rob^you can always install ooo if you want it though01:07
froudNot sure why he wants that01:07
froudKOffice is not as ready as OOo01:07
jsgotangcostrange though unless Riddell wants a veryt KDE specific distro release01:07
froudBut I guess this is KDE thang01:07
jsgotangcoyeah01:08
jsgotangcowhen i was with him and amu in sydney, they discussed a lot of very kde specific stuff01:08
froudDont mind either way01:08
jsgotangcolike appeal, etc.01:08
mdkefroud, we can discuss the profiling thing at the meeting01:09
froudwell Riddell is high up in the KDE heirachy01:09
froudmdke: up to you dude01:09
froudyou have a working sample now01:09
mdkeyeah i think that's a good idea01:09
jsgotangcoyeah01:09
jsgotangcosample?01:09
froudyeah do make faq-gnome01:09
jsgotangcoahh right01:10
froudsee the log01:10
froudfrom morning my time01:10
mdkeah cool01:10
froudI suggest ppl look at it and try understand it b4 discussing01:10
mdkebut we can't always read the whole log01:10
froudhuh01:10
mdkeposting to the list helps01:10
froudHmmm OK01:11
froudwill do now01:11
jsgotangcois this similar to make status01:11
mdkewicked01:11
froudyep yep01:11
froudstill have bugs to fix 01:11
mdkewe have lots of cool make tools now thanks to froud01:11
froudneed nice solution for image control01:11
mdkefroud, if you post em all to the list then everyone can use em01:11
froudhe he01:12
froudslowly dude01:12
mdkewhen they are finished sure01:12
froudI just did the profile thing-a-ma-gingy to show you what I mean by profiles01:12
froudI understand now that many ppl dont know what I am talking about onmany things01:12
froudbest way to show it is example01:13
jsgotangconice strategy01:13
jsgotangcook at least i can smile before i retire for the day01:13
froudmdke:  btw about logs see https://wiki.ubuntu.com/ForTheHasty01:13
froudtopic: irc01:14
jsgotangcook bye bye01:14
froudnite jsgotangco 01:14
froudum-pah, um-pah, um-pah-pah one of these days I'll be a dog01:15
froudme thinks of food01:15
froudlater01:15
=== froud is now known as froud-away
=== _froud_ [~froud@ndn-165-139-210.telkomadsl.co.za] has joined #ubuntu-doc
mdke_froud_, yeah i know where the logs are, its in the topic too, just that we don't all have time to read em all01:39
mdkegtg01:39
mdkebbl01:39
=== abelli [~john@1a2fc2eeb774c430.session.tor] has joined #ubuntu-doc
=== christian [~christian@dhcp-214-018.ethz.ch] has joined #ubuntu-doc
=== JonA [~jonathan@alxpc1jaa2.alx.aber.ac.uk] has joined #ubuntu-doc
=== jjesse_ [~jjesse@mail.ftpb.com] has joined #ubuntu-doc
=== jjesse_ [~jjesse@mail.ftpb.com] has left #ubuntu-doc []
=== jjesse_ [~jjesse@mail.ftpb.com] has joined #ubuntu-doc
=== jjesse_ [~jjesse@mail.ftpb.com] has left #ubuntu-doc []
=== jjesse_ [~jjesse@mail.ftpb.com] has joined #ubuntu-doc
=== jjesse_ [~jjesse@mail.ftpb.com] has left #ubuntu-doc []
=== jjesse_ [~jjesse@mail.ftpb.com] has joined #ubuntu-doc
=== jjesse_ [~jjesse@mail.ftpb.com] has joined #ubuntu-doc
=== gtaylor [~gtaylor@130-127-67-44.lehotsky.clemson.edu] has joined #ubuntu-doc
=== ealden [~ealden@219.90.93.78] has joined #ubuntu-doc
=== Seveaz [~seveas@seveas.demon.nl] has joined #ubuntu-doc
=== jiyuu0 [~jiyuu0@219.95.209.48] has joined #ubuntu-doc
=== Njal [~chatzilla@dsl-80-43-183-253.access.as9105.com] has joined #ubuntu-doc
NjalHaving a lil xml problem05:09
mdkehi Njal 05:10
Njallo05:10
NjalBeen writing in the how to find sites of interest in the userguide.xml for gnome05:11
Njaland i can't seem to get links working05:11
jjesse_hyperlinks or links in the wiki?05:11
Njalhyperlinks05:12
mdkeyou make links by referring to entities in global.ent05:12
mdkeyou should see plenty of examples in the userguide already, search for ulink05:12
NjalI use this05:13
Njal<ulink url="http://www.linux.org/groups/">Linux User Group's</link>05:14
jeffschthe end tag should be </ulink>05:14
Njalit didnt even like05:14
mdkeNjal, the best way is to look at existing examples in the document05:15
NjalDammit that was it, thanks, how did i miss that05:15
jeffschoh, and a spelling thing: it's Groups, not Group's :)05:15
Njalkk changing that now05:16
jeffschmdke: howzit goin?05:17
Njalum not sure if what i've wrote is good enough, should i just upload it to where ever?05:17
mdkejeffsch, good thanks, you?05:17
mdkeNjal, you have to create a patch and send it to the list05:17
jeffschfine... except for the dalek nightmares! :-)05:18
jjesse_hmmm can't understand why it won't let me be jjesse on this channel only allows jjesse_ :(05:18
NjalDaleks? You watch Dr Who?05:18
NjalKK patch, how?05:18
mdkeNjal, the way to check your work and create a patch is explained at http://wiki.ubuntu.com/DocteamStepByStepRepository05:18
jeffschNjal: yah05:18
Njaljeffsch: It's awesome05:19
mdkeNjal, try and have a look at the Docteam pages, they are helpful and will save you time05:19
Njalthanks for the link05:19
mdkejeffsch, :)05:19
mdkewasn't it awesome?05:19
jeffschyah. I can't wait for the finale.05:20
mdkeheh05:20
mdkepatience...05:20
mdkehere they've already started the adverts for the christmas episode05:20
mdkeweird05:20
NjalReally05:21
NjalWhen05:21
NjalI need to know about the xmas one05:21
jeffschhmmm... a shift in the space/time continuum05:21
jeffschthere's trouble afoot...05:22
jeffschthe dr can05:22
jeffschthe dr can't be far behind05:22
=== mdke nods
mdkei love the big bad wolf theme05:22
mdkethat was cool05:22
mdkeNjal, just a warning, don't tell jeffsch what happens in the last episode05:23
NjalKK05:23
jeffschyeah. I won't get it until tuesday05:23
NjalWhere you live?05:23
jeffschcanada05:23
jeffschvancouver05:23
Njalah, your not far behind us, i was under the impression that everyone was still on episode 605:24
Njalerm what's the email address i send my patch to?05:25
mdketo the docteam list05:26
mdkeNjal, have you read the wiki page? :p05:26
NjalYes05:26
NjalThough i will re-read it05:27
mdkethanks05:27
jeffschmdke: can you help with https://wiki.ubuntu.com/StyleGuide/WritingForInternationalAudience?05:28
jeffschi don't have any experience with translation stuff05:28
jeffschmaybe much of the content can come from http://developer.gnome.org/documents/style-guide/locale.html05:29
mdkei don't have a lot of experience, but yes it sounds like that is a good idea05:30
Njalpatch sent05:30
mdkethanks Njal 05:31
mdkewhen it arrives we will check it out and submit it05:31
NjalWould it be possible to get feedback on wether it's any good?05:31
mdkeyes05:31
Njalthanks05:31
jeffschmdke: maybe if you just look at the gnome stuff, and see what jumps out as right and what is not so right05:32
jeffschthen let me know, and then I'll do the ubuntu stuff05:32
mdkelooking now05:32
jeffschno rush05:32
mdkeone thing I was thinking about recently05:32
mdkeis the use of &quot; and &apos;05:33
mdkebecause obviously in some languages they will not be used in the same way05:33
mdkedunno what the answer to that is05:33
jeffschhmmm... i think the purpose of &quot; is to make sure that the same unicode code is used consistently05:34
jeffschthe double quote has more than one code in the character tables05:34
mdkeyes05:35
jeffschsometimes " and other times smart quotes05:35
mdkeyeah05:35
mdkei guess its down to the translator05:35
mdkebut sometimes translators don't know what to do with entities05:36
mdkeso far that gnome doc looks good05:36
mdkelots of our documentation violates it ;)05:36
jeffschi suppose if we're not careful, some entities will need translating, and others won't05:36
mdkeexactly05:36
=== gtaylor [~gtaylor@130-127-67-44.lehotsky.clemson.edu] has left #ubuntu-doc ["Kopete]
mdkejeffsch, ok have read the gnome doc, looks good05:39
Njalanyway i have to go05:40
Njali will talk later perhaps when i have something more to submit05:40
mdkeNjal, 05:40
mdkeyour email hasn't arrived yet05:40
NjalIt's been bounced pending mods decision05:41
mdkeNjal, you're not subscribed to the docteam list?05:41
Njalas a guest05:41
mdkesubscribing is a really good idea05:41
mdkethat way you find out what we are doing and so on05:41
NjalI went through the subscription process05:41
Njali get emails from the list loads05:41
mdkehmm05:42
mdkeif you're subscribed you should be able to post05:42
=== Seveas [~seveas@seveas.demon.nl] has joined #ubuntu-doc
NjalI know, i don't claim to know what's going on05:42
mdkehmm05:42
mdkelist info is here: http://lists.ubuntu.com/mailman/listinfo/ubuntu-doc05:43
mdkewhat's your email address, i'll see if you're subscribed05:43
Njalneilmunro@gmail.com05:44
mdkeyou're not subscribed05:45
Njaloh right05:47
NjalI'll just re-join then05:47
mdkecool05:47
Njalthat's really odd05:47
mdkeif you subscribed when the list was down, that might have been the problem05:48
Njalah05:49
Njalim just waiting for the subscribe email05:49
mdkek05:49
=== Burgundavia [~corey@S0106000000cc07fc.gv.shawcable.net] has joined #ubuntu-doc
=== abelli_ [~john@ef770a5136dd70e6.session.tor] has joined #ubuntu-doc
abelli_halo mora.06:31
=== jjesse_ [~jjesse@mail.ftpb.com] has joined #ubuntu-doc
=== Njal [~chatzilla@dsl-80-43-153-65.access.as9105.com] has joined #ubuntu-doc
Njalthat's odd07:03
NjalAs soon as i log in here i get my confimation email that i am now a member07:03
=== philipacamaniac [~phliipaca@208-47-135-198.dia.cust.qwest.net] has joined #ubuntu-doc
=== squinn [~sean@68.205.198.0] has joined #ubuntu-doc
squinnhey, _froud_ 08:15
=== philipacamaniac [~phliipaca@208-47-135-198.dia.cust.qwest.net] has left #ubuntu-doc []
=== zzzsleepy [~zzzsleepy@4bdee6d6eadda9b3.session.tor] has joined #ubuntu-doc
=== djm62 [~djm62@82-40-60-28.cable.ubr08.uddi.blueyonder.co.uk] has joined #ubuntu-doc
=== endy [~endy@cpc3-nfds8-3-0-cust183.leic.cable.ntl.com] has joined #ubuntu-doc
=== endy [~endy@cpc3-nfds8-3-0-cust183.leic.cable.ntl.com] has left #ubuntu-doc ["Leaving"]
=== mpt [~mpt@203-167-186-117.dsl.clear.net.nz] has joined #ubuntu-doc
=== djm62 [~djm62@82-40-60-28.cable.ubr08.uddi.blueyonder.co.uk] has left #ubuntu-doc []
=== jjesse_ [~jjesse@mail.ftpb.com] has left #ubuntu-doc []
=== karlheg [~karlheg@host-250-237.resnet.pdx.edu] has joined #ubuntu-doc
=== JonA [~jonathan@alxpc1jaa2.alx.aber.ac.uk] has joined #ubuntu-doc
=== froud [~sean@ndn-165-139-210.telkomadsl.co.za] has joined #ubuntu-doc
=== Njal [~chatzilla@dsl-80-43-153-65.access.as9105.com] has joined #ubuntu-doc

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!