| Time |
Nick |
Message |
| 00:03 |
|
kworstell_isl joined #evergreen |
| 07:53 |
|
rfrasur joined #evergreen |
| 08:18 |
|
BDorsey joined #evergreen |
| 08:28 |
|
mantis1 joined #evergreen |
| 08:35 |
|
mmorgan joined #evergreen |
| 08:57 |
|
dguarrac joined #evergreen |
| 09:18 |
|
jvwoolf joined #evergreen |
| 10:28 |
|
collum joined #evergreen |
| 11:02 |
|
javier_guel joined #evergreen |
| 11:05 |
javier_guel |
Hi all, Is there any way to add accents on action triggers templates? to could receive emails with accents |
| 11:09 |
csharp_ |
accents? do you mean italics? or ` marks? |
| 11:11 |
csharp_ |
the templates themselves are just text - by default it's plain text, but there are ways to use the header to send HTML (not done that myself, but it should be possible) |
| 11:21 |
javier_guel |
I mean marks, we are on México and we want to use for example the word: Título |
| 11:24 |
|
jihpringle joined #evergreen |
| 11:26 |
collum |
I just copied and pasted á to the end of the text for our test email trigger, and it worked. The email I received had the diacritic. But I had to paste it into the template. Keyboard shortcuts didn't work. |
| 11:39 |
javier_guel |
we already tried that, but we are receiving emails with words like this TÃtulo instead of Título, Is there any other place to check coding? |
| 11:44 |
|
BDorsey joined #evergreen |
| 11:44 |
JBoyer |
It’s possible that how you initially type them may matter. Some extended ASCII characters may not correctly survive the trip to UTF-8 even if they look right on your screen. I’m not sure if Charmap can help with things like Unicode combining characters and the like. |
| 11:52 |
|
jihpringle joined #evergreen |
| 11:59 |
javier_guel |
Is the same problem with lastnames, the emails received are with other characters, for example: Hernández MartÃnez, instead of Hernádez Martínez, |
| 12:22 |
|
jvwoolf joined #evergreen |
| 12:22 |
|
mrtnnbr joined #evergreen |
| 12:22 |
|
book` joined #evergreen |
| 12:22 |
|
jonadab joined #evergreen |
| 12:22 |
|
jweston joined #evergreen |
| 12:22 |
|
abneiman joined #evergreen |
| 12:22 |
|
scottangel joined #evergreen |
| 12:22 |
|
DaMobi joined #evergreen |
| 12:22 |
|
jeff joined #evergreen |
| 12:22 |
|
troy joined #evergreen |
| 12:22 |
|
bshum joined #evergreen |
| 12:22 |
|
dluch_ joined #evergreen |
| 12:22 |
|
Bmagic joined #evergreen |
| 12:30 |
|
collum joined #evergreen |
| 12:55 |
|
Stompro joined #evergreen |
| 12:57 |
Stompro |
Hello, should I worry that something is wrong if the "did you mean" feature update process only takes 4 minutes? |
| 13:03 |
Stompro |
The release notes just mention that it may take several hours... for large sites. We are not a large site, so it is probably fine. |
| 13:11 |
Bmagic |
Stompro: search for something and see what happens in the OPAC. If it's working, it'll suggest something that does exist |
| 13:32 |
|
_collum joined #evergreen |
| 15:06 |
|
sleary joined #evergreen |
| 15:34 |
|
collum joined #evergreen |
| 15:35 |
|
mmorgan1 joined #evergreen |
| 15:57 |
|
jvwoolf left #evergreen |
| 16:55 |
jeff |
multi-hop transits would be interesting. |
| 16:56 |
jeff |
i.e., to get from BLUE-BR1 to RED-BR2 you first go to GREEN-MAIN |
| 16:57 |
jeff |
anyone transiting an item whose destination is RED-BR2 would transit to GREEN-MAIN, and at GREEN-MAIN the item would print a transit slip for RED-BR2 (because GREEN-MAIN has a means of physically moving items there that not all libraries have) |
| 17:18 |
|
mmorgan1 left #evergreen |
