You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pls checkout master of archivist-composer to verify. There's data/problematic_doc_isolated.js as a breaking example.
What would be a good strategy to solve this? We could make the fragmenter robust to exclude those annotations and show a warning maybe? However I wonder what the cause of this data inconsistency is. I suspect that copy pasting is causing it (when you copy for instance entity references around).
The text was updated successfully, but these errors were encountered:
Hey, @oliver!
I think this is coming from importing ms word para with color marking. I could not verify this because of I haven't got windows machine now.
El único modo de vencer el secuestro del conocimiento
es comprender sus razones.
La manera de revertirlo, de cambiarlo
O todxs somos hackers de los secuestros cotidianos
O morimos sin saber lo que somos
¡Piensa para vivir, actúa para hackear!
Cada día, una acción procomún a la vez.
“Tengo horror de aquellos cuyas palabras van más allá que sus actos”
Albert Camus
Ahh too bad we are not able to improve the Composer desktop app atm. It hasn’t seen an update since over a year. I think we will relaunch it but i can not say when this will happen.
See: substance/archivist-composer#78
Pls checkout master of archivist-composer to verify. There's
data/problematic_doc_isolated.js
as a breaking example.What would be a good strategy to solve this? We could make the fragmenter robust to exclude those annotations and show a warning maybe? However I wonder what the cause of this data inconsistency is. I suspect that copy pasting is causing it (when you copy for instance entity references around).
The text was updated successfully, but these errors were encountered: