Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

more FLO formats, other format improvements #1

Open
wolftune opened this issue Dec 22, 2016 · 5 comments
Open

more FLO formats, other format improvements #1

wolftune opened this issue Dec 22, 2016 · 5 comments

Comments

@wolftune
Copy link
Contributor

Great step getting stuff up. I may be able to do this, but whoever gets to it first:

Would be far better for several reasons but mostly for maximizing contributions to not use proprietary file formats. Instead of iWork .pages and .numbers, it would be best to use Open Document Format for these. Rich-text is a proprietary Microsoft format, and license files, especially here, should be just plain text, probably Markdown so GitHub will display it nicely.

PDF is fine.

.sketch files should be exported to SVG. png and jpg are fine, but we do want the vector source files for all images when available.

xlsx file should be exported to open document format

For the site, it's really odd that html files are .txt — the files seem fine, but the names should be changed to .html (is .txt filename something Nation Builder requires or something?)

@nardo
Copy link
Owner

nardo commented Dec 26, 2016

Per comments on the CC license, we don't have a free software agenda. We have an agenda to make stuff easy for folks to edit. In that vein it'd likely be better to use .docx and .xlsx rather than the open document versions. Likewise Sketch -- converting to SVG would lose a ton of the specific stuff in the documents (I think).

.txt is used so that TextEdit won't open the files in HTML mode. I can switch to a different editor.

@wolftune
Copy link
Contributor Author

I acknowledge the agenda, and that relates to priorities here, but that's not a reason to do or not do something (if someone had a complaint about a sexist framing on the site, we wouldn't say anything about this not having a feminist agenda, we'd just work to address the issue)

I don't necessarily accept that docx and xlsx is better than open document. Open Document Format is a universal international standard, anyone can use it with both free and proprietary tools, and I don't think there's any downsides. I can and may open the proprietary formats in LibreOffice, but I'm not going to use any other tool. So, for me and other and for reasons that make sense anyway despite not being the purpose of this org, ODF is preferable.

As to SVG, same thing in being a universal standard. I have no reason to think the type of material here will lose anything in SVG format, but I'm not sure. For me to potentially work with the files, I'd use SVG. I haven't checked into what I can or can't do with the Sketch files, I haven't used such files before.

I don't understand the HTML mode issue, but I would want HTML recognized as HTML when I open the files in a text editor. I happen to use Vim and sometimes Atom, but tons of text editors exist.

Anyway, the richt-text thing is definitely no good, as we want README files and LICENSE files to be recognized and rendered by GitHub in Markdown or at least just plain text.

@SaraWolf
Copy link

SaraWolf commented Feb 6, 2017

Not sure if this helps but I generally use Open Office. It's open source but it functions basically just like word/office etc.

@wolftune
Copy link
Contributor Author

wolftune commented Feb 6, 2017

@SaraWolf that's the right idea. For your reference, a fork happened several years ago, and now LibreOffice is the significantly improved and updated version of Open Office, so you should just upgrade to that and recommend that to people instead of Open Office. Cheers

@endolith
Copy link
Contributor

it's really odd that html files are .txt — the files seem fine, but the names should be changed to .html

Yes, this is strange.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants