[01:07] *** ChanServ sets mode: +o OliverKrueger
[01:08] Hey there.
[01:08] Hi OliverKrueger
[01:09] Hi George.
[01:09] I received an email from a Benjamin on the webmaster@foswiki.org address.
[01:10] Ah.. .yeah I addressed it. Forgot to reply to the list. Couldn't register?
[01:10] He has problems registering a new account.
[01:10] I tried myself and ran into the same problem.
[01:10] Yeah the anti-spam controls are pretty aggressive. Can we talk in security channel or admin ?
[01:10] or pm?
[01:19] *** OliverKrueger has left
[03:13] *** ChanServ sets mode: +o Lynnwood_
[04:37] [distro] gac410 pushed 1 new commit to master: http://git.io/pUSY
[04:37] distro/master 9c83764 George Clark: Item13295: Don't override Oops errors during save...
[04:37] *** GithubBot has left
[05:26] [distro] FoswikiBot pushed 1 new commit to master: http://git.io/pUd5
[05:26] distro/master 01bac2f Carlinhos Cecconi: Item13252: Translations updated using Weblate (Portuguese (Brazil))...
[05:26] *** GithubBot has left
[05:30] *** gac410 has left
[08:56] *** ChanServ sets mode: +o MichaelDaum
[09:46] hi all, for weblate admin jast I think, if it possible to have "not suggested" link in "string to check" section it could be great
[09:47] indeed, when you're simple user, you just can do suggestion, and you can't filter string without suggestion
[09:48] a such link "not suggested string"/"whithout suggested string" could be useful
[09:48] no idea if it's weblate config or... a feature to dev...
[11:39] GuilainC: feature doesn't exist AFAICT
[12:43] i've take a look about the documentation, I'haven't find it too :(
[12:44] thanks for your answer
[14:04] *** ChanServ sets mode: +o gac410
[14:31] MichaelDaum: Two questions for you if you have a moment.
[14:31] hey george
[14:31] good noon
[14:31] :)
[14:32] UserRegistration page. GuilainC was questioning the lack of trailing : on one field, but on that page, none of the field names have :. But on the other pgs, password change, reset email change reset, etc., They all use the colon
[14:34] And while I was playing around with Registration, I found a javascript error. It appears to no longer create the WikiName from the First & Last names
[14:34] 1.1.9 does. master does not.
[14:35] So were we at one point moving to a style *without* the fieldname colons, or was that just an oversight. I think that was Arthur's work.
[14:36] * MichaelDaum checking
[14:39] where did you say do we use colons and where not?
[14:39] UserRegistration After each entry field label. No : First Name [.....,.] Last Name [....]
[14:40] ya
[14:40] On other user related forms. ChangePassword Password: [.....] New Password: [.....]
[14:41] oic
[14:41] that's inconsistent
[14:41] This also causes duplication of strings when overlapping. Password: and Password(no colon)
[14:41] Yes.
[14:41] so let's add colons
[14:42] I'll investigate the wikification in the meantime
[14:42] Okay. That's what I thought, Thanks.
[14:42] I will wait to add colons until it appears that translation is at a lull. I'll commit weblate first and then push my string changes
[14:43] And hopefully try not to put the repo into conflict
[14:51] have you got a task item already?
[14:51] Hm. Hang on. I opened several last night. now did I do that one ???
[14:52] got the fix for the wikification ... will create one specific to jquery.wikiword
[14:52] No... Want me to open one? Excellent.
[14:54] Item13297 Didn't set a component yet
[14:54] [distro] MichaelDaum pushed 1 new commit to master: http://git.io/pkjs
[14:54] distro/master 262a824 MichaelDaum: Item13298: jquery.wikiword not backwards compatible
[14:54] *** GithubBot has left
[14:55] Darn. I'll delete my task
[14:55] You are too fast :P
[14:56] Thanks MichaelDaum
[14:59] Here and there we have javascript disabled warnings. Noticed on on UserRegistration.
[15:00] * gac410 wonders if we should have a warning banner that just appears on any pages with "This site requires JavaScript for correct operation" or something like that.
[15:01] Maybe something that the user can dismiss. I hate sites were the site is hidden / unreachable without js. But with the 1.2 requirements, a bit more up-front warning might be good..
[15:06] there are too many banners and warnings and popups in this world
[15:06] Okay. As I said, I was just wondering.
[15:07] hi all
[15:07] Hi GuilainC
[15:07] take a look about your discussion
[15:07] the one banner that we is actually legally required ... and that we don't provide ... is the cookies warning
[15:07] what do you think about cookie banner
[15:07] oups MichaelDaum
[15:07] oh and how I hate click away these banners all over the web
[15:07] faster than me
[15:07] is 1.2 have this banner ?
[15:07] no
[15:08] ok
[15:08] imagine you get this banner every single day you hit the intranet wiki
[15:08] as most people clear their cookie store when they close their browser
[15:09] understand
[15:09] is it always possible to do one with broadcast variable and twisty
[15:10] true, GuilainC
[15:10] If there is a legal requirement to do the cookie warning then we probably ought to add it to 1.2. That could block use of foswiki in some jurisdictions
[15:11] Maybe make it a config or skin option. So admin decides whether to clutter the site. :)
[15:12] broadcast + twisty = how to add the legal cookie warning
[15:12] very simple to do
[15:12] I even do one before ;)
[15:12] so very easy :)
[15:15] Ah. I understand. You are saying add it to the SitePreferences Set BROADCAST_MESSAGE = %TWISTY ... Yes that would do it.
[15:15] The cookie will remember it, and sites that don't want it can easily remove it.
[15:15] more don't provide by defaut
[15:15] but provide by default how to add it :)
[15:16] so everybody is happy
[15:16] the scope of foswiki is to provide feature, not to implement it
[15:16] we don't create sessions for guests by default now, do we?
[15:16] hm. well to be "legal out of the box" we can provide it by default, Since most sites customize SitePrefs
[15:16] so the only time we create cookies is when users actively do something that requires remembering data for them
[15:17] jast, That feature is disabled. It's "experimental" so sites can enable it if desired.
[15:17] which is different from most sites, pushing google analytics and whatever onto users
[15:17] But guests get a *new* session every time the authenticate So they would get the warning again.
[15:18] we had discussed that disabling guest sessions by default breaks too many things sites might want.
[15:19] right
[15:19] ... like what? :)
[15:21] You want me to *remember* ???
[15:22] Lets see. Guest commenting, Twisty positions, any script that needs strikeone, some wiki apps use session variables, and those won't work.
[15:23] The recent AntiWikiSpam registration filter uses history saved in the session.
[15:26] GuilainC: I meant to mention. http://trunk.foswiki.org/ has the language selector enabled. So you can see the results of translations ... though you have to wait for an admin to push weblate changes into git.
[15:26] Sometimes it might be helpful to actually view the string in the context of the whole page.
[15:26] twisty positions aren't stored in the session
[15:26] Oh... separate cookie? never mind
[15:26] but yeah, strikeone is a good point
[15:27] GuilainC: your point-out of Password: string missing the colon: ... turns out that the user registration form was missing : on ALL of it's input field labels.
[15:28] And was missing the fullstop after most of the messages. I'll commit and run xgettext later tonight once translate.foswiki.org has no recent changes.
[15:34] thanks gac410 for that... I'm just starting typographic consistency analysis :)
[15:34] there are a lot of more... :)
[15:34] thanks for that, I'm waiting RaulFR validation, before take a look of the translation
[15:34] on trunk.foswiki.org
[15:35] Yeah. We need to be a bit cautious in how much of this we do. I don't want to make too many string changes and get other translators upset at needing to rework.
[15:35] Oh yeah that's right. I forgot you had to wait. Sorry about that.
[15:39] * gac410 poor eyes. Trying to see . and : on my laptop.
[15:43] for french, two eyes are better than only one... and RaulFR has a lot of experience not me
[15:43] for the string
[15:43] don't worry
[15:43] I don't think we have to do absolutely before 1.2
[15:44] it's clearly non blocker
[15:44] is more "quality"
[15:44] but quality is good for such project :)
[15:44] if i were you, first, I will wait that more or less all language translation are done
[15:45] encouraging translators for the new string.
[15:45] and then only, update typographic, consistency issues
[15:45] if getext is not bad, i should be able to find
[15:45] that only difference of the strings are trailing space, final point, colomns
[15:46] then validation of this point is not difficult for any translators even if you don't know the language
[15:46] what do you think ?
[15:52] True. A quick review of typographic changes should be fast. I think that xgettext will detect minor changes and just mark them fuzzy.
[15:52] We'll find out tonight. When I commit the changes to DefaultUserRegistration. It's all typographic.
[16:59] jast I'm going to put my email in the "Send reports on source string errors" as a test. If the volume is low enough, I may change that to the translate list.
[17:05] okay
[17:06] worked well. nice email shows the source string and comment. Too bad we couldn't mail in these to a task. I wonder which email list would be best. foswiki-svn maybe?
[17:07] that would kind of make sense
[17:07] yeah. it's pretty high volume, and only people following it will be the hardcore developers ... or the insane :)
[17:08] I'll do that.
[17:13] that's not high volume ;) I'm subscribed to the git mailing list
[17:14] it's purely developer discussion and has way more traffic than foswiki-svn
[17:16] :) well in the context of foswiki lists, it's the highest volume. I was on Perl5Porters for a while. That's high volume.
[17:28] *** ChanServ sets mode: +o RaulFR
[17:28] hello all :-)
[17:28] Hello RaulFR
[17:37] Bah... The Registration page has a string that is impossible to translate well. %MAKETEXT{"Select [_1] to join:" args="%multiple%"}% Where multiple is substituted as "group" or "groups" (Damn english only developers)
[17:38] * gac410 isn't going to fix it though. Not in the mood to get into %IF statement madness for this feature.
[17:55] [distro] gac410 pushed 1 new commit to master: http://git.io/pLUu
[17:55] distro/master 02de57d George Clark: Item13294: Fix punctuation on Registration page
[17:55] *** GithubBot has left
[18:13] Looks like the sourceforge email list server is stalled again. No emails for the past few hours. :(
[18:14] Anyway. I sent a status update to the Translation list. If you "comment" on a translation and choose the default "Source string comment" an email with the comment will be automatically sent to the developers foswiki-svn email list.
[18:17] So translators, please set comment type to Translation comment for local language comments
[18:19] Developers. We appear to have lost contact with translators ItaloValcy (Spanish) and AndrewPantyukhin (Russian). If anyone has local contact with them, please ask them to fix their email addresses on foswiki.org
[18:40] I've made some headway on the German translation
[18:40] down to 160 untranslated and 82 fuzzy (= broken :))
[18:41] Great. Are you going to commit to the repo?
[18:41] I guess...
[18:41] changes in de, fr, it
[18:42] I figure when you are around I'll let you do it :) Shoot your own foot instead of me shooting mine :)
[18:42] great, now it's my fault ;)
[18:42] [distro] FoswikiBot pushed 15 new commits to master: http://git.io/pL4k
[18:42] distro/master 2f6a033 Marco Ciampa: Item13252: Translations updated using Weblate (Italian)...
[18:42] distro/master 86d0ecb Martin Dahlem: Item13252: Translations updated using Weblate (Danish)...
[18:42] distro/master dbe7fcd Jan Krüger: Item13252: Translations updated using Weblate (German)...
[18:42] *** GithubBot has left
[18:43] German is #2 now... right behind English ;)
[18:44] Need to push the Release01x01 branch too. (If you navigate to http://translate.foswiki.org/projects/foswiki/#repository it will commit / push project wide.
[18:44] okay
[18:45] [distro] FoswikiBot pushed 6 new commits to Release01x01: http://git.io/pLBI
[18:45] distro/Release01x01 7874816 Jan Krüger: Item12813: Translated using Weblate (German)...
[18:45] distro/Release01x01 e98ba7d Martin Dahlem: Item12813: Translated using Weblate (Danish)...
[18:45] distro/Release01x01 17759e4 Raul F Rodriguez: Item12813: Translated using Weblate (French)...
[18:45] *** GithubBot has left
[18:45] BTW, I've seen you mention that you pull before committing. the other way around tends to work better, though I suspect Weblate auto-commits if necessary for pulling
[18:46] Okay. commit, then pull and finally push I was unsure.
[18:48] Is there an email log? I commented on a source string, When email was sent to my own address, it went right through. I updated to use the foswiki-svn list, and it seems to be lost.
[18:48] this is because pull is what combines changes, and it'd rather not clobber uncommitted changes, like svn is prone to doing
[18:48] I have logs at the mail server level, but I can't access that from home
[18:48] well at least it's not worth the hassle :}
[18:48] okay. definitely not worth the hassle.
[18:49] maybe an issue at sourceforge too. For a while commit messages seemed to be stalled.
[18:49] greylisting, perhaps?
[18:50] maybe. I made sure source address is an authorized sender on sourceforge. And checked my own smtp server, no greylist action there. (sourceforge is whitelisted)
[18:52] hmm, fun... Github claims my current session is on OS X 10.10
[18:52] I've hardly ever touched an OS X system
[18:52] interpreting user agent strings is usually a futile venture
[18:56] We supposedly have a feature to allow group membership selection on registration. Seems to be disfunctional :(
[20:24] [distro] Jlevens pushed 6 new commits to Item13135: http://git.io/ptUQ
[20:24] distro/Item13135 fde24bc JulianLevens: Item13135: Tweaked script
[20:24] distro/Item13135 754f33f JulianLevens: Item13135: Tweaked script
[20:24] distro/Item13135 e5f7088 JulianLevens: Item13135: Final main script + amended .gitignores
[20:24] *** GithubBot has left
[20:27] gac410: please checkout Item13135. I've documented my work there and the changes have been pushed to github in branch Item13135
[20:27] Okay. I just noticed your checkin . I'll pull that branch and give it a try.
[20:28] The reason for not pushing directly is that people need to know to run the script as soon as they pull it, otherwise things may look broken
[20:29] okay
[20:32] JulianLevens: Just one comment from reading the documentation. I don't think you can just blanket ignore working. There are a few readme files in that that we ship.
[20:33] Sorry, I don't understand you
[20:34] Oh, got it
[20:35] y, I wondered about that, how would you refine that
[20:35] yeah. We need to not ignore changes to the README files in working. hmm I think there is a way to subtract from the ignore list. hang on
[20:36] Yeah you can use !working/README !working/tmp/README etc.
[20:37] hm Doesn't seem to be ignored ... maybe because it's already in the index.
[20:40] By the way, what is the file ".gitexclude" that you reference. I know of .git/info/exclude but I can't find .gitexclude in the docs
[20:41] yeah, tracked files are ignored by ignore patterns
[20:41] Oh. you may want to also add the LocalSite.cfg. backups to the core .gitignore
[20:42] .gitexclude is used by the tool and its copied to .git/info/exclude (any symlink are added here as well)
[20:42] in other words it's YAFWS (yet another FW special)
[20:43] Ah... okay. so it's a local dev file to help "feed" the .git/info/exclude for stuff you want to ignore beyond the defaults
[20:43] y
[20:44] Hm another addition maybe any ".changes" files in the webs.
[20:45] and lease files
[20:45] Good catches I'll add those
[20:45] looks very good so far JulianLevens
[20:46] MichaelDaum had a lot of custom ignore stuff. So it will be interesting to see his comments.
[20:47] Ok, need to pop out back soon
[20:47] cu later
[20:52] New blocker: :( Item13297: User Registration page REGISTRATIONGROUPS is not functional
[20:52] Works on 1.1.9
[21:03] hm Actually not sure if lease files should be ignored. Leaving them off .gitignore means a simple git clean will clean them. Same for the .lock files for .htpasswd and in that case maybe we should not ignore .changes
[21:05] I am translating to French and checking strings against context and actual use in 1.2 using http://trunk.foswiki.org
[21:06] this string http://translate.foswiki.org/projects/foswiki/distribution-master/fr/translate/?sid=b779a526-c507-11e4-83dc-0201be1ff919
[21:06] okay great. Note there is a delay unless we commit the weblate updates. If you want, let us know and either jast or I can commit.
[21:06] yes, right
[21:06] hm link didn't work. Must be specific to your session.
[21:06] ok.. just a second
[21:07] the string is actually there https://github.com/foswiki/distro/blob/master/NatEditPlugin/templates/editdialog.natedit.tmpl#L36
[21:07] After a commit / push, trunk takes up to 15 minutes to refresh. Happens at each quarter / half / hour
[21:07] it is just "Headings", this appears in the dialog
[21:08] that can be seen when using NatEdit, when you click on the table icon
[21:08] by default, the dialog box suggests 1
[21:08] you can change this value
[21:09] if you change it to 4, you get this http://trunk.foswiki.org/Sandbox/TestNatEditWithTables
[21:10] it actually does not make any sense to me that there could be several "Headings" lines in a table
[21:10] or I am missing something
[21:11] also something I realize there, is that the style heading is no longer bold when the page is being viewed, it is normal font with underlining
[21:11] I have seen multiple heading lines. but it's very unusual. This is MichaelDaum's baby, so best to ask him.
[21:12] yes, I see
[21:12] Ah yeah that seems really strange. The headings are not being handled correctly by the looks of it.
[21:12] Strange. Headings look okay on other topics.
[21:15] I added a simple table with first one, then a 2nd line of headings to http://trunk.foswiki.org/Sandbox/TestCaseSensitivity and it displays correctly. Something else is going on.
[21:17] Okay it's the presence of %EDITTABLE% active on the page. When EDITTABLE is active, then it enables javascript client side sorting of headings, and for some reason looses the styling.
[21:17] I edited that topic
[21:17] switched to Wiki Text
[21:17] used NatEdit to insert a NatEdit table
[21:17] and saved
[21:18] the result is now
[21:18] http://trunk.foswiki.org/Sandbox/TestCaseSensitivity
[21:18] all the headings are messed up, including the ones that were correctly displaying when you posted this link
[21:18] Refresh your page. now look
[21:19] I removed the %EDITTABLE{}% macro from the last table and it fixed them all
[21:19] hmm
[21:20] have we found a bug ?
[21:20] It's a feature of EditRowPlugin. which renders the %EDITTABLE{{}% macro. I would call it a bug. CrawfordCurrie is the author of EditRowPlugin changes.
[21:21] Back to the NatEdit table dialog. To be correct, I think the first line should read "Heading rows:" not "Headings"
[21:22] yes right, I did not understand what was being translated, and that's why I started testing all this
[21:22] Yeah. And GuilianC's issues with Password: on UserRegistration led me down a rat-hole that the REGISTRATIONGROUPS doesn't work on 1.2 ... sigh
[21:23] Trunk has been in development for so very long, and has so many new / changed features. I fear that we are not going to have a quick beta cycle once people really start looking. :(
[21:24] So I think the bug here is "Adding EDITTABLE{}% macro on any table in a page loses styling of all tables on the page.
[21:26] not sure, the EDITTABLE macro was already there on your page and formatting was right
[21:26] I added it, tested, and then I %NOP% it out. Remove the nop and refresh the page.
[21:27] The nice thing is that it changes from server side sorting to client side javascript sorting. But look/feel changes are not good.
[21:29] you are right that if I edit http://trunk.foswiki.org/Sandbox/TestCaseSensitivity using the WYSIWYG editor and take out / include the I see the problem manifesting itself
[21:29] but when you showed me the page initially, the table with EDITTABLE in it was already there
[21:29] it was saved in that page, and it was displaying properly
[21:30] I'm getting confused.
[21:30]