Recherche avancée

Sur d’autres sites (6250)

• Why I became a HTML5 co-editor

  1er janvier 2014, par silvia

  A few weeks ago, I had the honor to be appointed as part of the editorial team of the W3C HTML5 specification.

  Since Ian Hickson had recently decided to focus solely on editing the WHATWG HTML living standard specification, the W3C started looking for other editors to take the existing HTML5 specification to REC level. REC level is what other standards organizations call a “ratified standard”.

  But what does REC level really mean for HTML ?

  In my probably somewhat subjective view, recommendation level means that a snapshot is taken of the continuously evolving HTML spec, which has a comprehensive feature set, that is implemented in a cross-browser interoperable way, has a complete test set for the features, and has received wide review. The latter implies that other groups in the W3C have had a chance to look at the specification and make sure it satisfies their basic requirements, which include e.g. applicability to all users (accessibility, internationalization), platforms, and devices (mobile, TV).

  Basically it means that we stop for a “moment”, take a deep breath, polish the feature set that we’ve been working on this far, and make sure we all agree on it, before we get back to changing the world with cool new stuff. In a software project we would call it a release branch with feature freeze.

  Now, as productive as that may sound for software – it’s not actually that exciting for a specification. Firstly, the most exciting things happen when writing new features. Secondly, development of browsers doesn’t just magically stop to get the release (REC) happening. And lastly, if we’ve done our specification work well, there should be only little work to do. Basically, it’s the unthankful work of tidying up that we’re looking at here.

  So, why am I doing it ? I am not doing this for money – I’m currently part-time contracting to Google’s accessibility team working on video accessibility and this editor work is not covered by my contract. It wasn’t possible to reconcile polishing work on a specification with the goals of my contract, which include pushing new accessibility features forward. Therefore, when invited, I decided to offer my spare time to the W3C.

  I’m giving this time under the condition that I’d only be looking at accessibility and video related sections. This is where my interest and expertise lie, and where I’m passionate to get things right. I want to make sure that we create accessibility features that will be implemented and that we polish existing video features. I want to make sure we don’t digress from implementations which continue to get updated and may follow the WHATWG spec or HTML.next or other needs.

  I am not yet completely sure what the editorship will entail. Will we look at tests, too ? Will we get involved in HTML.next ? This far we’ve been preparing for our work by setting up adequate version control repositories, building a spec creation process, discussing how to bridge to the WHATWG commits, and analysing the long list of bugs to see how to cope with them. There’s plenty of actual text editing work ahead and the team is shaping up well ! I look forward to the new experiences.

• awkward behaviour in bash find-loop with ffmpeg

  25 avril 2018, par Alexander

  There is something weird going on when running following script with Docker.

  The dockerfile for this is :

  FROM debian:9
  
  WORKDIR /app
  
  RUN apt-get -y update && \
  
      apt-get -y install ffmpeg curl
  
  COPY . /app

  The script run.sh :

  #!/bin/bash
  
  find /pfs/in -maxdepth 1 -name "*.flac" -print0 | while IFS= read -r -d $'\0' inFile; do
  
      echo "\n##### Process '${inFile}' #####"
  
      ffmpeg -y -i ${inFile} -ar 16000 tmp.wav # use 16kHz - default for EML
  
  done

  Starting this, when mounting 3 files into the container :

  $ ls pfs/in/
  
  Testaudio16k_2.flac  Testaudio16k.flac  Testaudio16k.wav  TestSprache_Saetze.flac
  
  $ docker run --rm -t -v $(pwd)/pfs/in:/pfs/in test-img:latest /bin/bash run.sh

  I get an error on processing the second file : pfs/in/Testaudio16k_2.flac: No such file or directory. The leading / is missing. It is also missing in the preceeding echo. Indeed this happens every second file (if I put more than 3 files in that folder).

  Now coming to the counter example :
  If I comment out the ffmpeg line in the script, rebuild and run, The echo prints for every file the correct path.

  Does anybody have an idea about this ?
  Is it about the find or is the ffmpegdoing something weird ? Something completely different ?

• Documentation #2094 : Déclarer ses objets éditoriaux - pipeline declarer_tables_objets_sql

  17 août 2011, par Eric Lupinacci

  Il existe aussi un fichier Google partagé que j’ai écrit avec Denisb et que Cédric a relu et corrigé : https://spreadsheets.google.com/spreadsheet/ccc?key=0Aq-LDsZ2YhzydDBvMjRSamQ5aWtfNWpKcnFESjQwU3c&hl=fr&authkey=CMmWhpEC