Recherche avancée

Sur d’autres sites (4052)

• Anomalie #4354 (En cours) : Problème de recherche REGEX, mauvais joker

  19 juin 2019, par Jimmy Laporte

  Bonjour,

  J’ai remarqué un problème dans la recherche REGEX. Les caractères accentués sont remplacés par un joker . dans le pattern pour la requête mysql. Hors cela ne fonctionne pas, si j’ai le titre d’un article qui est "Fêtes et Cérémonies" par exemple et que je recherche (dans le backend ou le front peut importe) "Fêtes et Cérémonies", l’article ne sort jamais. La requête REGEX envoyée à mysql est "F.tes C.r.monies|F.tes|C.r.monies" hors, tout comme avec un preg_match en php, "F.tes" ne matchera jamais "Fêtes" le pattern dois être "F.*tes".

  Pour résoudre le problème j’ai du modifier la ligne 202 dans le fichier ecrire/inc/rechercher.php

  <span class="CodeRay"><span class="local-variable">$q_t</span> = <span class="predefined">str_replace</span>(<span class="local-variable">$char</span>, <span class="local-variable">$is_preg</span> ? <span class="string"><span class="delimiter">"</span><span class="content">.</span><span class="delimiter">"</span></span> : <span class="string"><span class="delimiter">"</span><span class="content">_</span><span class="delimiter">"</span></span>, <span class="local-variable">$q_t</span>);
  </span>
  Télécharger

  
  par
  

  <span class="CodeRay"><span class="local-variable">$q_t</span> = <span class="predefined">str_replace</span>(<span class="local-variable">$char</span>, <span class="local-variable">$is_preg</span> ? <span class="string"><span class="delimiter">"</span><span class="content">.*</span><span class="delimiter">"</span></span> : <span class="string"><span class="delimiter">"</span><span class="content">_</span><span class="delimiter">"</span></span>, <span class="local-variable">$q_t</span>);
  </span>
  Télécharger

• truehd_core : Switch to in-place modifications

  6 juillet 2019, par Andreas Rheinhardt

  truehd_core : Switch to in-place modifications
  The truehd_core bitstream filter decreases the sizes of the
  
  major_sync_info structure (if present), of the
  
  substream_directory and of the substreams themselves. As a consequence,
  
  there is enough space available in front of the actual substream data
  
  for the new header, so that one only needs to modify the header in front
  
  of the actual data (which apart from shrinking is left untouched) and
  
  the packet's size and buffer pointer (after having made sure that the
  
  packet is writable).
  This and switching to bsf_get_packet_ref also removed the need for
  
  having separate packets for in- and output.
  Even if the input is not writable, there are noticable performance
  
  improvements : The average of 10 iterations of processing a file with 262144
  
  runs each (inlcuding about 20 skips per iteration) went down from 5669
  
  to 4362 decicycles. If the input is writable, it goes down to 1363
  
  decicycles.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] libavcodec/truehd_core_bsf.c

• avformat/matroskadec : Accept more unknown-length elements II

  17 mai 2019, par Andreas Rheinhardt

  avformat/matroskadec : Accept more unknown-length elements II
  Up until now, one last kind of unknown-length element hasn't been
  
  properly handled : Unknown-length elements that are supposed to be
  
  skipped, i.e. the level 1 elements that might reside after the
  
  clusters.
  This commit changes this. To do this, ebml_parse got a mode that
  
  essentially tries to skip everything except when parsing is needed
  
  (namely for unknown-length elements for which parsing is necessary
  
  as they can't be skipped). This mode is selected by using a NULL
  
  as destination where the parsed data should be written to.
  
  It is used to parse the level 1 elements in matroska_parse_cluster.
  The syntax list used for parsing must of course include links to
  
  the syntax of all the master elements that might need to be parsed.
  
  In other words : Instead of matroska_clusters (which contained every
  
  level 1 element except clusters as EBML_NONE elements designated to
  
  be skipped) matroska_segment is needed and used ; matroska_clusters has
  
  been removed.
  Furthermore, matroska_segment has been reordered so that clusters are at
  
  the front as this is now the most common case for this list.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] libavformat/matroskadec.c