IRC log for #koha, 2023-04-18

All times shown according to UTC.

Time S Nick Message
02:14 Jennee joined #koha
02:19 bag joined #koha
02:30 test joined #koha
02:31 test joined #koha
04:34 mtj hi #koha
04:35 mtj hi jennee[m], are you getting the hang of your chat software?
04:37 aleisha hello - does anyone know if i need to do anything special to update the dbix files in ktd? i ran koha-upgrade-schema which added new columns, then dbic, but no schema files were updated
04:42 mtj hi aleisha, take a look at https://perldoc.koha-community[…]_class_files.html
04:43 mtj update_dbix_class_files.pl [--koha-conf <path>] --db_name=db-name \
04:43 mtj --db_user=db-user --db_passwd=db-pass ...
04:43 aleisha i thought dbic was an alias for that script?
04:45 aleisha running the script like ` perl misc/devel/update_dbix_class_files.pl --db_name=koha_kohadev --db_user=koha_kohadev --db_passwd=password` gives me a DBI connect error
04:45 aleisha dbic runs, but doesnt appear to change any schema files
04:46 mtj hmm, pass on the dbic alias, i dont have it defined in ktd
04:47 aleisha ohhh wait figured it out! running an atomic update isnt enough, the changes need to be in kohastructure.sql
04:47 aleisha i thought the script looked at the database itself but i guess it looks at that instead!
04:52 mtj aah yep, that makes sense
06:09 fridolin joined #koha
06:22 cait joined #koha
06:26 cait1 joined #koha
06:27 cait1 good morning #koha
06:28 dcook hola cait1
06:32 cait joined #koha
06:32 cait hi dcook :)
06:38 cait2 joined #koha
06:38 reiveune joined #koha
06:39 reiveune hello
08:08 domm[m] We're currently playing a bit with using LDAP to auth users. Which basically works. But we don't have a 1:1 mapping of categorycode to an LDAP field. Instead, the categorycode needs to be deduced base on the group membership(s) of a user. This does not seem to be possible, or am I missing something?
08:13 ashimema I think there are a few bugs around adding that sort of granularity to the mappings Domm, but they've all stalled for a long time as SSO seems to have taken over in popularity compared to LDAP. Used to do loads of LDAP, but I can't remember the last time I set one up now
09:18 domm[m] ok, thanks, I'll take a look at the issues :-)
09:38 fridolin left #koha
09:47 paulderscheid[m] Morning #koha
09:48 paulderscheid[m] Hey cait what is this?... (full message at <https://matrix.org/_matrix/med[…]EMCTXIWDZvgwSYhLR>)
09:48 paulderscheid[m] s/```%/%/, s/```//, s/`//
09:48 paulderscheid[m] ktd, btw
09:56 Joubu works for me on master, paulderscheid[m]
09:56 paulderscheid[m] Pulling..
09:57 Joubu root@kohadevbox:koha$ koha-translate -i de-DE
09:57 Joubu % l: Unknown or unsupported format specification
09:57 Joubu "working", there is a warning, but not the error you get
10:05 paulderscheid[m] Now I also get that warning but the switch from engl to german is broken in the UI
10:07 paulderscheid[m] To be more precise. Just in the Staff UI. OPAC works.
10:10 Joubu misc/translator/po/de-DE-staff-prog.po:msgstr "Sind Sie sicher, dass Sie \"%s% löschen möchten?"
10:10 Joubu it's saying there is a '% l' that is wrong
10:10 Joubu this one seems suspicious
10:10 Joubu it should be \"%s\" instead I'd say
10:11 paulderscheid[m] Makes sense
10:12 Joubu hum it does not fix the problem
10:15 Joubu paulderscheid[m]: this fixes the problem:
10:15 Joubu -msgstr "Sind Sie sicher, dass Sie \"%s% löschen möchten?"
10:15 Joubu +msgstr "Sind Sie sicher, dass Sie \"%s\" löschen möchten?"
10:15 Joubu -msgstr "Unbekannter Status \"%s%"
10:15 Joubu +msgstr "Unbekannter Status \"%s\""
10:15 Joubu then `koha-translate -u de-DE -d kohadev`
10:16 paulderscheid[m] Thanks, found fixed it right at the same time ^^
10:16 paulderscheid[m] s/,//, s/found//
10:23 cait paulderscheid[m]: de-DE on master is broken
10:23 cait I had 2-3 placeholders messed up and that got pushed... and the next update will be for 23.05
10:23 cait test with French? :)
10:24 cait usually RMaints check for these, but it was missed for the .0 release, it was fixed in .1 but that didn't help master
10:26 mtj hi #koha, is there a way to test the 'correctness' of the .po files?
10:27 ashimema as in compilation?
10:28 ashimema junitmsgfmt misc/translator/po/*
10:28 ashimema and look for 'fatal error' in the output
10:28 ashimema mtj https://wiki.koha-community.or[…]translation_files
10:33 mtj hmm, is that something we could add to the test suite
10:33 oleonard o
10:33 oleonard o/
10:33 davidnind @later tell caroline aude_c: I think I've fixed the build for version 22.11 of the manual - will check once the build is finished to make sure the changes are incorporated
10:33 huginn davidnind: The operation succeeded.
10:35 aude_c[m] thank you davidnind-away!
10:35 paulderscheid[m] I think it wouldn't hurt mtj
10:36 paulderscheid[m] Thank cait I'll watch out for that.
10:36 paulderscheid[m] I need the german one, unfortunately.
10:36 ashimema for rmaint, we do it as part of our release process
10:37 ashimema the fixes, and there are usually a lot of them at the moment, are very manual
10:37 ashimema it's the most annoying part of rmaint for me.
10:47 cait mtj:  not really... because the po files are added just prior torelease
10:47 cait often as one of the last steps
10:48 cait paulderscheid[m]: then you need to fix the 3 mistakes, I am sorry for that... I hoped it was only me suffering for half a year but I guess these times are over
10:48 cait the Rmaint page tells you how you can find the errorenous lines
10:49 paulderscheid[m] No worries, I'll just write a script that fixes them. Just one more thing to run.
10:49 Joubu we could fix them in master, why not,
10:49 Joubu ?
10:50 ashimema we could fix them in master.. it would be a small commit
10:50 ashimema i wasn't aware they were broke 😜
10:50 paulderscheid[m] Well that would be better :D
10:50 cait we normally don't update po fileswith patches, I was not sure if we shoudl do that
10:50 ashimema it raises the same thing I've been raising for ages though.. there is no feedback loop that allows the rmaints to make the fixes stick upstream
10:50 ashimema we have to often fix the same issues over and over again for each and every release.
10:51 ashimema which is soooo annoying
10:51 mtj hmm, im just thinking about having some historical way to track the .po errors
10:51 ashimema we need bernardo's help getting that sorted.. that's a pootle issue
10:51 cait a script to automatically set them to fuzzy would be a start
10:51 cait no need to do that manually really
10:51 paulderscheid[m] Another avalanche of ideas incoming ^^
10:51 cait it would not fix the feedback loop issue
10:51 paulderscheid[m] I love this place
10:51 cait ... maybe we coudl publish the problems somewhere?
10:52 cait so we hav ea script that sets them fuzzy and then send out an email or upload them somewhere where translators can check for errors with their langauge
10:52 cait like... a fancy log
10:52 cait no tsure if it can be fixed on pootle really... unless you do a merge request back on po files with the fuzzy?
10:53 ashimema yup
10:53 cait ... and sorry if I am not making sense, was just done with doing training for today
10:53 ashimema that's exacrtly what we should be doing
10:53 ashimema merging the fixes the rmaints do at every release back up to the po files on pootle
10:53 ashimema we don't just mark them all as fuzzy.. many are real fixes
10:53 ashimema many are also the plural forms headers
10:54 ashimema those really should just be fixed once
10:58 cait it goes always back to we need to have better access to the translation server and processes
11:09 cait1 joined #koha
11:10 mtj we could allow rmaints to run a manual 'release' build in jenkins
11:11 mtj ...which could run some extra release stuff, like testing .po files etc
11:14 marcelr joined #koha
11:14 marcelr o/
11:30 mtj davidnind++ congrats ^
12:21 matts_ joined #koha
12:50 AnkeB joined #koha
13:07 marcelr who want to try bug 29185 ?
13:07 huginn Bug https://bugs.koha-community.or[…]_bug.cgi?id=29185 enhancement, P5 - low, ---, m.de.rooy, Needs Signoff , Show MARC21 tag 765 - Original Language Entry
13:07 marcelr easy one
13:20 emlam joined #koha
13:21 emlam morning all! (or afternoon, or evening, depending on what part of the world you're in :)
13:28 marcelr hi emlam
13:29 ashimema do we need to mark up 765 as which language it's in
13:29 ashimema I recently saw something about this accessability wise marclr
13:30 ashimema exmple: `<span lang="de-DE">Eine Überschrift</span>`
13:33 marcelr ok good point
13:33 marcelr question is do we know it too ?
13:33 marcelr didnt see it in 765 itself
13:33 marcelr could grab it out of 0xx
13:33 ashimema ah.. good question
13:33 ashimema I don't know marc21 well enough
13:34 ashimema I'm not going to fail it for this.. I note I can't see any lang="" in our xslt so I guess we're not doing it anywhere else yet
13:34 marcelr fair enough; new report ?
13:35 ashimema yeah.. I think that makes sense 🙂
13:43 hamid joined #koha
15:00 oleonard joined #koha
15:03 reiveune bye
15:03 reiveune left #koha
15:40 cait ashimema: you can't tell which language it is
15:41 cait not from the record the 765 is in
15:41 cait https://www.loc.gov/marc/bibliographic/bd765.html
15:43 cait hmm. ok maybe ou could use 042 $h, but not sure how often people use that
16:45 aude_c[m] davidnind-away caroline 22.11 manual now has Caroline's new section from the cherry-picked commit. Thank you! 👏 I'll be cherry-picking again tomorrow; hopefully that will all be running smoothly now.
17:11 Mauricio_BR joined #koha
17:19 Mauricio_BR Hello everyone. Please help me with a problem in Koha. When I need to edit an specific marc framework, the changes doesn`t save. I can confirm this consulting the database (marc_subfield_structure). If I change the records directly in the table then the changes stores in the table and the framewok shows the subfields correctly. Console in Chrome shows "The answer has been truncated" when marc_subfields_structure.pl is called. Please helpme, waht could
18:02 cait2 joined #koha
18:03 fridolin joined #koha
18:20 lukeg joined #koha
18:26 cait joined #koha
21:00 cait2 joined #koha
21:03 cait2 left #koha

| Channels | #koha index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary