← Previous day | Today | Next day → | Search | Index
All times shown according to UTC.
| Time | Nick | Message |
|---|---|---|
| 01:34 | cait1 joined #koha | |
| 05:49 | Joubu | cait, caroline, aude_c[m]: html and epub versions of the manual have been automatically generated during the night, which means we have everything ready :) It could be nice to do some testing on your side: like focus on a couple of strings today then see tomorrow the strings in the generated versions and see if they are there. |
| 05:49 | (talking about the *translated* versions of course) | |
| 06:04 | marcelr joined #koha | |
| 06:04 | marcelr | o/ |
| 06:22 | cait1 | :D |
| 06:22 | Joubu++ | |
| 06:23 | Karter[m] | Morning everyone, quick question about some language pack files and ' Fuzzies ' . I am on the Pootle server checking some translations and we noticed on the 23.05 version there are around 8,703 ( incomplete ) where as in the 22.11 version there are around 64 incomplete. Is there a possibility that the new file version is merging the not corrected translated text or merging the text without translation indication of 'fuzzy'. Basically does |
| 06:23 | anyone know the reasoning behined all these ( incompletes ) ? | |
| 06:24 | cait1 | wihch language ar you looking at? |
| 06:24 | a lot of new strings between versions is not unusual | |
| 06:26 | we keep adding too many things :) | |
| 06:26 | Karter[m] | nederlands :) |
| 06:26 | the nl-NL-staff-prog.po file specifically | |
| 06:27 | cait1 | ah yes |
| 06:27 | I think it's likely the normal update | |
| 06:28 | Karter[m] | haha great thankyou |
| 06:28 | cait1 | when a new version comes out, the old po files are merged, but we add new things, restructure templates... it can add up to a few 1000 strings |
| 06:28 | we restructured breadcrumbs and page titles | |
| 06:29 | i believe a lot of the fuzzies ould come from that | |
| 06:29 | Karter[m] | ahh thankyou i will pass this on \ |
| 06:29 | cait1 | I also see a lot where an ending space or so is a difference |
| 06:30 | https://translate.koha-communi[…].po#unit=28954798 | |
| 06:31 | it doesn't look totally wrong at least, but I don't quite remember from our 23.05 translateion, it's been a while already | |
| 06:31 | Karter[m] | Yes thankyou I see what you mean, I think the person in charge of checking our text and translations is worried it says 8700 haha |
| 06:31 | cait1 | bbia |
| 06:31 | b | |
| 06:32 | at least those are usually quick to fix :) | |
| 06:37 | reiveune joined #koha | |
| 06:38 | reiveune | hello |
| 06:45 | thibaud_g joined #koha | |
| 06:45 | thd joined #koha | |
| 06:45 | Joubu | Karter[m]: I've just tried some of them (nl/fuzzy/nl-NL-staff-prog.po) and they look correct to me, they need adjustement |
| 06:46 | thd | Joubu: Thank you for starting the DMARC test for the koha-devel lists. |
| 06:47 | Joubu: Do you have command line access to the system running lists.koha-community.org? | |
| 06:50 | Joubu: DKIM signatures are not being rewritten for koha-devel which has led to DKIM failures in the past. I have a fix but I need to know what MTA is being used on the system. Most likely Postfix. | |
| 06:51 | Joubu | no, it's hosted by BibLibre, either lds or fridolin should have access. |
| 06:52 | thd | Thanks. |
| 06:53 | IP address is 212.47.245.115. | |
| 06:56 | cait joined #koha | |
| 07:02 | thd | Joubu: You use Gmail which has only sometimes been excessively strict. Currently, at the address where I tested, the Gmail system passes DMARC messages with SPF and DMARC even without a DKIM signature which should be an important part of DMARC. Gmail may even prefer DMARC with no DKIM signature to SPF and DKIM without DMARC. I have not tried sending bad D |
| 07:03 | .. not tried sending bad DKIM. | |
| 07:13 | * cait | waves |
| 07:14 | magnuse | \o/ |
| 07:47 | * cait | did it. |
| 07:48 | cait joined #koha | |
| 08:10 | magnuse | cait++ |
| 09:20 | Joubu joined #koha | |
| 09:43 | Karter[m] | question - Translations / Language packs - If a file version 22 has correctly translated ' AAA ' -> ' BBB '. What causes a ' Fuzzy ' |
| 09:45 | Joubu | black magic |
| 09:45 | :D | |
| 09:46 | do you have an example? | |
| 09:46 | Karter[m] | if that was my question ignore it sorry misclicked enter ^ |
| 09:49 | Joubu | If you find occurrences of strings that are marked fuzzy when you think they shouldn't, you can report them to me |
| 10:52 | krimsonkharne[m] | hey #koha |
| 10:58 | jzairo joined #koha | |
| 11:06 | Joubu | I really need bug 35079 pushed ASAP |
| 11:06 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=35079 enhancement, P5 - low, ---, julian.maurice, Signed Off , Add option to gulp tasks po:update and po:create to control if POT should be built |
| 11:07 | davidnind | Joubu++ # Thanks for answering my questions/suggestions for the git workflow for the manual |
| 11:08 | Joubu | no problem! Let me know if you have more :) |
| 11:11 | cait | :) |
| 11:11 | Joubu++ davidnind++ | |
| 11:11 | love to see the movement on manual and translations | |
| 11:12 | super excited about having a translated manual again! | |
| 11:14 | can someone activate kidclamp for me? :D | |
| 11:23 | ashimema | still only 7.20 am for kidclamp right now cait 😜 |
| 11:28 | cait | ah ok, then we will let him rest a while longer :) |
| 11:36 | khall on the other hand... | |
| 11:37 | Bug 33664- Add ability to cancel order line is waiting for you again | |
| 11:39 | ashimema | Lol |
| 11:39 | Pretty sure they share a timezone | |
| 11:40 | Lucas is different, think he's ahead of them | |
| 11:41 | cait | kyle just failed my patch earlier, so he can't claim being asleep heh |
| 11:41 | tcohen[m] | Kyle starts working around 6, he doesn't count |
| 11:49 | magnuse | cait: have you never failed a patch in your sleep? |
| 11:52 | ashimema | Haha |
| 11:52 | Indeed.. I said it was early.. didn't comment on what early birds they are | |
| 11:53 | I often talk to them at inappropriately early times without realising until half way through a conversation | |
| 11:57 | tcohen[m] | I always assume you know I'm asleep ashimema, and just leave me the note for later heg |
| 11:58 | ashimema | yeah, I do that too |
| 11:58 | but still feel bad when you reply | |
| 12:00 | that reminds me tcohen,, did you get my later? | |
| 12:00 | shall I add those tests.. | |
| 12:02 | tcohen[m] | we will need them |
| 12:02 | not the highest priority for today | |
| 12:04 | cait++ # just saw the roles wiki | |
| 12:08 | kidclamp joined #koha | |
| 12:11 | Karter[m] | I am trying to explain the procedure to someone with translation files and i think this would clear up their question but want to make sure i am telling them truth : Is this statement correct? When a new file version is created by the translator in Pootle, the file versions from 22 are merged to help create file version 23. The translators can then work on the file to make and check the translation strings for correctness, and then upload them |
| 12:11 | to Pootle. In the case someone updates file version 22 and makes translation changes, if these changes occur after version 23 was initially created, then the changes will not have been included in file version 23, as the updated version 22 file has not been merged since it was merged before this change. Therefore, if a translation is marked as 'Fuzzy' in file version 22, and a new version, 23 is created, and the translated string has not been | |
| 12:11 | checked, it will continue to be marked as 'Fuzzy.' However, if in version 22, it does NOT show 'Fuzzy,' then 'fuzzy' will only be added if that string has been modified and requires attention. There will NOT be any reason for a version 22 to merge again as it is now outdated and we should be working form version 23. | |
| 12:14 | the reason is, I am being come to with a file version 22 which has 60 incompletes and the person is worried that every version release, the manual changes made in 22, if they have not been fixed by a translator before the next version is released, then they will need to manually fix the translations again as their file is now not the latest version being merged. | |
| 12:20 | cait | Pootle will soon be Weblate, but the process is the same |
| 12:20 | if you explain, maybe keep it neutral | |
| 12:20 | 1: yes, we create the new version files from the ones from the version before | |
| 12:20 | Karter[m] | yes im trying not to choke on my words with this to here and the person im trying to help haha |
| 12:21 | cait | 2: also yes, we only merge once, so once the new version is out, you need to fix both |
| 12:21 | if you have corrections or changes | |
| 12:21 | Karter[m] | And what adds the fuzzy indicator, is that always manually added by a human or can it be computer generated? |
| 12:21 | Joubu | Karter[m]: The easy way to say it is .po files are not shared between version |
| 12:21 | cait | 3: I think is correct too (fuzzy will remain fuzzy, changed onces will be new fuzzies) |
| 12:22 | Joubu | if you modify a string in version X, it won't be modified in version Y |
| 12:22 | cait | with Y being the later version if the po files have already been created |
| 12:22 | you always need to make sure you fix the newest version so that your changes stick moving forward | |
| 12:22 | Joubu | unless you are working on the last version, in this case the next version will do a snapshot of the .po files and reuse them |
| 12:23 | Karter[m] | clear thankyou to you both |
| 12:24 | Joubu | BUT weblate is supporting translation propagation between component. So soon we will have modification propagated between versions (hopefully, I have not tried yet!) |
| 12:25 | cait | I think Pootle also had a suggestion feature |
| 12:25 | it would suggest you the strings from the other versions to easily accept them | |
| 12:25 | Joubu | it's not a suggestion |
| 12:25 | it's propagation | |
| 12:25 | cait | so ti's usually not super horrible |
| 12:26 | I was talking about pootle, it would fil in the input field or offer you otpions to click on from other versions for similar strings | |
| 12:41 | meps007[m] joined #koha | |
| 13:24 | Dyrcona joined #koha | |
| 13:45 | Joubu | Does this make sense and help to understand the black magic, or does it add confusion? https://snipboard.io/k5tCnz.jpg |
| 13:46 | Context: how the translation workflow work for the manual | |
| 13:46 | ashimema | nice |
| 13:46 | Joubu | aude_c[m], cait ^ |
| 13:46 | ashimema | that's awesome |
| 13:46 | cait | I like images, but need a moment to process |
| 13:47 | the ad makes it hard to read and download gives a black image :( | |
| 13:47 | Joubu | Sorry, I am not seeing the ads :-/ |
| 13:47 | cait | seem bigger than usual |
| 13:48 | * ashimema | didn't see ads either |
| 13:48 | cait | maybe you got a good blocker |
| 13:48 | Joubu | cait: https://cloud.joetka.eu/s/WMC8dJyzeeNRQbE |
| 13:50 | I wanted to have both koha and koha-manual on the diagram, but I think koha deserves its own :D | |
| 13:50 | cait | hm what is not clear for me right now is where the Koha is |
| 13:51 | you say pull koha-manual and koha-mnaual-i18n - but we also need koha somewhere for the updating? | |
| 13:51 | do you pull that there too? | |
| 13:51 | ugh, manual | |
| 13:51 | yes, you are right, it deserves it's own diagram :) | |
| 13:52 | Joubu | it's all about the manual |
| 13:52 | cait | yes, I was confused |
| 13:52 | Joubu | but it's the same :D |
| 13:52 | cait | I like the little librarian |
| 13:52 | Joubu | just replace koha-manual with koha |
| 13:52 | cait | well all the stick figures |
| 13:52 | Joubu | what is different is not really on the image actually |
| 13:53 | cait | the koha-manual-i18n is a litle lonely - what goes in there? |
| 13:53 | Joubu | ha yes, it's different for the consumers |
| 13:53 | it's the scripts, to make everything works | |
| 13:53 | cait | ah ok |
| 13:53 | Joubu | it's what is run by the cronjob |
| 13:54 | it's the "merge po" step | |
| 13:54 | cait | makes sense |
| 13:54 | where shoudl we put it for safe keeping? wiki? | |
| 13:56 | Joubu | I am in the documentation step, waiting for Koha branches to be ready (ie. push and backport what I need to continue) |
| 13:56 | I will put it somewhere when finished, no worries ;) | |
| 13:56 | cait | :) |
| 13:57 | Joubu++ | |
| 14:02 | bag joined #koha | |
| 14:23 | Joubu | cait, ashimema: And I guess this is what it will be for Koha - https://cloud.joetka.eu/s/PecQXrfMxayaGej |
| 14:27 | ashimema | that's really nice |
| 14:27 | I like | |
| 14:28 | adding in eventually the full removal of translations from the core koha repo 😜 | |
| 14:28 | which we've been discussing for best part of a decade right | |
| 14:28 | Joubu | see bug 35174 |
| 14:28 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=35174 enhancement, P5 - low, ---, jonathan.druart+koha, ASSIGNED , Remove .po files from the codebase |
| 14:28 | cait | Joubu is getting us there :) |
| 14:28 | Joubu | this is for next cycle |
| 14:29 | It won't be hard. The hard part is to remove them from the git history | |
| 14:29 | cait | maybe not only the package manager, but also RMaints? we need the tarball to still include or have another way of easily installing them |
| 14:29 | Joubu | git clone :) |
| 14:30 | cd misc/translator && git clone https://gitlab.com/koha-community/koha-i18n.git po | |
| 14:30 | and you are done | |
| 14:30 | you have the same structure as before | |
| 14:30 | cait | true, but I see the mailing list pots incoming |
| 14:30 | Joubu | it's what I've done yesterday for koha-manual |
| 14:31 | cait | we'll talk about that as soon as we get there |
| 14:31 | Joubu | I've included RM and RMaints in the diagram, the "release" use case is what you mean |
| 14:31 | cait | also: we are building our own packages, please include instructions :) |
| 14:31 | yeah | |
| 14:32 | Joubu | I think we will have koha-l10n that will be required for koha |
| 14:32 | so I think it won't change much if you build your own packages | |
| 14:32 | cait | that's good |
| 14:32 | Joubu | for koha-common I mean |
| 14:32 | tcohen[m] | hey, traefik is down on the main server, so jenkins and wiki are not accessible. I'm looking at it |
| 14:32 | cait | it'slovely that the translations get auto-updated when you install a new package |
| 14:32 | i'd like to keep it that simple for deployment | |
| 14:32 | don#t mind if there is an extra step somewhere | |
| 14:33 | hm also instructions for devs on how to test translations (can't/shouldn't clone that inside my Koha git repo I think) | |
| 14:33 | or best... built it into kohadevbox right away please :D | |
| 14:33 | Joubu | we could even have koha-l10n built nightly, and you would get your translations in production the day after, after an update of koha-l10n |
| 14:34 | for devs, and ktd, it will be as simple as the git clone command I pasted above | |
| 14:34 | cait | for production it would be just great to not require any extra steps, I think otherweise it's ok |
| 14:34 | because if you have nightly it doesn# thelp outside of master | |
| 14:35 | because of the monthly release/changing you'd not want other po files/updates until you also update Koha | |
| 14:35 | Koha version = po file version need to match | |
| 14:35 | Joubu | you are right |
| 14:36 | too bad | |
| 14:36 | lds joined #koha | |
| 14:36 | Joubu | there is a way, but less easy :) |
| 14:37 | reiveune | bye |
| 14:37 | reiveune left #koha | |
| 14:39 | cait | i think including them on release time for now is good |
| 14:52 | ashimema | tcohen |
| 14:53 | I posted a patch to fix regressions.t | |
| 14:53 | on bug 35119 | |
| 14:53 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=35119 enhancement, P5 - low, ---, martin.renvoize, RESOLVED FIXED, Make bibliographic errors more prominent and match current styling |
| 14:53 | ashimema | just looking at the other failing tests.. I 'think' they're unrelated to that patch.. just trying to work out what might be causing them |
| 14:56 | cait | hm bug 35176 is interesting- we have the same phenomenon for subscriptions (also filed already) |
| 14:56 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=35176 enhancement, P5 - low, ---, koha-bugs, NEW , Unable to delete itemnotes_nonpublic |
| 14:56 | cait | could it be a change to the objects or so? |
| 15:00 | bag joined #koha | |
| 15:00 | Joubu | Have a great weekend #koha! |
| 15:01 | cait | you too! |
| 15:09 | krimsonkharne[m] | you too joubu and bye everybody :-) |
| 15:17 | cait | bye all :) |
| 15:17 | cait left #koha | |
| 15:25 | matts | Have an excellent week-end everyone ! |
| 15:56 | tuxayo | @later tell marcelr I've SOed bug 35111 so you are free to QA it if it looks good to you. (the 1st SO was from you. So we can swap roles) |
| 15:56 | huginn | tuxayo: The operation succeeded. |
| 15:57 | cait joined #koha | |
| 15:58 | tuxayo | marcelr++ thanks for collecting all the background jobs bugs |
| 16:40 | raap joined #koha | |
| 16:40 | raap | buen dia. Quien me puede ayudar?? |
| 16:57 | davidnind | raap: Welcome! Ask your question, if someone can answer, they may respond. It is often quite here (particularly in the weekends), so you may not get an instant response... |
| 17:02 | quite should be quiet! | |
| 18:03 | raap joined #koha | |
| 18:03 | raap | hola |
| 18:03 | tengo instalado KOHA y funciona correctamente. Como hago para acceder a KOHA desde una computadora remota con un navegador?? | |
| 18:11 | ashimema | You'll need to set up DNS |
| 18:13 | Or.. access using the IP address of your server | |
| 18:20 | raap | probare. Gracias |
| 18:33 | davidnind | making your catalog available on a network (including the internet) is a standard networking/web server configuration issue - not specific to Koha (1. Have DNS entries for the domains/URLs you want to use (for the OPAC + Staff interface); 2. Configure the Apache web server (including/etc/apache2/sites-available/ and sites-enabled, as well as ports.conf); 3. Configure networking so that that your server is accessible on your network; 4. Hardening |
| 18:33 | your server, including using https) | |
| 18:34 | our installation instructions don't cover this, as there are lots of tutorials on the internet on setting up a linux server (Debian and Ubuntu) and configuring Apachehopefully you can find something | |
| 18:35 | s/Apachehopefully you can find something/Apache/ | |
| 18:38 | hopefully you can find tutorials on this in your language (in English, Digital Ocean and Linode have some great tutorials available - they are web server/VPS server hosting providers) | |
| 19:53 | gmcharlt joined #koha | |
| 19:54 | huginn joined #koha |
← Previous day | Today | Next day → | Search | Index