💾 Archived View for station.martinrue.com › js0000 › e8eca5e6fe9242a2be173171336da477 captured on 2024-05-12 at 16:37:34. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-05-10)
-=-=-=-=-=-=-
i keep coming back to gemini as a good tech balance
local client handles display customization
gemtext readable by humans
text remains a viable communication media
reduce network traffic
something i'd like to see added would be to have some machine translation hooks built in to protocol/client in order to facilitate breaking down language silos
💭
1 year ago · 👍 lykso
@skyjake thank you, by the way this detail doesn't make Lagrange any worse, which is still A W E S O M E !!! 👏👏👏 · 1 year ago
@freezr No, I haven't implemented a CSV renderer yet. It has been discussed in the past, and I think it would be a nice feature to have although CSV syntax isn't optimal for making larger tables by hand. · 1 year ago
@skyjake great! Is is true that Lagrange can render CSV file? · 1 year ago
Lagrange has a built-in language translation feature that uses LibreTranslate. It's "Translate..." in the page context menu. The resullts certainly aren't state-of-the-art in quality but it usually gets the message across. · 1 year ago